Bug 61857 - /etc/init.d/ypbind start/stop output buggy
Summary: /etc/init.d/ypbind start/stop output buggy
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ypbind   
(Show other bugs)
Version: 7.3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2002-03-25 11:10 UTC by Telsa Gwynne
Modified: 2007-04-18 16:41 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-03-25 11:10:59 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 Telsa Gwynne 2002-03-25 11:10:55 UTC
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

How Reproducible:


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.

Comment 1 Alexander Larsson 2002-03-25 21:17:39 UTC
Should be fixed in ybind-1.10-7, soon in a rawhide near you.

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