Bug 837 - ypbind cannot bind to domain on NIS server
Summary: ypbind cannot bind to domain on NIS server
Status: CLOSED DUPLICATE of bug 264
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ypbind (Show other bugs)
(Show other bugs)
Version: 5.2
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-01-15 05:47 UTC by landrye
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-01-15 16:06:29 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description landrye 1999-01-15 05:47:05 UTC 
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.
Comment 1 landrye 1999-01-15 05:58:59 UTC 
See also bug 264

URL: http://developer.redhat.com/bugzilla/show_bug.cgi?id=264
Comment 2 Jeff Johnson 1999-01-15 16:06:59 UTC 
*** This bug has been marked as a duplicate of 264 ***
Note You need to log in before you can comment on or make changes to this bug.