I think I have found a bug in the Programs Scheduling applet of MCC. It is mangling the cron files when saving a change to an existing job.
Here is an example: Contents of my /var/spool/cron/root file prior to making any change # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/var/tmp/cronattemp installed on Tue Oct 1 07:55:58 2002) # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $) 0 0 * * * /home/greg/scripts/rdate 0 0,4,8,12,16,20 * * * /home/greg/scripts/hourly_backup.sh 0 13 * * * /home/greg/scripts/backup_rotation.sh Contents of /var/spool/cron immediately following the modification of time on the third job. I simply re-entered the times. Notice the 0 in fron of /home in line 6. # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/var/tmp/cronattemp installed on Tue Oct 1 08:09:31 2002) # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $) 0 0 * * * /home/greg/scripts/rdate 0 0,4,8,12,16,20 * * * /home/greg/scripts/hourly_backup.sh 0 13 * * * 0/home/greg/scripts/backup_rotation.sh Here is another example: I went to the change command button and clicked apply without actually changing anything. The contents of /var/spool/cron/root now is # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/var/tmp/cronattemp installed on Tue Oct 1 08:14:47 2002) # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $) 0 0 * * * /home/greg/scripts/rdate ,20 * * * /home/greg/scripts/hourly_backup.sh 0 13 * * * 0/home/greg/scripts/backup_rotation.sh The time sequence of the job is now mangled (compare line 5 to original above) Not sure how to fix it, but I thought the developer on this one would like to know. /g ___________________ [EMAIL PROTECTED]
