syslog(3) issues

Attilio Rao attilio at freebsd.org
Wed Sep 5 18:36:55 UTC 2012


On Mon, Sep 3, 2012 at 3:23 AM, Ian Lepore
<freebsd at damnhippie.dyndns.org> wrote:
> On Sun, 2012-09-02 at 19:50 -0600, Ian Lepore wrote:
>> 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
>>
>
> Oops, I glitched the PR number when I pasted it, this one should be
> correct:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=160433

This patch fixes the problem for me, thanks a lot.

Alexander, do you have any reservation against it? When do you think
the patch can be merged to -CURRENTR?

Thanks,
Attilio


-- 
Peace can only be achieved by understanding - A. Einstein


More information about the freebsd-hackers mailing list