Hi, Just updated a few servers to U7, and rebooted them. I found out that crond would not start at boot even if it is configured to: crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off I have tested another reboot, same thing: I had to start crond manually. I don't see anything in the logs, and I don't have direct access to the console right now. Anyone seen the same thing?
Ugo Bellavance <ugob at camo-route.com> wrote in news:e1isdm$9km$1 at sea.gmane.org:> Hi, > > Just updated a few servers to U7, and rebooted them. I found out > that crond would not start > at boot even if it is configured to: > > crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off > > I have tested another reboot, same thing: I had to start crond > manually. > > I don't see anything in the logs, and I don't have direct access to > the console right now. > > Anyone seen the same thing? >I must also say this server hasn't been rebooted for a while, but since I saw there was an update of vixie-cron, I thought this was the problem. Ugo
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Apr 12, 2006 at 12:39:18PM +0000, Ugo Bellavance wrote:> Hi, > > Just updated a few servers to U7, and rebooted them. I found out that crond would not start > at boot even if it is configured to: > > crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off > > I have tested another reboot, same thing: I had to start crond manually. > > I don't see anything in the logs, and I don't have direct access to the console right now. > > Anyone seen the same thing?Try "refreshing" the startup scripts: # chkconfig --del crond # chkconfig --add crond # chkconfig crond on - -- Rodrigo Barbosa <rodrigob at suespammers.org> "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEPRiWpdyWzQ5b5ckRAmEJAKCDG6j0qglcUzndGXmj6Jcilpn/2QCfaMIJ X5XYCIy8VvYKoePm0krZrls=x9x+ -----END PGP SIGNATURE-----