Red Hat Bugzilla – Bug 264
vixie-cron and ypbind starting order should be reversed
Last modified: 2014-03-16 22:08:38 EDT
Default crond is started before ypbind. This is a problem, because crond will not accept jobs from users which it doesn't know. And of course a lot of users won't be 'known' until ypbind has been started. Should be easy enough to fix, but it is quite annoying... Regards Ward Wouts
*** Bug 264 has been marked as a duplicate of this bug. *** The default start and stop orders for the NIS daemons are wrong. cd /etc/rc.d/init.d grep chkconfig yp* ypbind:# chkconfig: - 13 87 yppasswdd:# chkconfig: - 66 34 ypserv:# chkconfig: - 65 35 ypbind is started before and stopped after ypserv but ypbind depends on ypserv. This makes it difficult to run NIS clients on the same machine as an NIS server (to for example use netgroups). What is the best solution to this problem? I had thought of changing the initscripts to change the start and stop order but I think this might have hidden dependencies with other packages. ------- Additional Comments From landrye@capital.ous.edu 01/15/99 00:58 ------- See also bug 264 URL: http://developer.redhat.com/bugzilla/show_bug.cgi?id=264
I think nfsfs should be started after ypbind too. When you have a setup without a nameserver but with NIS you probably want to use NIS to distribute hostnames. Mounting of nfsfs will fail on boot if you have this setup and want to use hostnames in /etc/fstab
bill: you want to futz with these?
this has been fixed in 5.9; the current starting order is: network portmap ypbind nfsfs random nscd syslog atd crond ...
make that: network portmap ypserv ypbind nfsfs ...