Environment
Novell Open Enterprise Server 2 (OES 2) Linux
Situation
Cron jobs for LUM users are not running after reboot
Resolution
To prove that you are seeing this problem check the load order in /etc/init.d/rc5.d (if run level 5, modify for your specific runlevel).
Look at the start order for namcd and cron. The lower the "S#" number the earlier it will start during the boot process. You want namcd to run before cron.
To fix this immediately run "rccron restart" to restart cron as namcd should already be running and cron jobs will start working for LUM users.
To fix this across reboots you need to ensure that cron starts after namcd.
1. Modify the /etc/init.d/cron file and in the "BEGIN INIT INFO" section on the "Should-Start:" line add "namcd"
2. Run "chkconfig cron off".
3. Run "chkconfig cron on" this will tell the server to start the cron service on reboot.
4. Check the start order in /etc/init.d/rc5.d
Look at the start order for namcd and cron. The lower the "S#" number the earlier it will start during the boot process. You want namcd to run before cron.
To fix this immediately run "rccron restart" to restart cron as namcd should already be running and cron jobs will start working for LUM users.
To fix this across reboots you need to ensure that cron starts after namcd.
1. Modify the /etc/init.d/cron file and in the "BEGIN INIT INFO" section on the "Should-Start:" line add "namcd"
2. Run "chkconfig cron off".
3. Run "chkconfig cron on" this will tell the server to start the cron service on reboot.
4. Check the start order in /etc/init.d/rc5.d