[12360] in Athena Bugs
Re: Solaris crash...
daemon@ATHENA.MIT.EDU (jweiss@MIT.EDU)
Wed Aug 10 11:59:05 1994
From: jweiss@MIT.EDU
Date: Wed, 10 Aug 1994 11:58:43 +0500
To: Theodore Ts'o <tytso@MIT.EDU>, bugs@MIT.EDU
Cc: testers@MIT.EDU, jweiss@MIT.EDU
In-Reply-To: [2690] in testers
P.S. I tried looking for logs, for a panic message or something else,
and couldn't find anything in /usr/adm. Does Solaris log messages
anywhere else?
Executive summary: On Solaris under 7.6 long syslogs were bitbucketed,
under 7.7 ALL syslogs are bitbucketed.
As far as I can tell syslogs worked on the-other-woman (my
SPARCclassic) for less than a week, in the middle of 7.7 release
testing. Why it worked then I don't know. It just started working
one day, and stopped when I took the next letter release. When
syslogs are not working, no data seems to get through.
I know I've metioned this to some people, but I haven't submitted a
formal bug report. Because this makes it significantly harder to
debug some things, to say nothing of failing to warn me of someone
trying to break into my machine, I'd like to see it fixed RSN. JIC,
please consider this a formal bug report about syslog on 7.7 Suns.
Jonathon
