In article <[email protected]>, [email protected] wrote:
>> Permissions are perfect. >> and the bind version is 9.3 >> >> #rpm -qa |grep bind >> bind-utils-9.3.3-7.el5 >> bind-chroot-9.3.3-7.el5 ^^^^^^^^^^^ >> kdebindings-3.5.4-1.fc6 >> bind-9.3.3-7.el5 >> ypbind-1.19-7.el5 >> bind-libs-9.3.3-7.el5 >> system-config-bind-4.0.3-2.el5 I suspect you are using bind in chroot-ed environment. (snipped) >> > On 11/24/2010 07:09 AM, hemanth kumar wrote: >> > > Hi all, >> > > >> > > When I start the named after adding the line include >> > > "/usr/local/samba/private/named.conf"; >> > > >> > > to named.conf file,named fails to start with error the following msg. >> > > >> > > Starting named: >> > > Error in named configuration: >> > > /etc/named.conf:64: open: /usr/local/samba/private/named.conf: file not >> > > found >> > > [FAILED] >> > > but the file is very much present in that path. In chroot-ed environment, I suppose you put samba-related named.conf under chroot-ed top directory (ex. /var/named/chroot/usr/local/samba/private/named.conf)? ---- Tomoki AONO ([email protected]) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
