RE: crontab entry

2003-10-10 Thread Chris Purcell
> Sounds like cron isn't running as root. So it is able to write a file > without hard coding a path to it because it is creating the file in it's > working directory. Create a directory that the user cron is running as > can write to. That sounds like what the problem is. > > Wade Actually, Ju

RE: crontab entry

2003-10-10 Thread Wade Chandler
al Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Purcell Sent: Friday, October 10, 2003 12:59 PM To: [EMAIL PROTECTED] Subject: crontab entry root's crontab looks something like this... SHELL=/bin/bash MAILTO=root PATH=/usr/local/sbin:/usr/local/bin:/sbin

Re: crontab entry

2003-10-10 Thread Justin Banks
Chris Purcell wrote > root's crontab looks something like this... > > SHELL=/bin/bash > MAILTO=root > PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin > rsync=/usr/bin/rsync -e ssh -azv --delete --delete-excluded > --exclude=/some/folder [EMAIL PROTECTED]::home /home/ > > 7 */2 *

crontab entry

2003-10-10 Thread Chris Purcell
root's crontab looks something like this... SHELL=/bin/bash MAILTO=root PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin rsync=/usr/bin/rsync -e ssh -azv --delete --delete-excluded --exclude=/some/folder [EMAIL PROTECTED]::home /home/ 7 */2 * * * $rsync > /root/rsync_`/bin/date +

RE: Using the date command in a crontab entry - THANKS!

2002-03-07 Thread Eric Sisler
My thanks to [EMAIL PROTECTED] and Arthur H. Johnson II <[EMAIL PROTECTED]> for helping to alleviate my stupidity. ;-) It seems that crond was tripping over the % rather than the +: >actually its the % that crond is interpreting as newline. use >/usr/local/sbin/backup.bash "`date +\%Y-\%m-\%d

Re: Using the date command in a crontab entry

2002-03-07 Thread Arthur H. Johnson II
e command in a crontab entry, and I keep > getting an error. I've tried just about every possible syntax I can think > of, so I'm either being stupid or what I want can't be done. I've tried > the following entries (minus the time/date/day fields): > > /usr/lo

RE: Using the date command in a crontab entry

2002-03-07 Thread Stephen_Reilly
actually its the % that crond is interpreting as newline. use /usr/local/sbin/backup.bash "`date +\%Y-\%m-\%d`" Fri steve -Original Message- From: Eric Sisler [mailto:[EMAIL PROTECTED]] Sent: 07 March 2002 15:51 To: [EMAIL PROTECTED] Subject: Using the date command in a cro

Using the date command in a crontab entry

2002-03-07 Thread Eric Sisler
Greetings, I'm trying to insert the date command in a crontab entry, and I keep getting an error. I've tried just about every possible syntax I can think of, so I'm either being stupid or what I want can't be done. I've tried the following entries (minus the tim

Re: crontab entry question

2000-08-22 Thread Bret Hughes
Uncle Meat wrote: > On 22-Aug-2000 [EMAIL PROTECTED] spoke something to the effect: > > > > If I change the command to > > > >/301 ** *root run-parts > > /etc/run.hourly > > > > Then this command will every half hour right ? > > You intuition about the form

Re: crontab entry question

2000-08-22 Thread David Kramer
On Tue, 22 Aug 2000 [EMAIL PROTECTED] wrote: > does the following crontab entry > 01 * * * * root run-parts /etc/run.hourly > read > run at 1 am everyday and month run-parts ? No, it says run every minute. > > The problem is I thought crontab entries were of the format &

Re: crontab entry question

2000-08-22 Thread Vidiot
> >does the following crontab entry >01 * * * * root run-parts /etc/run.hourly >read >run at 1 am everyday and month run-parts ? > >The problem is I thought crontab entries were of the format > > Minute Hour DayOfMonth Month DayOfW

crontab entry question

2000-08-22 Thread kabir
does the following crontab entry 01 * * * * root run-parts /etc/run.hourly read run at 1 am everyday and month run-parts ? The problem is I thought crontab entries were of the format Minute Hour DayOfMonth Month DayOfWeek Command eg 0 1 ** * root