On 2010-08-17 19:57, Brian K. White wrote:
You can edit /etc/crontab directly with any editor of your choice at any time and the effects take place immediately when you save the file. No need to restart cron, no need to notify cron or reload the file with the crontab command.
Now that I remember. The proper way is not editing /etc/crontab, but adding a file in /etc/cron.d/, which has the same syntax. This way, if there is an update/upgrade, we are safe even if it is overwritten.
You can also create scripts in /etc/cron.d/* and not write any crontab entries in any crontab anywhere.
That. You were too concise ;-) If I read "man cron" correctly, /etc/cron.d/ is read directly by the daemon every minute. However, the suse script "/usr/lib/cron/run-crons" checks every 15 minutes to run, if needed, the scripts in cron.hourly, cron.daily, cron.weekly, and cron.monthly. -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar))