From owner-freebsd-stable@FreeBSD.ORG Tue Nov 4 01:43:49 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 8A3B4106564A for ; Tue, 4 Nov 2008 01:43:49 +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 521108FC14 for ; Tue, 4 Nov 2008 01:43:49 +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 mA41hkLF031828; Mon, 3 Nov 2008 20:43:46 -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 mA41hjaa029665 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Nov 2008 20:43:45 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200811040143.mA41hjaa029665@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 03 Nov 2008 20:43:53 -0500 To: "Poul-Henning Kamp" From: Mike Tancsa In-Reply-To: <7.1.0.9.0.20081103113557.167702f0@sentex.net> References: <43507.1225730046@critter.freebsd.dk> <7.1.0.9.0.20081103113557.167702f0@sentex.net> 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: Tue, 04 Nov 2008 01:43:49 -0000 At 11:48 AM 11/3/2008, Mike Tancsa wrote: >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 ? I tried changing the config so that there is only the fifo log being written to and disabled newsyslog so that syslogd is not getting a HUP signal. The strange thing is that reading from it gives different results?!? Sometimes doing [ps0278]# fifolog_reader all.fifo | wc >From 0 Wed Dec 31 19:00:00 1969 To 1225760679 Mon Nov 3 20:04:39 2008 Read from 1d800 59 413 3068 0[ps0278]# and a exactly for 1min it will show the correct results 0[ps0278]# fifolog_reader all.fifo | wc >From 0 Wed Dec 31 19:00:00 1969 To 1225760538 Mon Nov 3 20:02:18 2008 Read from 0 10765 75995 556816 0[ps0278]# and then go back to showing just a subset for 4 min. I am guessing this coincides with when the flush runs This is a nanobsd image, so /var on /dev/md1 and RELENG_7 from a few days ago I have been running #!/bin/sh i=0 while true do i=`expr $i + 1` logger $i echo $i sleep 1 done and they seem to be there when it shows all the results, but for the most part it just shows a subset ---Mike