I just spent an hour trying to figure out why our clients couldn't log to the syslog-ng server anymore. To make a long story short, a patch had replaced the original syslogd start script so both daemons were started. syslogd started first and managed to bind to udp port 514 so syslog-ng never even saw the messages. It didn't complain over not being able to bind the port though -- I would have expected it to say "failed to bind udp port 514" or something like that. Think you could make syslog-ng whine more if it can't bind the port? OK, now all I have left to fix is the raid system, the backbone switch, our two printers on this floor, and the backup system. I won't be going to bed early tonight... -- ___ . . . . . + . . o _|___|_ + . + . + . . Per Olofsson, konstnär o-o . . . o + MagerValp@cling.gu.se - + + . http://www.cling.gu.se/~cl3polof/