Bug 517570
Summary: | ypbind fails to read configuration file at startup | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bill Kanawyer <bill> |
Component: | ypbind | Assignee: | Karel Klíč <kklic> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 11 | CC: | rvokal, vcrhonek |
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: | 2010-04-15 15:02:54 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
Bill Kanawyer
2009-08-14 18:18:27 UTC
Hi Bill, if you set NISDOMAIN/domainname only in the /etc/sysconfig/network, the ypbind must be started using `service ypbind start`, as /sbin/ypbind program itself does not look into /etc/sysconfig/network, but /etc/init.d/ypbind does. If the domainname is set on the command line, and then /sbin/ypbind is run, it reads /etc/yp.conf. Karel, Thanks for looking into this issue. My memory may be playing tricks on me, but I don't ever recall in 20+ years of working with ypbind implementations that it would fail to read /etc/yp.conf by default even if domainname was not previously set. Assume for the sake of argument that the domainname was previously set (as I believe it was) before running the tests. Therefore please try.... Steps to Reproduce: 0. Run "domainname my.test.domain" to set domain name 1. Run "/sbin/ypbind -c" to confirm /etc/yp.conf is accessed. 2. Run "/sbin/ypbind " to confirm /etc/yp.conf IS NOT accessed. 3. Run "/sbin/ypbind --broadcast" to confirm broadcast functionality works. Are you still unable to reproduce the error in step 2 as reported? If you cannot reproduce the failure under those circumstances, please go ahead and close the case as a no change. Thank you again for your interest. Yes, I am unable to reproduce the error. I already tried the steps as described with the domainname set, and ypbind accessed /etc/yp.conf every time. When the domainname is not set, ypbind without -c does not open /etc/yp.conf, and it prints "domainname not set - aborting." Fedora 12 behaves the same as F-11. Closing now. Please reopen this bug if it still fails on your computer even with the domainname set. |