Sorry should have told you that I used the full path for everything and it is still not working - is there a way of making sure the commands you use in crontab will work i.e. could I set all the env variable to null and try manually typing the command? Dan ----- Original Message ----- From: "Robert C. Paulsen Jr." To: Sent: Tuesday, May 21, 2002 1:19 PM Subject: Re: [SLE] checking crontab....

On Tue, May 21, 2002 at 01:05:53PM +1000, dan wrote:

...

Hi

I have tried to get a program to work via crontab...trouble is something is going wrong and for some reason the program is not being called. I have executed the program in question via the command line so I suspect it is something to do with environment variables.

Does anyone know if either crontab produces an error log or if I can debug what it is doing?

Jobs run from crontab don't have the path set up the same as jobs run from a shell. You probably need to fully-qualify the program name.

-- Robert C. Paulsen, Jr. robert@paulsenonline.net

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com

I'm not sure if this has been beaten to death, but I use cron both on my home desktop system (SuSE 7.3), my laptop (SuSE 8.0), and the blu.org server (RH 7.2), and work (Tru64 Unix). First, I keep a copy of my crontab files in a local directory. Then I run the crontab file to install them. crontab mycrontab Then I run crontab -l to check it. The other thing is that you should make sure that your scripts all have the appropriate execute permission. I always test my scripts by inserting echoes on dangerous lines, and set up a reasonable close time just so I can make sure the script will work to some extent. (I usually test the production script manually also). On 21 May 2002 at 13:17, dan wrote:

Sorry should have told you that I used the full path for everything and it is still not working - is there a way of making sure the commands you use in crontab will work i.e. could I set all the env variable to null and try manually typing the command?

-- Jerry Feldman Enterprise Systems Group Hewlett-Packard Company 200 Forest Street MRO1-3/F1 Marlboro, Ma. 01752 508-467-4315 http://www.testdrive.compaq.com/linux/

* Charles Philip Chan (cpchan@sympatico.ca) [020520 20:58]:

First of all did you do a

rccron restart

after editing the crontab?

You don't need to restart cron after editing the crontab or /etc/cron.d files. Otherwise users wouldn't be able to add cronjobs. -- -ckm

You don't need to Cc me, I'm subscribed to the list. * Charles Philip Chan (cpchan@sympatico.ca) [020520 21:44]:

This is what I thought also (this is with the main crontab file in /etc), Until I found out I had a few new jobs that I put into it not starting until I restarted cron.

crond checks the modtime on etc/crontab and /etc/cron.d every minute. -- -ckm

* tabanna (tabanna@aig.forthnet.gr) [020520 23:43]:

Where, please, is the correct place to write ones 'cron' preferences ?

{ until now, i have edited :

/var/cron/tabs/rootcron

, and, then executed : "crontab rootcron" }

That's one way to do it. Another is to just run 'crontab -e'. -- -ckm