Red Hat Bugzilla – Bug 249520
ypbind initscript does not write error message when DOMAINNAME cannot be set
Last modified: 2009-01-20 16:48:25 EST
Description of problem:
The initscript for ypbind checks whether DOMAINNAME is set and has other value
than "(none)". If not, it checks whether NISDOMAIN is not empty and sets
DOMAINNAME to NISDOMAIN value in that case. Otherwise it will silently quit
with exit code 1, leaving user no clue what has failed.
For troubleshooting purposes, failures should be logged, as suggested in bug
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
ypbind is not an approved package for 5.2. I'll set "fast". Steve, if this is
not feasible for FasTrack, then close or defer it.
Since this bugzilla was filed against pre-RHEL 5.1 and was not addressed in 5.2
Beta via FasTrack, moved to 5.3 FasTrack.
Created attachment 302333 [details]
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.