Am Di, den 30.11.2004 schrieb Florin um 16:04:
> FrankB <[EMAIL PROTECTED]> writes:
>
> > Sers,
> >
> > Am Mo, den 29.11.2004 schrieb Florin um 17:05:
> > > Hi,
> > >
> > > No, I didn't avaoid your question .. I simply took some time to test
> > > things. I'm back to my original approach in setting this up now.
> >
> > never thinking this...
> > If my day has 36 hours i wouldn't be so stressed :-)
> >
> > > There were indeed some issues with the named setup ... I'm now using a
> > > different approach that I have used some time ago ... based on some code
> > > from the /usr/sbin/bind-chroot.sh script I wrote for bind some time ago.
> > >
> > > can you give it a try please ?
> >
> > yeah.. this fine script does everything needed to chroot bind...
> > perhaps missing some echo that one must restart syslogd too...
>
> oups ... indeed ... I have forgotten to add this event ...
>
> > I don't regocnize that this script should be called...
> > Maybe this could be call at the "first start" of mnf!??
> > or point the user to do it by hand (in the frontend - DNS section)!??
> >
> > but if you get around with the setup issues, what i'm be sure of,
> > no one had to make thoughts about this...
>
> I'm not sure I follow you here ... can you be more specific please ?
As I Understand, perhaps of the setup issues, one must prepare for
chroot bind by hand, calling the /usr/sbin/bind-chroot.sh script...
Now, is there no way, to do this automaticly?
Perhaps this could do by the first time activating the caching dns in
the frontend...
ie add a var BindChrootPrepare=Yes|No to the configuration (installation
default = No), check this when one enables bind and then call this
script...
But if the setup issue is solved, there is no need to prepare it by
hand, or?
Hope i write my thinking clearer down...
> > > PS. I'm not using the /usr/share/naat/templates/var/lib/named-chroot but
> > > /usr/share/naat/templates/etc ones and then use the script to move and
> > > creates what is necessary ..
> > >
> > > let me know if you find a problem ..
> > >
> > > >FrankB <[EMAIL PROTECTED]> writes:
> > >
> > > > Hello Florin,
> > > >
> > > > may i ask a question about named and chroot on mnf?
> > > >
> > > > for me it seems that named is not chrooted
> > > > let me explain my thinking, correct me if im totaly wrong...
> > > >
> > > > The backend proceses the sysconfig of named to
> > > > /var/lib/named-chroot/etc/sysconfig/named
> > > >
> > > > now, if named starts, it isn't chrooted yet and look in
> > > > /etc/sysconfig/named for its root-directory and options
> > > > and after that named is chrooted and dont touch the
> > > > sysconfig-named-file again.
> > > >
> > > > -------------------------------------------------------------------------
> > > > [EMAIL PROTECTED] sysconfig]# cat /etc/init.d/named
> > > > #!/bin/bash
> > > > #
> > > > # named This shell script takes care of starting and stopping
> > > > # named (BIND DNS server).
> > > > #
> > > > # chkconfig: 345 55 45
> > > > # description: named (BIND) is a Domain Name Server (DNS) \
> > > > # that is used to resolve host names to IP addresses.
> > > > # probe: true
> > > >
> > > > # Source function library.
> > > > . /etc/rc.d/init.d/functions
> > > >
> > > > # Source networking configuration.
> > > > [ -r /etc/sysconfig/network ] && . /etc/sysconfig/network
> > > >
> > > > RETVAL=0
> > > > prog="named"
> > > >
> > > > # Check that networking is up.
> > > > [ "${NETWORKING}" = "no" ] && exit 0
> > > >
> > > > [ -f /etc/sysconfig/named ] && . /etc/sysconfig/named
> > > >
> > > > [ -f /usr/sbin/named ] || exit 0
> > > >
> > > > [ -f ${ROOTDIR}/etc/named.conf ] || exit 0
> > > >
> > > > start() {
> > > > # Start daemons.
> > > > if [ -n "`/sbin/pidof named`" ]; then
> > > > gprintf "$prog: already running"
> > > > return 1
> > > > fi
> > > > gprintf "Starting %s: " $prog
> > > > if [ -n "${ROOTDIR}" -a "x${ROOTDIR}" != "x/" ]; then
> > > > OPTIONS="${OPTIONS} -t ${ROOTDIR}"
> > > > fi
> > > > daemon named -u named ${OPTIONS}
> > > >
> > > > ---[SNIP]---
> > > > ---------------------------------------------------------------------------------------
> > > >
> > > > shouldn't now the sysconfig-named-template not moved to
> > > > /usr/share/naat/template/etc/sysconfig/ ?
> > > > (and adaptions to the events)
> > > >
> > > > or
> > > >
> > > > if /etc/sysconfig/named is a symbolic link
> > > > to /var/lib/named-chroot/etc/sysconfig/named
> > > > i think everything goes round... but it isn't on my mnf
> > > >
> > > > [EMAIL PROTECTED] /]# ls -l /etc/sysconfig/named
> > > > -rw------- 1 root root 444 Nov 27 10:28 /etc/sysconfig/named
> > > >
> > > > another thing is, the location of the basic zone-files (named.ca,
> > > > named.local). They are hold in /var/named/
> > > > shouldn't they are in /var/lib/named-chroot/var/named/ ?
> > > > or is it better to have a symbolic link too?
> > > >
> > > > and as well the named.pid-file is writen to
> > > > /var/run/ and not to /var/lib/named-chroot/var/run/...
> > > >
> > > > what do you think?
> > > > how i write above, perhaps i'm totaly wrong...
> >
> > thanks and greatz
> > FrankB
> >
> >
> > ____________________________________________________
> > Want to buy your Pack or Services from MandrakeSoft?
> > Go to http://www.mandrakestore.com
> > Join the Club : http://www.mandrakeclub.com
> > ____________________________________________________
____________________________________________________
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com
____________________________________________________
