From: Rodgers, Rodney (Rodney.Rodgers@disa.mil)
Date: Thu Jun 16 2005 - 13:16:56 EDT
Below was my initial entry. There were so many responses, thanks to
everyone.
Cron must be funky, but -HUP didn't work
Thanks to JV for the solution.
I simply had to wake up cron:
now I will just have to push this out to all the machines.
either 'crontab -e root' add a space and delete a space, or
/etc/init.d/cron stop & start
to wake cron up. Common problem.
-----Original Message-----
From: Rodgers, Rodney [mailto:Rodney.Rodgers@disa.mil]
Sent: Thursday, June 16, 2005 11:30 AM
To: sunmanagers@sunmanagers.org
Subject: cron files
I am in need of assistance.
I received some messages in my root mail that I need to fix.
Your "cron" job
/rootcron/GCCVer/blah_blah.blah
produced the following output:
sh: /rootcron/GCCVer/blah_blah.blah: not found
easy enough, I replaced the correct file by pushing a small script to
several machines.
crontab -l | grep -v ....> /tmp/crontab.new
then
echo '0 0 * * * /rootcron/GCCVer.... > /tmp/crontab.new etc... I was able
to change the file easy enough.
but the problem is , is that it is not reading the new file. Not even after
a kill -HUP (PID) of the cron daemon.
I did a # ps -ef | grep -i cron and then a # kill -HUP (pid) thinking this
would do the trick. I am still getting the same errors in the root mail.
How can I get the system to read the corrected root file in
/var/spool/cron/crontabs ?
Thanks in advance
Rod
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:30:55 EDT