On Sun, 05 Sep 2010, Joost Kraaijeveld wrote: > I have found the reason: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585395 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586156 > > The first also has a workaround/patch that works for me.
Do yourself a huge favour, and switch to rsyslog... klogd can lose information for a number of reasons, it is unreliable, and it has always been unreliable IME. I've seen it lose communication with syslogd on various systems in the past several years. As soon as rsyslogd became stable enough for production use, we switched all of our systems away from the syslogd+klogd combo and never had any more issues. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100905131715.gd15...@khazad-dum.debian.net
