Thank you very much for your reply . Can you please do me favor and let me know where I have to check for the scripts that may wipe out these files on reboot ? How can I check if /var/spool on transient storage ?
Please be informed that I have two CentOS servers , one is running CentOS 5.0 and the other is CentOS5.2 . For the CentOS5.2 , the cron job does not disappear after server reboot but for the 5.0 one it does . Can you please let me know what is wrong here ?
Thank you in advance
On Wed, Oct 28, 2009 at 5:16 AM, John R Pierce <pierce@xxxxxxxxxxxx> wrote:
crontab -e /should/ be editing the file /var/spool/cron/$USERhadi motamedi wrote:
> Dear All
> Please be informed that I have an CentOS 5 server and I need it to be
> automatically rebooted at pre-specified times . To this end , I tried
> to set it as its crontab job as the followings :
> #crontab -e
> 30 15 * * * reboot
> It got through but after the server first reboot the crontab job
> disappeared . So I tried to set it in another way , as the followings :
> set the cron list in /tmp/temp
> add the following lines to /etc/rc.local :
> crontab /tmp/temp
> But still the crontab job will disappear after the server first reboot
> . Can you please do me favor and let me know how can I make the
> crontab job permanent on my CentOS server even after server reboot ?
> Let me thank you in advance
>
and crond reads /var/spool/cron/* to decide what to do.
do you have scripts that are wiping out these files on reboot? or is
/var/spool on a transient (non-persistent) storage ?
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
