I recently noticed on a headless Sparc running 3.0-Generic (from the CD)
that syslogd was consuming 99% of the CPU time. I found a similar closed
bug report where Theo said to run ktrace/kdump, which I did and found
that syslogd was failing on trying to write to /dev/console. I commented
that line out of /etc/syslogd.conf and restarted syslogd. As expected,
it runs normally but I don't get su and alert messages.
Is this a bug? Given that I booted headless, shouldn't /dev/console be
sending output to the terminal I have on serial A? I don't have this
problem on a headless Sparc64, for whatever that's worth.
Thanks.
- Ross
|