Bug 1928

Summary:	The ypbind script may not bind the domain in time.
Product:	[Retired] Red Hat Linux	Reporter:	dfm
Component:	ypbind	Assignee:	Preston Brown <pbrown>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.2
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	1999-04-01 21:37:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description dfm 1999-04-01 07:11:42 UTC

I've observed that, when ypbind is used in broadcast mode,
other scripts may be run before the ypbind daemon has
received and processed the response to its broadcast
request.

If amd is also being started at boot time, and expects to
obtain one or more mount maps through NIS, it will
effectively give up on those mount maps if it can't get them
on the first try. In that case, it must be stopped and
started anew -- even a restart via SIGHUP won't help.

The fix I adopted involves adding a loop to
/etc/rc.d/init.d/ypbind, after it has invoked "daemon
ypbind", which tries "ypwhich" once every second until that
program returns a nonzero exit status. (The actual patch
will follow by mail once I have a bug number.)

I've encountered this problem on two different machines
running Red Hat 5.2. A quick inspection of the ypbind script
in 5.9 (Starbuck) suggests that it is vulnerable to the same
thing, but I haven't demonstrated that under conditions of
actual use.

------- Email Received From  Dan Martinez <dfm> 04/01/99 03:59 -------

Comment 1 Preston Brown 1999-04-01 21:37:59 UTC

Thanks very much for the fix, it is sane and looks professional.

Fixed in ypbind-3.3-16.