>In the sequens of the boot I got an other error >syslogd: cannot write to remote file handle on 192.168.10.254 > >I've never used remote logging, so I didn't know if I need to configur >something >at the server to allow remot logging and must skiped the apropriate >instruction >in the ltsp documentation. How does I fix this error ?
I have just had to solve this problem myself yesterday, so I can help with this part. On my system the ws001 IP address is 192.168.1.0, the server is 192.168.2.1. On the server the syslogd was invoked with "-m 0 -r -s 192.168.0.0/192.168.0.255". I guess the "192.168.0.255" is the mask, so only 192.168.0 messages were logged (non-existing on our setup). I changed the mask to now log from "-s 192.168.0.0/192.168.255.255", followed by a syslog restart from /etc/init.d, and now it works like a charm. On SuSE the syslog invocation is specfied in /etc/rc.config by changing the SYSLOGD_PARAMS parameter. You can check man syslog for more info. ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _____________________________________________________________________ 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
