Sebastian, I've never seen this error before, I mean the one from syslogd. How is syslogd being run on your server? It is launched by a script called rcsyslogd (SuSE thing). Do a 'vi `which rcsyslogd`' and look for where the daemon is being started. What command-line options are there? Try restarting the daemon: 'rcsyslogd stop; rcsyslogd start'. Oh, and is 192.168.0.2 your syslog server?
As for the XF86_S3 error, it looks like you put XSERVER = XF86_S3 in lts.conf, but you don't have the LTSP XFree86 3.3.6 S3 Xserver installed. Either install it or change your lts.conf entry to read just "s3" instead of "XF86_S3". This will use the LTSP XFree86 version 4.x Xserver and tell it to use the s3 driver module. Jason > From: Sebastian Schulze <[EMAIL PROTECTED]> > Date: Fri, 12 Jul 2002 18:21:01 +0200 > Subject: [Ltsp-discuss] Problem with "start_ws" or "syslogd" or whatever? > > I have installed the ltsp-packages on an old PII/333/SuSE 7.3. > > After solving some minor problems with the nfs and dhcp I have still an=20 > important problem on the first (and at this time the only) client (PI/100= > ,=20 > 10Mbit network): > > The client is booting the kernel, but in runlevel 5 the X-Server is not=20 > starting. > > The last messages on the screen are: > > Building the XF86config file > Building the start_ws script > Starting syslogd > syslogd: syslogd: cannot write to remote file handle on192.168.0.2:514 > /temp/start_ws: /usr/X11R6/bin/XF86_S3: no such file or directory [10 tim= > es] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Gadgets, caffeine, t-shirts, fun stuff. http://thinkgeek.com/sf _____________________________________________________________________ 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
