Bug 553 - ypserv starts after ybind
ypserv starts after ybind
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: ypserv (Show other bugs)
5.2
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1998-12-21 15:00 EST by Jay Berkenbilt
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1998-12-21 15:23:26 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jay Berkenbilt 1998-12-21 15:00:28 EST
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 15:23:59 EST
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.

Note You need to log in before you can comment on or make changes to this bug.