When I run edge.cronset, I receive the following error message: "mv: cannot access /tmp/krontmp2 no such file or directory"

Keywords

edge cronset doesn't add entry to crontab file

Release

BackupEDGE all versions.

Problem

When I run edge.cronset, I receive the following error message: mv: cannot access /tmp/krontmp2 no such file or directory The entry is not saved through the edge.cronset program. Duplicate entries are placed into the crontab file.

Cause

An unusual bug that occurs whenever the only entry in the crontab file is the entry for BackupEDGE.

Solution

Edit the crontab file /usr/spool/cron/crontabs/root manually and remove any entries for BackupEDGE. These would be entries that have /etc/edge.nightly in them. Then place a comment line at the beginning of the file so there is an entry in the file other than for BackupEDGE. A safe way to do this would be as follows:

           crontab -l > /tmp/crontab

           vi /tmp/crontab          (make changes as necessary,save and exit)

           crontab /tmp/crontab

The first command outputs a copy of the crontab file to a temp file. The second command allows you to edit the temporary crontab file. The third command replaces the original crontab file with the newly edited crontab file. Your newly created crontab file might look like this:

* This is a comment line

Then run edge.cronset again. After running the program, you should observe that the settings are saved and that an entry for the edge.nightly program is properly placed in root's crontab file.

Back to the main index