Summary: | YPBIND not connecting to NIS server on system startup ; solution provided | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | swietanowski |
Component: | ypbind | Assignee: | Cristian Gafton <gafton> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-01-27 19:21:18 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: |
Description
swietanowski
1999-06-16 09:14:10 UTC
The delay isn't for it to retry; if the server's not there, the server's not there. It's for waiting to make sure that it's actually bound to a server; if the connection is timing out, telling it to try again isn't going to help. Or am I misunderstanding what you're saying? In a synchronized startup of a cluster (or any network) with some NIS server and some clients it may be reasonable for the slave to wait. This is the case I have in my installation. I have a cluster wich is turned on by just one power switch. The clients usually boot faster than the NIS server and they need to wait the additional few seconds. Also, even with the server running, the ypbind did not always succeed in connecting. Adding the forced config reread for ypbind seems to have fixed the problem for me. if you set ypbind to breadcast for an NIS server it will keep retrying every 30 seconds to bind to a new server. |