Martin Schulze writes ("Re: syslogd mysteriously stops logging to tty8"):
> Martin Schulze wrote:
> > Is this still the case? We've found a bug that caused syslogd to
> > write into wrong files under some race conditions. This was fixed in
> > 1.3-18 and I suppose this also solves your problem. Could you close
> > the bug if you agree?
I haven't seen these symptoms for some time now so I think that must
have been the problem.
> there have been many improvements and bugfixes to syslogd since then.
> Do you mind trying the current CVS version and see if the bug still
> exists? If not, checking the current version in etch may be helpful
> as well.
Sorry for failing to respond earlier, but since I don't have a setup
which reproduces the bug now, and your bug description sounds like the
fault I had, I'm closing the bug.
Ian.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
