home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!yale!gumby!destroyer!mudos!mudos!not-for-mail
- From: mju@mudos.ann-arbor.mi.us (Marc Unangst)
- Newsgroups: comp.unix.pc-clone.32bit
- Subject: Bug in syslogd under Esix 4.0.3
- Date: 30 Dec 1992 04:50:23 -0500
- Organization: The Programmers' Pit Stop, Ann Arbor MI
- Lines: 20
- Distribution: world
- Message-ID: <1hrrcvINN737@mudos.ann-arbor.mi.us>
-
- There seems to be a fairly significant bug in syslogd under Esix
- 4.0.3. After writing a log message to a file, syslogd does not flush
- the log message from its buffer before writing the next log message.
- Thus, each time it writes out a subsequent log message, all the
- messages previous to that message are rewritten as well. Naturally,
- this makes for a rather rapidly-growing logfile.
-
- Has anybody fixed this? Has anybody ported another syslogd to Esix?
- I just started running INN on this system, and INN does almost all of
- its logging through syslogd. Thus, I'm somewhat desperate to find a
- syslogd that works correctly...
-
- (And yes, I did try hacking on the syslogd provided with INN. It
- doesn't work properly with SVR4 STREAMS syslog device.)
-
- --
- Marc Unangst, N8VRH | "Of course, in order to understand this you
- mju@mudos.ann-arbor.mi.us | have to remember that the nucleus of the atom
- | is squishy."
- | -W. Scheider, from a Physics lecture
-