From owner-freebsd-stable@FreeBSD.ORG Mon Nov 3 16:47:55 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC24F106567A for ; Mon, 3 Nov 2008 16:47:55 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id A3CC78FC2A for ; Mon, 3 Nov 2008 16:47:55 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id mA3GlrfP027595; Mon, 3 Nov 2008 11:47:53 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id mA3GlruN025099 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Nov 2008 11:47:53 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200811031647.mA3GlruN025099@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 03 Nov 2008 11:48:00 -0500 To: "Poul-Henning Kamp" From: Mike Tancsa In-Reply-To: <43507.1225730046@critter.freebsd.dk> References: <43507.1225730046@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: freebsd-stable@freebsd.org Subject: Re: fifo log problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 16:47:56 -0000 At 11:34 AM 11/3/2008, Poul-Henning Kamp wrote: >In message <200811031547.mA3FlVVs024666@lava.sentex.ca>, Mike Tancsa writes: > > >Seems to work fine with cat > >Ok, and the loss is not from one end, it is random records in >the middle ? Yes, they seem to initially get written and then tail off for some reason. I am not sure why. Actually, if I SIGHUP syslogd, it seems to make a difference, in that I can generally see when newsyslog sig HUPs syslog to do log rotation. Perhaps this is confusing things ? e.g. 1225628270 Nov 2 07:17:50 st32278 ovpn-kit[1047]: Initialization Sequence Completed 1225641602 Nov 2 11:00:02 st32278 syslogd: restart 1225641608 Nov 2 11:00:08 st32278 ppp[927]: tun0: Chat: deflink: Redial timer expired. In this snippet the last entry was 07:17 for some reason and then the SIGHUP from newsyslog seems to wake things up for some reason. ---Mike >-- >Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 >phk@FreeBSD.ORG | TCP/IP since RFC 956 >FreeBSD committer | BSD since 4.3-tahoe >Never attribute to malice what can adequately be explained by incompetence.