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 -----Original 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:/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 +%m%d_%I%M%p` The problem is redirecting the output to the above file name. If I manually run that command from the shell, it works fine and creates a file called something like /root/rsync_1010_1257PM. When I run it from a cron job, it fails and the job doesn't run. This is the error... /bin/bash: -c: line 1: unexpected EOF while looking for matching ``' /bin/bash: -c: line 2: syntax error: unexpected end of file If I do a simple redirect without the date command, it works fine. For example, $rsync > somefile.txt works no problem from cron. Thanks, Chris -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
