Date: Wed, 11 Dec 1996 01:40:02 -0800 (PST) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-bugs Subject: Re: bin/2191: syslogd stops logging after several hours of load - FDIV048 Message-ID: <199612110940.BAA29597@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/2191; it has been noted by GNATS. From: J Wunsch <j@uriah.heep.sax.de> To: uhclem@nemesis.lonestar.org Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/2191: syslogd stops logging after several hours of load - FDIV048 Date: Wed, 11 Dec 1996 09:54:09 +0100 (MET) As uhclem@nemesis.lonestar.org wrote: > (I had warned management against putting 2.2-Alpha in a production > environment, but they did it anyway because they wanted to write the > logs on write-once CDs from time to time. ) (You could still use the 2.2 machine just for the CD-R part. You gotta run mkisofs on the logs anyway, so this can be done across an NFS mount.) > >How-To-Repeat: > > I tried to come up with a simplified way to reproduce this. I tried > Despite letting this run for 24 hours, syslogd continued to log > as it should. Well, then chances are pretty low that anybody else than you will ever be able to reproduce and debug it. So unless it will be fixed incidentally as a side-effect of another fix, the bug will remain forever. :-( Is there any chance that you run a debugger on syslogd once it stops writing? (Remember, you can use the `attach' command in gdb to attach to a running process.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612110940.BAA29597>