One of my colleagues suggested changing the respawn to once for
cron, make sure cron isnt runnig, run telinit q, check for cron,
alter the line back to respawn, telinit q again. My colleage stated
he has seen this work for srcmstr. It was also suggested to move the
cron line above pcnfs line.
/etc# ls -la locks
lrwxrwxrwx 1 root system 10 Mar 12 2003 locks ->
/var/locks
so thats ok
# ls -al /usr/sbin/cron
-r-s--S--- 1 root cron size same as his other 5.1s
/usr/sbin/cron
Everything checks out, cron will start fine manually but will not
respawn from inittab.
It has been suggested that the install_Assist line in the inittab
keeps the system from re-reading the inittab
We killed install assistance pid on his system and now the cron
will respawn.
cron, make sure cron isnt runnig, run telinit q, check for cron,
alter the line back to respawn, telinit q again. My colleage stated
he has seen this work for srcmstr. It was also suggested to move the
cron line above pcnfs line.
/etc# ls -la locks
lrwxrwxrwx 1 root system 10 Mar 12 2003 locks ->
/var/locks
so thats ok
# ls -al /usr/sbin/cron
-r-s--S--- 1 root cron size same as his other 5.1s
/usr/sbin/cron
Everything checks out, cron will start fine manually but will not
respawn from inittab.
It has been suggested that the install_Assist line in the inittab
keeps the system from re-reading the inittab
We killed install assistance pid on his system and now the cron
will respawn.
No comments:
Post a Comment