Summary: | init-script for named/bind 9.3.1-r3 asks for options | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Christian <benke> |
Component: | [OLD] Server | Assignee: | Konstantin Arkhipov (RETIRED) <voxus> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 107724 | ||
Bug Blocks: | |||
Attachments: |
/etc/conf.d/named
working init-script |
Description
Christian
2005-08-11 09:55:29 UTC
Created attachment 65678 [details]
/etc/conf.d/named
this is my /etc/conf.d/named - when the chroot-path is set, the
init.d/named-script starts with * Starting chrooted named ..., when it's
commented out it says * Starting named ... - so basically it is read...
Created attachment 65682 [details]
working init-script
works with this init-script, seems there are probs with --pid/--pidfile
I had the same issue. In the /etc/init.d/named script replace the following lines ----------------------------------------------------------- # As with the named.conf test, above, there's no need # for chroot and non-chroot cases here PIDFILE=$(grep "pid-file" ${CHROOT}/etc/bind/named.conf | \ egrep -v ".*[#,//].*pid-file" | \ head -n 1 | \ sed -ne 's:.*pid-file\(.*\)\"\(.*\)\";:\2:p') [ -n "$PIDFILE" ] || PIDFILE=/var/run/named.pid PIDFILE="${CHROOT}$PIDFILE" KEY="${CHROOT}/etc/bind/rndc.key" ------------------------------------------------------------ with the lines provided by Christian's old named script ---------------------------------------------- if [$CHROOT -a -d $CHROOT ] ; then PIDFILE="${CHROOT}/var/run/named/named.pid" KEY="${CHROOT}/etc/bind/rndc.key" else PIDFILE="/var/run/named/named.pid" KEY="/etc/bind/rndc.key" fi ---------------------------------------------- seems that there are still chroot and non chroot cases needed. Or did we something wrong? fixed in 9.3.1-r5 and 9.2.5-r7 solution taken from bug #107724 sorry for delay. |