string
string
string
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Action<br />
To workaround, increase the file descriptor limit in the yp startup script,<br />
/etc/rc2.d/S71rpc. Add this to the script before ypserv is started:<br />
ulimit -n 256<br />
ypbind[int]: NIS server for domain<br />
"<strong>string</strong>" OK<br />
Cause<br />
This message appears after an "NIS server not responding" message to indicate that<br />
ypbind(1M) is able to communicate with an NIS server again.<br />
Action<br />
Proceed with your work. This message is purely informational.<br />
ypbind[int]: NIS server not responding<br />
for domain " <strong>string</strong> "; still trying<br />
Cause<br />
This means that the NIS client daemon ypbind(1M) cannot communicate with an<br />
NIS server for the specified domain. This message appears when a workstation<br />
running the NIS naming service has become disconnected from the network, or<br />
when NIS servers are down or extremely slow to respond.<br />
Action<br />
If other NIS clients are behaving normally, check the Ethernet cabling on the<br />
workstation that is getting this message. On SPARC machines, disconnected network<br />
cabling also produces a series of "no carrier" messages. On x86 machines, the above<br />
message might be your only indication that network cabling is disconnected.<br />
If many NIS clients on the network are giving this message, go to the NIS server in<br />
question and reboot or repair as necessary. To locate the NIS server for a domain, run<br />
Alphabetical Message Listing 211
Change language