How did you solved the syslogd problem ?
You're right, here's the explanation:
THIS REGARDS SUSE 9.1 AND LTSP-4
The problem may be distribution-specific, so my solution may not work on other systems:
The syslogd must be allowed to accept data from other machines. The easiest way is to give it the mask for the subnet your clients are in. To do so, just fire up Yast, go to System, Sysconfig Editor, choose System and Logging.
You will find a variable called SYSLOGD_PARAMS. Here you insert something like "-r -s 192.168.10.0/24" (in my case, as 192.168.10... is my subnet for the clients).
I found this hint in the German www.linux-club.de LTSP forum.
Regards Rolf
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_____________________________________________________________________
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
