loggin in a chrooted environment.

[Bill Larson]

As long as you specify a complete directory path for your log file(s), these
paths must exist in the chroot environment.  For example, you must have a
/opt/chroot/opt/chroot/var/log directory for the log.msgs file.

I suspect that what you really want is something like "/var/log/log.msgs"
for you "my_file" channel file.

Remember, when you are running in a chroot environment, your base directory
that you run out of (/opt/chroot) will be considered to be your root (/)
directory and everything is identified in relation to that new root directory.

Bill Larson

Fabiola Caceres wrote:
> 
> 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