[996] in Release_7.7_team
Re: syslogd
daemon@ATHENA.MIT.EDU (John Hawkinson)
Mon Jun 16 09:59:16 1997
Date: Mon, 16 Jun 1997 09:59:10 -0400
To: "Richard Basch" <basch@lehman.com>
Cc: release-team@MIT.EDU, op@MIT.EDU, testers@MIT.EDU, bugs@MIT.EDU
From: John Hawkinson <jhawk@MIT.EDU>
Richard quotes me:
| > / I'm not sure whether this is bug in /dev/log (log(7)) or something
| > / else. This behavior of queueing syslogs is not mentioned in log(7),
| > / syslogd(1m), syslog(3), or anywhere else I looked.
|
| First, Solaris uses SYSV-style logging. In other words, /dev/log is a
| compatibility feature for BSD-style programs, but a syslogd based on
| /dev/log will not receive all the messages. The kernel logs its
| messages using prioritized message queues. If the Athena syslogd does
| not "speak" this style of syslogs, I think you will find that you will
| be omitting all the kernel logs.
I think perhaps you're a bit confused by my terminology. /dev/log is
not a compatibility interface -- if you attempt to use /dev/log in the
BSD fashion you will fail miserably, completely, and entirely. The
zephyr syslogd used to do so before I added support for Solaris.
/dev/log under Solaris is indeed a STREAMS interface and must be
open()ed, then must be configured with ioctl() for I_STR, and read
with getmsg(). The athena/zephyr syslogd does this.
--jhawk
