tag 512757 confirmed pending
thanks
On 01/-10/-28163 08:59 PM, Michael Kaaden wrote:
> AFAICS the only problem is the correct order for the start of NIS,
> autofs, and cron. cron should start after NIS and autofs.
Thanks for the hint, I committed a fix.
Christian
signature.asc
Description:
Hi,
AFAICS the only problem is the correct order for the start of NIS,
autofs, and cron. cron should start after NIS and autofs.
If I read the documentation correctly, it should be sufficient to change
/etc/init.d/cron from
# Required-Start:$remote_fs $syslog $time
# Required-Stop: $remo
Package: cron
Version: 3.0pl1-106
Severity: normal
I wonder whether this is related to the ordering of the init.d scripts:
# ls /etc/rc*d/S*{autofs,nis,cron}
/etc/rc2.d/S03anacron@ /etc/rc3.d/S16nis@ /etc/rc5.d/S03anacron@
/etc/rc2.d/S03cron@ /etc/rc3.d/S17autofs@ /etc/rc5.d/S03cron@
Package: cron
Version: 3.0pl1-105
Severity: important
If the crontab is created by a NIS user it runs until the OS is stopped.
On reboot, cron displays in syslog :
Jan 23 13:09:54 myhost /usr/sbin/cron[3552]: (mylogin) ORPHAN (no passwd entry)
'cron' does not re-activate the 'crontab' once NIS i
4 matches
Mail list logo
