Logging options for chrooted bind on Solaris 7

[Brad Knowles]

At 10:26 PM +0000 6/28/01, Mike Iglesias wrote:

>  I'm working on chrooting bind on a Solaris 7 system.  What are people doing
>  for logging?  Are you logging to a file or using some way to get syslog
>  to work in the chrooted environment?  Solaris syslogd doesn't have
>  a -a option to monitor another socket, so using syslog will be difficult
>  or impossible.

	Logging to a file is usually the best option -- syslog can lose 
up to 75% or more of all data on a busy network, due to the fact that 
it uses UDP as a transport mechanism.  Moreover, syslog also flushes 
writes after every line written, which usually seriously trashes the 
performance of the server, if syslog is being heavily used.

	Logging directly to a file avoids all these problems.

-- 
Brad Knowles, <brad.knowles at skynet.be>

/*        efdtt.c  Author:  Charles M. Hannum <root at ihack.net>          */
/*       Represented as 1045 digit prime number by Phil Carmody         */
/*     Prime as DNS cname chain by Roy Arends and Walter Belgers        */
/*                                                                      */
/*     Usage is:  cat title-key scrambled.vob | efdtt >clear.vob        */
/*   where title-key = "153 2 8 105 225" or other similar 5-byte key    */

dig decss.friet.org|perl -ne'if(/^x/){s/[x.]//g;print pack(H124,$_)}'