On Sun, 8 Nov 1998, Dino Nardini wrote:
> (2) Linuxconf loaded just fine from the command prompt but it couldn't find
> a makemap reference in "/usr/lib/linuxconf/redhat/DIST/conf.daemons", which
> didn't exist. The closest I could find was
> "/usr/lib/linuxconf/redhat/linuxconf.daemons". After adding a reference to
> makemap the error (and core dumps) disappeared. I immediately upgraded to
> Linuxconf 1.13 subrev 4 and added the dnsconf and mailconf modules. I had
> some problems rebuilding my dns server... linuxconf didn't appear to reboot
> named when I made dns changes. Doing a manual boot of named worked.
Here is the story. Until recently, linuxconf did not supported bind 8. In
fact it started to support it a little after RedHat did their feature
freeze for 5.2. This explains why little attention was given to the sysv
init script /etc/rc.d/init.d/named. This file looks like this
(The start)
#!/bin/sh
#
# 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.
By adding the following lines
# processname: named
# config: /etc/named.conf
linuxconf will reliably restart the dns (/etc/rc.d/init.d/named restart).
Well, it will do so if /etc/named.conf is newer than the named process (or
the last restart time). This will be reliable because linuxconf blindly
rewrite this file each time you modify the DNS. It rewrites it even if no
new information was added in this specific file. This "features" is handy
here.
Now, to get really reliable (if you modify a zone file by hand), one would
have to had a
# config:
line for every zone file. Linuxconf has a trick for that. If you call
linuxconf with the following command
linuxconf --hint dnsconf
it will tell you if the DNS must be restarted. This feature appeared in
the late 1,11 revision. But given that linuxconf did not supported bind 8
until recently, it has been of no use to redhat packaging for 5.2. I guess
that it will be used in future release. RedHat already use the hinting
system extensivly.
In the mean time, if you want a complete solution for this problem, you
may want do apply this patch at the end of this message to
/etc/rc.d/init.d/named
About the problem with httpd, I would say that the files in
/etc/httpd/conf are probably "in the future", so linuxconf keeps thinking
that they are newer than the process.
*** named.bak Thu Sep 24 02:47:09 1998
--- named Fri Nov 13 01:41:14 1998
***************
*** 6,11 ****
--- 6,12 ----
# 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
***************
*** 43,48 ****
--- 44,58 ----
restart)
/usr/sbin/ndc restart
exit $?
+ ;;
+ probe)
+ if [ -x /bin/linuxconf ] ; then
+ NAMED=""
+ eval `/bin/linuxconf --hint dnsconf`
+ if [ "$NAMED" != "" ] ; then
+ echo $NAMED
+ fi
+ fi
;;
*)
echo "Usage: named {start|stop|status|restart}"
---------------------------------------------------------
Jacques Gelinas <[EMAIL PROTECTED]>
Check out Linuxconf at http://www.solucorp.qc.ca/linuxconf
New modules: mgettyconf, managerpm
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
