Il giorno Wed, 18 Sep 2002, Delz cos� ha scritto:
|From: Delz <[EMAIL PROTECTED]>
|To: [EMAIL PROTECTED]
|Date: Wed, 18 Sep 2002 08:51:25 +0800
|Subject: [Ltsp-discuss] Ypbind Timed Out ???
|
|Hi,
|
|How do I eliminate ypbind timeouts, I get this message a lot when my
|workstation is connected on my LTSP server. This are the errors generated
|under /var/log/messages
|
|Sep 17 22:10:31 purchasing04 ypbind[365]: broadcast: RPC: Timed out.
|Sep 17 22:11:45 purchasing04 ypbind[365]: broadcast: RPC: Timed out.
|Sep 17 22:12:59 purchasing04 ypbind[365]: broadcast: RPC: Timed out.
|Sep 17 22:14:13 purchasing04 ypbind[365]: broadcast: RPC: Timed out.
|Sep 17 22:15:27 purchasing04 ypbind[365]: broadcast: RPC: Timed out.
|Sep 17 22:16:41 purchasing04 ypbind[365]: broadcast: RPC: Timed out.
|Sep 17 22:17:55 purchasing04 ypbind[365]: broadcast: RPC: Timed out.
|Sep 17 22:19:09 purchasing04 ypbind[365]: broadcast: RPC: Timed out.
|Sep 17 22:20:23 purchasing04 ypbind[365]: broadcast: RPC: Timed out.
|Sep 17 22:21:38 purchasing04 ypbind[365]: broadcast: RPC: Timed out.
|
This does not have to do with LTSP's configuration and neigher does it with
ypbind's, I think. Rather, I think the problem lies in rpc not beeing
available or timing out for some reason. What does rpcinfo -p <server_IP>
tell you?
Sandro
--
Bellum se ipsum alet
La guerra nutre se stessa
Livio, Ab urbe condita, XXXIV,9
-------------------------------------------------------
This SF.NET email is sponsored by: AMD - Your access to the experts
on Hammer Technology! Open Source & Linux Developers, register now
for the AMD Developer Symposium. Code: EX8664
http://www.developwithamd.com/developerlab
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.openprojects.net
