|Summary:||ypserv starts after ybind|
|Product:||[Retired] Red Hat Linux||Reporter:||Jay Berkenbilt <ejb>|
|Component:||ypserv||Assignee:||David Lawrence <dkl>|
|Status:||CLOSED WORKSFORME||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||1998-12-21 20:23:26 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Jay Berkenbilt 1998-12-21 20:00:28 UTC
Although not common, it is possible and sometimes desirable to run ypbind and ypserv on the same machine. /etc/rc.d/init.d/ypserv is configured so that ypserv is started with S65, but ypbind is started with S13. ypserv must be started first if the two services run on the same machine. On my machine, I start ypserv with S12ypserv. Also, ypbind should be stopped before ypserv is stopped in order for shutdown to be clean.
Comment 1 David Lawrence 1998-12-21 20:23:59 UTC
This is a valid argument but it doesn't really hurt anything. The ypbind daemon will startup and fail but it will keep trying unitl a server is found. Therefore after the ypserv daemon starts then ypbind will complete it's initialization. I will recommend to the developer in charge of ypbind to make this change.