Re: why bind unable to find log files

2011-06-13 Thread Eivind Olsen
kshitij mali wrote: > Jun 13 11:00:23 relay named[14508]: logging channel 'resolver_file' file > '/var/log/resolver.log': permission denied > Jun 13 11:00:23 relay kernel: audit(1307943023.256:7): avc: denied { > append } for pid=14511 comm="named" name="resolver.log" dev=cciss/c0d0p2 > ino=139

Re: why bind unable to find log files

2011-06-12 Thread kshitij mali
Hi Warren, please see the error message in /var/log/messages , has i have created the dir log in the chroot /var/named/chroot/var and created the file resolver.log and also changed the owner ship of file as well as the dir log to named === Jun 13 11:00:23 relay nam

Re: why bind unable to find log files

2011-06-11 Thread Robert Spangler
On Saturday 11 June 2011 09:53, the following was written: > On Jun 11, 2011, at 4:22 AM, kshitij mali wrote: > > Hi Mark , > > > > Thanks of taking intreast in my case , yes the rhel4 default bind named > > service is running in chroot jail , know tell we what config changes do > > i nedd

Re: why bind unable to find log files

2011-06-11 Thread Warren Kumari
On Jun 11, 2011, at 4:22 AM, kshitij mali wrote: > Hi Mark , > > Thanks of taking intreast in my case , yes the rhel4 default bind named > service is running in chroot jail , know tell we what config changes do i > nedd to change. > Create a directory inside the chroot jail called var/log/

Re: why bind unable to find log files

2011-06-11 Thread kshitij mali
Hi Mark , Thanks of taking intreast in my case , yes the rhel4 default bind named service is running in chroot jail , know tell we what config changes do i nedd to change. Regards, Kshitij On Sat, Jun 11, 2011 at 7:53 AM, Mark Andrews wrote: > > Are you starting named with -t ? If so you nee

Re: why bind unable to find log files

2011-06-10 Thread Mark Andrews
Are you starting named with -t ? If so you need to look at the path relative to the . Mark In message , kshitij mali w rites: > --===0107398317155429819== > Content-Type: multipart/alternative; boundary=20cf3033451dccf8a204a559ffe8 > > --20cf3033451dccf8a204a559ffe8 > Content-Type: