UNIX for Dummies Questions & Answers

Here is what my crontab shows when I do crontab -e

# fields minute(0-59) hour(0-23) day(1-31) month(1-12) day of week (0-6, 0=sun)
#

30 04 * * 06 /home/rkruck/scripts/shell/backup
15 9 * * * /home/rkruck/scripts/shell/get_passwd_files

The first script runs no problem as scheduled, but the second entry for get_passwd_files doesn't execute. I know the script works because I can run it manually. The second script uses scp to grab all of the /etc/passwd files off of a list of servers. This is run as a regular user that is in the /etc/cron.d/cron.allow file, however even as root it doesn't run. This is a solaris 10 x86 machine if that helps any.

Any suggestions are appreciated.

Thanks
Robert

Please use the search function of the forum - there are lot's of posts and solutions or suggestions to cron problems.

Read the FAQ for cron:
https://www.unix.com/answers-frequent...n-crontab.html

- Check the mails of the user - maybe cron was upset and has sent a mail.
- Redirect it's output to a file like "* * * * * /yourscript.sh >> bla.log 2>&1" and check what's in there.
- Source the .profile or any environment defining file
- Use absolute paths

Thanks,

problem solved. Seems cron couldn't find the scp command so once I put in the full path for scp it worked fine.

Next time I'll remember to do a search before posting =)

As a one time exercise you could create a cron containing just an "env" command and execute it once. The output will be in the mail for the user owning that crontab. This will show you the initial environment (including $PATH) available when running from cron.

Hi,

even I am having some problem running a script thru the cron. When you say "Use absolute paths", do you mean absolute paths in the script or setting up the cron?

I have already followed steps 1 thru 3 and had he doubt on the 4 hence asking.
In the 2nd step the redirection does not put any info in the file "bla.log".

Please advice.

Thanks.

Both. You have to make sure everything finds everything because you will not have the same environment when working live on the shell where a lot is usually already in your $PATH.