Subject: re: Is this kernel fault OK?
To: Simon Burge <email@example.com>
From: matthew green <firstname.lastname@example.org>
Date: 06/27/2003 10:48:50
My first thought is "is it really truly syslogd?" It's not obvious from
above whether or not the syslogd message was immediately before the
trap or some time earlier in the past. Is it reproducable? If so, how
stable is the box without syslogd running?
i've seen sparc64 crash when syslogd started up .... it was a bug
that got squashed a while ago.