Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 553

Summary: ypserv starts after ybind
Product: [Retired] Red Hat Linux Reporter: Jay Berkenbilt <ejb>
Component: ypservAssignee: David Lawrence <dkl>
Status: CLOSED WORKSFORME QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2CC: ejb
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1998-12-21 20:23:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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.