Re: logging to a pipe?

That is the option I have running successfully on several nameservers to
give usage data

log to stderr and then
named 2>&1 | /path/logprocessor.pl

I found this from http://www.campin.net/DNS/graph.html, see the comments in
the top of the script at http://www.campin.net/DNS/bind9-query-logger.txt

Peter

"Marten Lehmann" <lehmann@cnm.de> wrote in message
news:cgkget$1v9u$1@sf1.isc.org...
> > Correct. The ARM makes it crystal-clear that the reserved word "file"
> > is followed by a pathname enclosed in double quotes.
>
> Ok so far. But I need to parse the log in realtime and what's easier
> than logging to a script which can select the useful entries and react
> accordingly? A script can receive input continuesly but it's hard to
> read only new entries of a logfile, especially when it's truncated or
> renamed after a certain size. The workaround would be to log everything
> to stderr so I could start named with
>
> /var/tmp/logger.pl
>
> But I don't know where BIND prints the stderr-output, obviously not to
> stderr.
>
> Regards
> Marten
>
>
>