Adam Getchell wrote: > Running crontab -e, my file looks like: > > # run-parts > 01 * * * * root run-parts /etc/cron.hourly/logcheck.sh > 02 4 * * * root run-parts /etc/cron.daily > 22 4 * * 0 root run-parts /etc/cron.weekly > 42 4 1 * * root run-parts /etc/cron.monthly When I run crontab -e I get an empty file. When you run 'crontab -e', you edit your own personal crontab file, in /var/spool/cron. The syntax for this file is just slightly different. Since this isn't the system crontab, the sixth item in the file isn't a username, it's a command. Cron is, then, interpereting "root" as the command it's supposed to run. None of this should be necessary, however, since the system crontab will run all of this. Try removing them all, and look in your logs to make sure that cron is actually executing the files as it should be. > I can run my logcheck script manually in the listed directory, and I also > thought that I could write any shell script, drop it into /etc/cron.hourly, and > edit crontab appropriately. You can drop any executable into /etc/cron.hourly you like, and you don't have to change the crontab file at all. That's what run-parts does. It executes all of the (executable) files in the directory it's given as an argument. MSG -- To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
