Bug 1928 - The ypbind script may not bind the domain in time.
Summary: The ypbind script may not bind the domain in time.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ypbind
Version: 5.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Preston Brown
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-04-01 07:11 UTC by dfm
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-04-01 21:37:43 UTC


Attachments (Terms of Use)

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@area.com> 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.


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