I recently had a similar problem with a cron, had to write a wrapper script & source some ENV files. Cron runs in a restricted environment & may not have some VARs, or PATHs set that you have when run interactively. Also 'set -x' and 'set -n' with some extra echo statements in bash can help you troubleshoot what is actually happening in your cron script. The username/owner of the cron should get the email output of the cron runs, I would check this & make sure your user account is setup correctly. -HTH [EMAIL PROTECTED]

Jess Cannata wrote:

I tried removing /dev/null from the crontab so it will send an e-mail. It doesn't send any e-mail, but it does log the info in /var/log/messages. I even added the following crontab job:

*/1 * * * * /opt/opium/bin/sync_users &

It always reports that it is pushing the files to the clients, but nothing happens.

It works fine when ran manually, but when ran via crontab it fails. I'm quite perplexed because I don't see any reason why this shouldn't work. I will keep looking into it.

Thanks for your help.

Jess


-- Art Wildman/ITO - mailto: [EMAIL PROTECTED] National Weather Service Office: WFO-JAX 13701 FANG Dr., Jacksonville, FL. 32218 http://www.srh.noaa.gov/jax



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Oscar-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-users

Reply via email to