Date: Sun, 02 Sep 2012 19:50:44 -0600 From: Ian Lepore <freebsd@damnhippie.dyndns.org> To: attilio@freebsd.org Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: syslog(3) issues Message-ID: <1346637044.1140.566.camel@revolution.hippie.lan> In-Reply-To: <CAJ-FndDeNVcEv5HRBMtQ5ZKa3zdWwt5d4fFPaoXnyV3MS31QDw@mail.gmail.com> References: <CAJ-FndDeNVcEv5HRBMtQ5ZKa3zdWwt5d4fFPaoXnyV3MS31QDw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2012-09-03 at 00:35 +0100, Attilio Rao wrote: > Hi, > I was trying to use syslog(3) in a port application that uses > threading , having all of them at the LOG_CRIT level. What I see is > that when the logging gets massive (1000 entries) I cannot find some > items within the /var/log/messages (I know because I started stamping > also some sort of message ID in order to see what is going on). The > missing items are in the order of 25% of what really be there. > > Someone has a good idea on where I can start verifying for my syslogd > system? I have really 0 experience with syslogd and maybe I could be > missing something obvious. There's a chance this PR about syslogd incorrectly calculating socket receive buffer sizes is related and the patch attached to it could fix it... http://www.freebsd.org/cgi/query-pr.cgi?pr=1604331 I filed the PR long ago, if the patches have drifted out of date I'll be happy to re-work them. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1346637044.1140.566.camel>