Re: Possible serious problem with the newest sysklogd?

1998-10-18 Thread Gregory S. Stark
Martin Schulze [EMAIL PROTECTED] writes: You'll also find the new version which has the offending code removed: ftp://ftp.infodrom.north.de/pub/people/joey/debian/sysklogd_1.3-28_i386.deb Does -29 have it reinserted? I'm seeing the same problem. greg

Re: Possible serious problem with the newest sysklogd?

1998-10-18 Thread Martin Schulze
Gregory S. Stark wrote: You'll also find the new version which has the offending code removed: ftp://ftp.infodrom.north.de/pub/people/joey/debian/sysklogd_1.3-28_i386.deb Does -29 have it reinserted? I'm seeing the same problem. Yes. That was the intention - which failed again. *sigh*

Re: Possible serious problem with the newest sysklogd?

1998-10-18 Thread Stephen Crowley
On Sun, Oct 18, 1998 at 12:36:37PM +0200, Martin Schulze wrote: Could you try the next prelimnary version? ftp://ftp.infodrom.north.de/pub/people/joey/debian/sysklogd_1.3-29.2_i386.deb Great! This seems to fix it, no problems here. -- Stephen Crowley Debian GNU/Linux Developer

Possible serious problem with the newest sysklogd?

1998-10-15 Thread Seth M. Landsman
Hmm, so I just updated the syslogd on my system yesterday (using dselect, slink 2.1 i386 system). Then I stopped receiving mail completely via qmail. About 4 hours later I realized I hadn't received any mail for the day and saw no qmail entries in my logs. I restarted qmail and

Re: Possible serious problem with the newest sysklogd?

1998-10-15 Thread Martin Schulze
Seth M. Landsman wrote: Hmm, so I just updated the syslogd on my system yesterday (using dselect, slink 2.1 i386 system). Then I stopped receiving mail completely via qmail. About 4 hours later I realized I hadn't received any mail for the day and saw no qmail entries in my logs.

Re: Possible serious problem with the newest sysklogd?

1998-10-15 Thread Martin Schulze
Seth M. Landsman wrote: On Thu, Oct 15, 1998 at 04:59:42PM +0200, Martin Schulze wrote: Seth M. Landsman wrote: Hmm, so I just updated the syslogd on my system yesterday (using dselect, slink 2.1 i386 system). Then I stopped receiving mail completely via qmail. About 4 hours later

Re: Possible serious problem with the newest sysklogd?

1998-10-15 Thread Martin Schulze
Seth M. Landsman wrote: I've traced the problem to splogger blocking. If I kill splogger, everything is happy, but no qmail messages get logged. The problem is that no new unix domain sockets are accept()'ed. I don't know why. Furthermore, I've found that qmail writes to the log