RE: Logging from cron

2004-03-23 Thread Jason Ferguson
I do the following: The following line syncs the data 0,15,30,45 6-22 * * * /usr/local/bin/file_sync > /tmp/rsync-error 2>&1 The following runs once a day to delete added files 0 5 * * * /usr/local/bin/file_sync_delete > /tmp/rsync-error 2>&1 The next line monitors the sync

Re: Logging from cron

2004-03-23 Thread Tim
Thanks Brian. :-) Tim *** REPLY SEPARATOR *** On 3/23/2004 at 1:00 PM Brian Cuttler wrote: >We always run rsync from a shell script, sometimes we pipe the >shell script output to mailx or such. I'm sure you can write >it to a log file but don't recall the syntax off hand. > >W

Re: Logging from cron

2004-03-23 Thread Tim
Hi Tim, That worked. Thanks!!! BTW, sorry about the automated message from my anti-spam system. I didn't realize that replies would include an individual subscriber's email. So I quickly created a separate email address for this list without the spam trap. Thanks again, Tim *** R

Re: Logging from cron

2004-03-23 Thread Brian Cuttler
We always run rsync from a shell script, sometimes we pipe the shell script output to mailx or such. I'm sure you can write it to a log file but don't recall the syntax off hand. We never run the single command as a cron task, ie never 0 23 * * 1-5 rsync but do 0 23 * * 1-5 script1.sh I'm sur

Re: Logging from cron

2004-03-23 Thread Tim Conway
"$rsynccommandline >$logfile 2>&1" is one way - use however many "v"s you need. If you want to accumulate the output of several invocations, "$rsynccommandline >>$logfile 2>&1" If you really want it in syslog "$rsynccommandline 2>&1 |logger $facility.$severity", and make sure you have syslog con