Ok, I added my blacklist script to the /etc/cron.daily subdirectory. I gave it the same ownership and rights as the other scripts in there. I am using the same shell to execute it. But it is not running, or if it is it is not updating the blacklist hold file. If I run it manually it works. I figured that since I was making it a "system" cron job that simply placing it in the directory would activate it. Apparently that isn't the case. I know I can create a root cronjob to do this, but I really wanted it to be part of the base system. What am I doing wrong?
Brian Densmore
* Brian Densmore ([email protected]) wrote:
Ok, I added my blacklist script to the /etc/cron.daily subdirectory. I gave it the same ownership and rights as the other scripts in there. I am using the same shell to execute it. But it is not running, or if it is it is not updating the blacklist hold file. If I run it manually it works. I figured that since I was making it a "system" cron job that simply placing it in the directory would activate it. Apparently that isn't the case. I know I can create a root cronjob to do this, but I really wanted it to be part of the base system. What am I doing wrong?
Just a guess, but cron doesn't know about your $PATH, so you'll need to set it in your script or use the absolute paths in your commands. Have you checked the cron log?
dan
On Wednesday 27 October 2004 09:11 am, Brian Densmore wrote:
Ok, I added my blacklist script to the /etc/cron.daily subdirectory. I gave it the same ownership and rights as the other scripts in there.
... I know I can create a root cronjob to do this, but I really wanted it to be part of the base system. What am I doing wrong?
Oh, you mean you can create an entry in root's crontab to run it.
I usually put the scripts in /usr/etc, then put a symlink from the script to something in /etc/cron.daily (or whatever). That works.
May I suggest you develop some logging or error reporting that shows you if the script is getting called?
-
Brian Densmore -
dan radom -
Jonathan Hutchins