I think that is due to the fact that in /etc/sysconfig/syslog I added -x to the syslog arguments since according to man syslogdOn Mon, Jan 27, 2003 at 02:54:23PM -0500, Alvaro wrote:Jake Schroeder wrote:It seems like you are also having a hostname problem, since your server is unable to resolve the IP address 192.168.100.11 into the workstation's hostname.What can you see in there that shows any problem ? I can ping the ws001 by name or ip address from the server I can ping the server from the workstation nowThe syslog should show you "ws001" instead of "192.168.100.11"; this seems to show that you need a DNS zone called 100.168.192.in-addr.arpa. and a corresponding PTR record in the zone for each host on your LAN. Maybe this isn't the actual cause of the problem, but many programs delay an awful long time when they can't reverse-resolve their hostname. Cheers, - Jake
-x prevents dealocks when nameserver and syslogd are running in the same machine.
Alvaro ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _____________________________________________________________________ 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.freenode.net
