Red Hat Bugzilla – Bug 61857
/etc/init.d/ypbind start/stop output buggy
Last modified: 2007-04-18 12:41:09 EDT
Description of Problem:
If /etc/init.d/ypbind start can't find the ypserver (?), it overwrites the
output on the screen so that you don't know it's failed.
Version-Release number of selected component (if applicable): ypbind-1.10-3
Steps to Reproduce:
1. Install RH with 'medium firewall' and 'use NIS' in the install.
2. meet problems with NIS. Try to restart ypbind in case it's that.
3. /etc/init.d/ypbind stop produces the right output:
Shutting down NIS services.... [ FAILED ]
4. /etc/init.d/ypbind start produces two lines. The first is:
"Listening for an NIS domain server..." and then it flashes up [ FAILED ].
Then it overwrites this with "Shutting down NIS services", doesn't overwrite
the rest of the first message, so to get "Shutting down NIS services: server"
and finishes with [ OK ]
So unless you're watching as it happens, you'll think the 'start' worked.
The bug here is the buggy message: the firewall/no warning in the installer
will go somewhere else when I figure it out.
Should be fixed in ybind-1.10-7, soon in a rawhide near you.