Hi all my slackware friends,
After installing 13.37 for a few weeks, I found out today there are some changes on how crond being handled in 13.37:
i)in /etc/rc.d/rc.M, the log level has changed from '-l10' to '-l notice'
ii)crond no longer need to explicitly pipe to /var/log/cron using
Code:
/usr/sbin/crond -l10 >>/var/log/cron 2>&1
, and just
Code:
/usr/sbin/crond -l notice
will do, and somehow we still get log in /var/log/cron. Wonder where is the logging being done ?
iii)there is a new folder /etc/cron.d/
Now the problem is, if I put anything in /etc/cron.d/ , the cron job wouldn't get noticed by the cron daemon, and it will waite for a long time before it run the new job. What I put just a simple /etc/cron.d/beta file and the content of it is:
Code:
root@thinkphoenix:/etc/cron.d# cat beta
* * * * * date >> /root/beta.log
the file was created earlier;
Code:
root@thinkphoenix:/etc/cron.d# ll beta
-rwxr-xr-x 1 root root 33 May 17 01:08 beta*
, but the crond only pick up this a bit later:
Code:
root@thinkphoenix:/etc/cron.d# cat /root/beta.log
Tue May 17 01:16:01 MYT 2011
Tue May 17 01:17:01 MYT 2011
Tue May 17 01:18:01 MYT 2011
Tue May 17 01:19:01 MYT 2011
My friends, any idea on how to make the cron job being execute the next minute I created it ? As you know there is no start/stop cron daemon script in slackware, so do I really need to kill the cron process and start it again everytime I created a new cron job for 13.37 ?
Any sharing and discussion will be greatly welcome. You can let me know how you think about this new cron approach as well in 13.37. (Or may be it's already in 13.1 and I didn't notice that ?)