[EMAIL PROTECTED] said: > Personally, I would create a script that executes it, that is, if it needs > to be somewhere else, ie in the $PATH, else just move it there. > In that directory, you don't tell it what time to executes, it executes > all files in /etc/cron.daily/ once a day. > cat /etc/crontab for details, mine states: > 25 6 * * * root test -e /usr/sbin/anacron || run-parts --report > /etc/cron.daily > at 6:25 am daily.
thanks, Peter, Scott yes, I'm writing (well, cut'n'pasting to be more precise) a script in /usr/local/bin, then I'll put it's name in /etc/cron.daily /usr/local/bin is on the path, so, I guess I don't need synlinking # cat /etc/crontab | grep daily 02 4 * * * root run-parts /etc/cron.daily so, all things being equal the symlinked /usr/local/bin/logsproc should run at 4:02 am (I think) q: how can I time and log execution time ? I'd like to log when it was executed, and, how long it took, to a 'permanent' log, something like: head logarchived2.log 10 Mar 2001 06:22:57 25 logfile(s) now resolved in: 11459 sec. 10 Mar 2001 06:23:36 logarchived2 finished all logfiles in: 11498 sec. -- Voytek -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
