Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 84855 - ypbind startup script should wait for pcmcia to bring up network
Summary: ypbind startup script should wait for pcmcia to bring up network
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ypbind
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-02-22 03:51 UTC by Eugene Kanter
Modified: 2007-04-18 16:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-01-02 18:42:58 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Eugene Kanter 2003-02-22 03:51:53 UTC 
Description of problem:

For laptop configuration /etc/rc.d/init.d/ypbind starts soon after pcmcia.
Inserting "ifconfig" in ypbind shows that eth0 is not up when ypbind starts.

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

ypbind-1.11-4

How reproducible:

always

Steps to Reproduce:
1. install on a notebook, configure DHCP, run authconfig and enable NIS.
2. reboot.

    
Actual results:

ypbind can not find NIS server.

Expected results:

ypbind finds NIS server.

Additional info:

"sleep 10" helps, but probably more intelligent solution is needed.
Comment 1 Bill Nottingham 2006-08-05 03:52:32 UTC 
Red Hat apologizes that these issues have not been resolved yet. We do want to
make sure that no important bugs slip through the cracks.

Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc.
They are maintained by the Fedora Legacy project (http://www.fedoralegacy.org/)
for security updates only. If this is a security issue, please reassign to the
'Fedora Legacy' product in bugzilla. Please note that Legacy security update
support for these products will stop on December 31st, 2006.

If this is not a security issue, please check if this issue is still present
in a current Fedora Core release. If so, please change the product and version
to match, and check the box indicating that the requested information has been
provided.

If you are currently still running Red Hat Linux 7.3 or 9, please note that
Fedora Legacy security update support for these products will stop on December
31st, 2006. You are strongly advised to upgrade to a current Fedora Core release
or Red Hat Enterprise Linux or comparable. Some information on which option may
be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/.

Any bug still open against Red Hat Linux 7.3 or 9 at the end of 2006 will be
closed 'CANTFIX'. Again, if this bug still exists in a current release, or is a
security issue, please change the product as necessary. We thank you for your
help, and apologize again that we haven't handled these issues to this point.
Comment 3 Bill Nottingham 2007-01-02 18:42:58 UTC 
Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc.
f you are currently still running Red Hat Linux 7.3 or 9, you are strongly
advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux
or comparable. Some information on which option may be right for you is
available at http://www.redhat.com/rhel/migrate/redhatlinux/.

Closing as CANTFIX.
Comment 4 Eugene Kanter 2007-01-02 20:54:39 UTC 
Bill, I am running Fedora core 6 currently. I'll need to recreate environment
and test if this is still applicable.

But generally speaking ypbind startup script must be more robust and should not
take a very long time waiting for NIS server reply if NIS server is not available.
Note You need to log in before you can comment on or make changes to this bug.