> OK. I echoed every line that is to be run before it is run. I know it > looks like commands take up more than one line, but they don't - it's > just the text wrap. > > On Sat, 2005-01-08 at 20:05 +0100, [EMAIL PROTECTED] wrote: > > On 08-01-05 10:28 -0600, Michael Sullivan wrote: > > > I'm having issues with my backup scripts. I wrote both backup scripts > > > back when I was using FC1 on my client PC. One is a full backup of > two > > > user accounts in /home and then /etc and the other creates a list of > > > files created/modified the date before the script is run and then only > > > backs those files up. Full backup is on Sunday; every other day gets > > > iBackup. They're listed in the crontab to run at 3am. The trouble is > > > each morning when I'm reading my cron report for the backup it says > that > > > there was a problem with tar in my script, but when I run the script > > > from the command line as root it works fine. I scheduled the script > in > > > root's (su -) crontab.
Probably a difference in cron's environment versus the environment that you're starting the command in as root... When I encounter things like this I'll tend to flush out the script with additional environment properties to make things work. You can do this by prepending environment settings manually into the start of the script (typically the PATH is the critical one), or you can automate part of it by following the suggestion for using an 'at' script as the basis for the cron script as documented here: http://www.cod.utvinternet.com/documentation/mondo-with-cron/mondo-with-cron -5.html This suggestion is from mondo-rescue, but you'd do a similar thing with 'at' using your script name. I'm willing to bet that this will fix your cron issue. Dave -- [email protected] mailing list
