[1010] in Release_7.7_team
Jonathon Weiss: syslogd
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Wed Jun 18 03:10:38 1997
From: Jonathon Weiss <jweiss@MIT.EDU>
To: release-team@MIT.EDU
Date: Wed, 18 Jun 1997 03:10:33 EDT
Eit. I wanted to talk about this at the meeting today. Mike, could
you please put it on the agenda for next week, unless people want to
start replying by mail. I'll try to find a stand in to go to the
meeting.
Jonathon
------- Forwarded Message
Received: from SOUTH-STATION-ANNEX.MIT.EDU by po10.MIT.EDU (5.61/4.7) id AA03222; Mon, 16 Jun 97 02:22:37 EDT
Received: from DELIVERATOR.MIT.EDU by MIT.EDU with SMTP
id AA18928; Mon, 16 Jun 97 02:22:32 EDT
Received: from jweiss@localhost
by deliverator.MIT.EDU (8.8.5/4.7.4)
id CAA23655; Mon, 16 Jun 1997 02:22:31 -0400 (EDT)
Message-Id: <199706160622.CAA23655@deliverator.MIT.EDU>
From: Jonathon Weiss <jweiss@MIT.EDU>
To: release-team@MIT.EDU
Cc: ops@MIT.EDU, testers@MIT.EDU
Subject: syslogd
Date: Mon, 16 Jun 1997 02:22:31 EDT
Sender: jweiss@MIT.EDU
Ops recently realized that we are not getting reboot syslogs for our
solaris machines logged centrally. This is particularly probalematic
for our servers, but it would also be nice if cluster machines logged
reboots. Based on some tests we have run, it appears that the sun
syslogd simply does not log the reboot messages, locally, remotely, or
otherwise. However, the athena syslogd seems to do so (although it
ends up with a somewhat garbled message, that may be what it is being
given. What are the possibilities of getting suns to run the
athenized syslogd?
Actually, while composing this, it occured to me that we might be able
to solve the problem by simply having the Athena rc script log
something at a level that will go to the remote logger. eg.:
/usr/bin/logger -p user.notice Yo, I am rebooting.
Ted, I have the feeling I'm forgetting somethign. Will this, in fact,
be sufficient for us?
Jonathon
------- End of Forwarded Message
