Re: fifo log problem
- From: "Poul-Henning Kamp" <phk@xxxxxxxxxxxxxx>
- Date: Mon, 10 Nov 2008 07:16:31 +0000
In message <200811040143.mA41hjaa029665@xxxxxxxxxxxxxx>, Mike Tancsa writes:
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
To 1225760679 Mon Nov 3 20:04:39 2008From 0 Wed Dec 31 19:00:00 1969
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
To 1225760538 Mon Nov 3 20:02:18 2008From 0 Wed Dec 31 19:00:00 1969
Read from 0
10765 75995 556816
0[ps0278]#
I could fear that you have two fifologs running at the same time,
possibly as a result of syslogd doing something strange on sighup...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@xxxxxxxxxxx | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: fifo log problem
- From: Mike Tancsa
- Re: fifo log problem
- References:
- Re: fifo log problem
- From: Mike Tancsa
- Re: fifo log problem
- Prev by Date: Re: libzfs: vmem.h missing
- Next by Date: Re: php-cgi frozen with sbwait when SMP enable
- Previous by thread: Re: fifo log problem
- Next by thread: Re: fifo log problem
- Index(es):
Relevant Pages
|