| OK, if anyone is still interested in this. :P My syslogd has once again
| stopped logging, and I have a ktrace.  syslogd is taking up almost all
| my CPU.  I wasn't thinking to check whether that was the case last time,
| but the other symptoms appear to be exactly the same as the case I
| mention below.  I am now running the released NetBSD 1.5.1 on i386.

Yes. I have this problem. In my site there are 8+ NetBSD servers
running 1.5.1 (5 running 1.5 yet).(all i386)

Every month there are two or three events of "syslogd stopped".
I dont know the reason of this... In this case, I can not
execut "shutdown -r now" because I need to have root privileges
and the "su(1)  command" waits forever after the password.
It seems like waiting to write the "su message" in the logs.

All I do is press the reset button... When the server
start up, all works fine again.

How can I do in order to find an explanation
of the problem? (and solve it)

Thanks a lot.

Heron Gallegos
----------------------------------------------------
All servers run "/usr/sbin/syslogd -s"
My router to internet have a line like this:
access-list 101 permit udp any mynet mymask neq syslog
(I wrote this rule thinking "the problem may be an attack")