troubleshooting syslog traffic from thin clients to server

[john]

Hi all,

As I flail around looking for reasons why teachers are reporting
general badness with the LTSP experience on Hardy, I note that there
is a lot of
traffic complaining about no syslog server on the servers LTSP facing
interface e.g. 192.168.0.254

I gathered this with:

 tcpdump -i eth4

14:39:19.204412 IP 192.168.0.175.syslog > 192.168.0.254.syslog: SYSLOG
kernel.warning, length: 73
14:39:19.205245 IP 192.168.0.175.syslog > 192.168.0.254.syslog: SYSLOG
kernel.error, length: 64
14:39:19.206023 IP 192.168.0.227.syslog > 192.168.0.254.syslog: SYSLOG
kernel.error, length: 64
14:39:19.206160 IP 192.168.0.175.syslog > 192.168.0.254.syslog: SYSLOG
kernel.warning, length: 73
14:39:19.206590 IP 192.168.0.202.syslog > 192.168.0.254.syslog: SYSLOG
kernel.info, length: 51
14:39:19.207638 IP 192.168.0.175.syslog > 192.168.0.254.syslog: SYSLOG
kernel.error, length: 36
14:39:19.207919 IP 192.168.0.227.syslog > 192.168.0.254.syslog: SYSLOG
kernel.warning, length: 73
14:39:19.209731 IP 192.168.0.227.syslog > 192.168.0.254.syslog: SYSLOG
kernel.error, length: 64
14:39:19.210179 IP 192.168.0.175.syslog > 192.168.0.254.syslog: SYSLOG
kernel.error, length: 118

My understanding was that syslog from thin client to server was an
option under hardy, but not on by default. Can anyone help me decipher
this?

Thanks!

John