Syslogd and serial console bug?

[Santos]

Hi all.

Bug bin/8865 strikes again?

I have a FreeBSD 4.8 Release machine. After sometime, the logs just 
aren't modified, syslogd just doesn't log. The last entry
on /var/log/messages is from may 15.

Could this be caused to use a serial console (-P on /boot.config, no 
keyboard attached) to access the machine? There was once a time that 
when i Control^D'ed on the serial console and  a lot of messages, 
obviously threw by syslogd, scrolled by, messages that should be loged 
to the console and /var/log/messages.

Some output:

# syslogd -d -ss
off & running....
init
cfline("*.err;kern.debug;auth.notice;mail.crit          /dev/console", 
f, "*", "*")


Killed syslogd and commented out the line 
"*.err;kern.debug;auth.notice;mail.crit          /dev/console" on 
/etc/syslogd.conf, and guess what...

# syslogd -d -ss

**insert explosion of messages from may 15, may 16 and may 17 here!**


So it probably was caused by the serial console :). Doesn't the -P flag 
on /boot.config takes care of "telling" the rest of the system that now 
the console is a serial one?  Having ttyd1 on /etc/ttys doesn't work for 
me, had to use cuaa1 instead, to have a working serial console. Maybe 
this cause the bug?


Santos