query logging to FIFO

Kevin Darcy kcd at daimlerchrysler.com
Sat Nov 11 01:31:17 UTC 2000


Syslog typically uses a socket rather than a FIFO for input. Now, whether
syslog can reasonably *write* to a FIFO, I don't know. I can't say in all
my years I've ever tried that. Somehow I doubt that such a Rube Goldberg
arrangement would solve the original poster's (CPU utilitization) problem,
though, unless it could benefit greatly from multiple processors.


- Kevin

jreprogle at worldnet.att.net wrote:

> I assume that bind uses openlog and closelog to log to the syslog. I
> would also assume that bind does not use this api for dumping data into
> a FIFO.
>
> How DOES syslogd do it?
>
>                         Jim Reprogle
>
> In article <02344987900009 at www.gis.net>,
>   Danny Mayer <mayer at gis.net> wrote:
> >
> >               Did you look at how syslogd does it?
> >
> >                               Danny
> >
> > At 09:13 PM 11/9/00 +0000, peek775 at my-deja.com wrote:
> > >I know from looking at the bind source code that
> > >bind closes logfiles after making an entry. Does
> > >it also do this for FIFOs?
> > >
> > >The reason I ask is that I have bind8 logging all
> > >queries to a FIFO. Another process reads from the
> > >FIFO and processes the information in real time. I
> > >have a problem with my code because it seems to be
> > >stuck in a busy loop reading EOF from the FIFO.
> > >This ramps up the CPU utilization of my process.
> > >It looks like this is caused from bind closing the
> > >FIFO for writing, and then re-opening it when it
> > >has more data to dump in.
> > >
> > >Any help???
> > >
> > ><#include stddisclaimer.h>
> > >
> > >
> > >Sent via Deja.com http://www.deja.com/
> > >Before you buy.
>






More information about the bind-users mailing list