> Message: 12 > Date: Tue, 05 Jul 2005 09:25:01 -0700 > From: Gordon Messmer <yinyang@xxxxxxxxx> > Subject: Re: Bind Error with New Kernel > To: For users of Fedora Core releases > <fedora-list@xxxxxxxxxx> > Message-ID: <42CAB45D.7050604@xxxxxxxxx> > Content-Type: text/plain; charset=UTF-8; > format=flowed > edwarner99@xxxxxxxxx wrote: > > With kernel 2.6.12-1.1387_FC4 bind no longers wants to > write my .jnl files in /var/named/chroot/var/named. > Instead it insists on writing the file to /var/named/ > but only if I give the folder write permission for > named. Sounds like chroot isn't working, or isn't being attempted. Are there any interesting errors logged in /var/log/messages by named? Does /etc/sysconfig/named still say "ROOTDIR=/var/named/chroot"? > I'm guessing here, but SELinux might be breaking > > something. Does chroot work properly if you boot with > SELinux disabled? I have never changed /etc/sysconfig/named. It is still "stock". What lines have to be changed? I am running SELinux disabled. __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail
