Bug 244081 - busted patch? ypbind-mt-1.12-disconnect-logging.patch
Summary: busted patch? ypbind-mt-1.12-disconnect-logging.patch
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: ypbind   
(Show other bugs)
Version: 3.9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Steve Dickson
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-06-13 17:42 UTC by Jack Neely
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 18:36:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jack Neely 2007-06-13 17:42:25 UTC
Description of problem:
My Beowulf uses NIS and finds the NIS servers via a broadcast on the internal
network.  This morning, NIS was horribly, horribly broken.

With the -d option for debug, ypbind segfaults.

# ypbind -d
parsing config file
No entry found.
add_server() domain: beowulf, broadcast
[Welcome to ypbind-mt, version 1.12]

do_broadcast() for domain 'beowulf' is called
Answer for domain 'beowulf' from unknown server ''
Segmentation fault

Without the debug option ypbind clone()'s itself as a daemon and then the new
process segfaults.

This was a fun way to find my Beowulf this morning.  I've gone back to
1.12-5.21.9 and am not having problems.  The only change I see is the logging patch.

Version-Release number of selected component (if applicable):

Comment 1 RHEL Product and Program Management 2007-10-19 18:36:17 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

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