Date: Mon, 03 Sep 2012 12:42:28 +0430 From: Hooman Fazaeli <hoomanfazaeli@gmail.com> To: attilio@FreeBSD.org Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: syslog(3) issues Message-ID: <5044666C.3030005@gmail.com> 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 9/3/2012 4:05 AM, 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. > > > Is not it caused by syslogd compression? As you may know syslogd compresses consecutive identical messages into one message like "last message repeated N times". The -cc option disables compression.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5044666C.3030005>