1847177 Members
5009 Online
110263 Solutions
New Discussion

Re: cron daemon

 
Ashish_29
Occasional Contributor

cron daemon

we have a K-Class system and after system reboot, cron daemon did not started and i had to start it manually.

Can somebody tell me why daemon has not started after reboot or where i can find the related information.

5 REPLIES 5
Steven E. Protter
Exalted Contributor

Re: cron daemon

check the file /etc/rc.log for errors.

Check the config file /etc/rc.config.d/cron

The first variable should be set to 1. If it is set to zero, this is your explanation. Set it to 1 and next boot time, cron will try and start.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Sunil Sharma_1
Honored Contributor

Re: cron daemon

check rc.log in /etc directory.

Sunil
*** Dream as if you'll live forever. Live as if you'll die today ***
HGN
Honored Contributor

Re: cron daemon

Hi

Make sure the CRON value is set to 1 in
/etc/rc.config.d/cron file
#!/sbin/sh
# @(#)B.11.11_LR
# Cron configuration. See cron(1m)
#
# CRON: Set to 1 to start cron daemon
#
CRON=1

Still if it does not start you have to look for errors.

Rgds

HGN
Mohanasundaram_1
Honored Contributor

Re: cron daemon

Hi Ashish,

after checking the above suggestions, you should also confirm what run level your system is in currently.

who -r

will indicate this. check /etc/inittab for the initdefault value. If your script is in a directory above the initdefault value then those will not get run.

This is because your system never transitioned to that level.

So, check these details and also let us know what is your OS version, where is your script located (example : /etc/rc3.d) and output of inittab file.

With regards,
Mohan.
Attitude, Not aptitude, determines your altitude
Mohanasundaram_1
Honored Contributor

Re: cron daemon

Oops! I did not notice that you were talking about cron.

That is the reason I was asking about "your script" . But still it does not hurt to check the run level.

Also ensure the cron patches are in place.
Attitude, Not aptitude, determines your altitude