FrankB <[EMAIL PROTECTED]> writes:
> 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, why do you say that ? See here below. # *** pre actions *** # *** main actions *** touch DNSServer/main/template--etc--named.conf; touch DNSServer/main/template--etc--sysconfig--named; touch DNSServer/main/template--etc--rndc.key; touch DNSServer/main/template--etc--rndc.conf; touch DNSServer/main/template--etc--resolv.conf; touch DNSServer/main/template--etc--dhcpd.conf; touch DNSServer/main/script--check-services.pl; touch DNSServer/main/script--bind-chroot.sh; # *** post actions *** touch DNSServer/post/restart--shorewall touch DNSServer/post/script--permissions.sh; touch DNSServer/post/restart--named; touch DNSServer/post/restart--dhcpd; touch DNSServer/post/restart--syslog; As you can see the files are created in /etc ... then moved to the chroot location by the script ... no need to do things by hand ... > Now, is there no way, to do this automaticly? isn't the case already ? > 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... yes but I thing this is already there ... but I might be wrong ... my 2cts, -- Florin http://www.mandrakesoft.com http://people.mandrakesoft.com/~florin/
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
