From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 3 02:23:18 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7EB28106564A; Mon, 3 Sep 2012 02:23:18 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 4F0D68FC14; Mon, 3 Sep 2012 02:23:18 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.5/8.14.5) with ESMTP id q832NH8V023013; Sun, 2 Sep 2012 20:23:17 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q832NFNg039620; Sun, 2 Sep 2012 20:23:15 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) From: Ian Lepore To: attilio@freebsd.org In-Reply-To: <1346637044.1140.566.camel@revolution.hippie.lan> References: <1346637044.1140.566.camel@revolution.hippie.lan> Content-Type: text/plain; charset="us-ascii" Date: Sun, 02 Sep 2012 20:23:15 -0600 Message-ID: <1346638995.1140.575.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers Subject: Re: syslog(3) issues X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Sep 2012 02:23:18 -0000 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 -- Ian