loggin in a chrooted environment.

Mark.Andrews at nominum.com Mark.Andrews at nominum.com
Mon May 7 01:59:13 UTC 2001


	The "null" channel is built in and should not be redefined,
	also "drfault" should be "default" and there should only
	be one "category default" declaration.

	Mark

> 
> Hi,
> I need help. When I tried to kill named to turn on logging I get an error
> and named stops. I'm running chrooted named and I start with the following
> command:
> #./named -u named -t /opt/chroot/
> 
> # pgrep named
> 28514
> # kill -USR1 28514
> # couldn't open null channel
> 
> -------------------------
> Here is my logging statement from my named.conf
> 
>         loggin {
>                  channel my_file {
>                         file "/opt/chroot/var/log/log.msgs";
>                         severity dynamic;
>                         print-category yes;
>                         print-severity yes;
>         };
>         category drfault { default_syslog; my_file; };
>         category panic  { default_syslog; my_file; };
>         category packet { /opt/chroot/var/log/my_file; };
>         category eventlib       { my_file; };
>         category queries        { my_file; };
>         category default        { null; };
>                 channel null { null; };
> };
> 
> Please help,
> thank you,
> 
> Fabiola Caceres
> InfiNet Hostmaster
> Systems Group
> fabiola at infi.net
> (757)624-2284
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com


More information about the bind-users mailing list