From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 2 23:35:26 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 BD2C8106566B for ; Sun, 2 Sep 2012 23:35:26 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3D3D18FC0C for ; Sun, 2 Sep 2012 23:35:25 +0000 (UTC) Received: by lage12 with SMTP id e12so4000020lag.13 for ; Sun, 02 Sep 2012 16:35:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=hN6wQr/V4T8dUHJP9y/OgXfSR5XzRlOwmyBqhSkM/Vk=; b=LfTVDvXUTtwmsh8dRPVswsvwkqEVAiwxr+vzHSqR8NGfY30HeG+hsOoEuyRgzhELNi mlD4Wnf82BEeoGcYnBS6nGrQDdbI7P4doEL0r1bTV00d8AWvQRhZ8rOROaYuPiSL6eEk Hrj3fgCMZWlMk1x+KECbuAI4BR9uST7VrDr4sO3uFUXzUgan2Ty9bCtjds2JPi31+mHw XLXSFA3sV4vmWSCfv8oPP2fXdLQOA10HqZeNmgYXb7aVfNah7+3WLcNZzVJZbuGT15ZO vXl7CyVa79uWeyV2vTJdDWLKcwT7n00DTEVziPvOKS9dyMm5WQyZvDqHCZaiH6shr1dU hCow== MIME-Version: 1.0 Received: by 10.112.83.97 with SMTP id p1mr4858975lby.94.1346628924693; Sun, 02 Sep 2012 16:35:24 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.112.102.39 with HTTP; Sun, 2 Sep 2012 16:35:24 -0700 (PDT) Date: Mon, 3 Sep 2012 00:35:24 +0100 X-Google-Sender-Auth: tF5Jq95IIGuNu0WBbnc42G7j3zI Message-ID: From: Attilio Rao To: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 Subject: syslog(3) issues X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Sep 2012 23:35:26 -0000 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. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein