AW: named 9.3.3 start-script

Hi Gabriel,

Here it is:

[root@host1 configs]# cat /etc/sysconfig/named
# BIND named process options
# ~~~~~~~~~~~~~~~~~~~~~~~~~~
# Currently, you can use the following options:
#
# ROOTDIR="/some/where"  --  will run named in a chroot environment.
#                            you must set up the chroot environment
#                            (install the bind-chroot package) before
#                            doing this.
#
# OPTIONS="whatever"     --  These additional options will be passed to named
#                            at startup. Don't add -t here, use ROOTDIR instead.
#
# ENABLE_ZONE_WRITE=yes  --  If SELinux is disabled, then allow named to write
#                            its zone files and create files in its 
$ROOTDIR/var/named
#                            directory, necessary for DDNS and slave zone 
transfers.
#                            Slave zones should reside in the 
$ROOTDIR/var/named/slaves
#                            directory, in which case you would not need to 
enable zone
#                            writes. If SELinux is enabled, you must use only 
the
#                            'named_write_master_zones' variable to enable zone 
writes.
#
# ENABLE_SDB=yes         --  This enables use of 'named_sdb', which has support
#                        --  for the ldap, pgsql and dir zone database backends
#                        --  compiled in, to be used instead of named.
#
# DISABLE_NAMED_DBUS=[1y]--  If NetworkManager is enabled in any runlevel, then
#                            the initscript will by default enable named's D-BUS
#                            support with the named -D option. This setting 
disables
#                            this behavior.
#


Trevor: I did not install the bind-chroot-package, so I don't think thats the 
error,

I just noticed, that when config-file is really at his place 
/etc/named.conf..it starts just fine, but I need to create symlinks to place 
the named.conf and the /var/named-directory onto a replicated device (DRBD) so 
both cluster-nodes can access the same config-files

Is it possible, that the script cannot handle this?

Greetings from Germany


> what do you have in /etc/sysconfig/named ?
> 
> 
> 
> 
> On Mon, 2008-07-07 at 17:50 +0200, Schmidt, Florian wrote:
> > Hello everyone,
> >
> > This is my first posting to the list, so I do not know yet if there's a lot 
> > of activity
> here or not ;) But any help would be appreciated.
> >
> > I want to install bind-9.3.3-10.el5.i386.rpm shipped with RHEL5 (Kernel 
> > 2.6.18-
> 53).
> >
> > The Installation is no problem, but when I try to start the named via
> /etc/init.d/named start, he fails and says:
> >
> > Jul  7 16:39:20 host1 named: none:0: open: /etc/named.conf: permission 
> > denied
> >
> > I googled around a little bit and found something about chowning the file to
> root:named and setting file permissions to 640. I even gave 777, but nothing 
> works.
> >
> > If I start named directly via /usr/sbin/named he comes up just fine, but 
> > because of
> clustering with linux-ha [heartbeat] I need to start it with the 
> init.d-script.
> >
> > What's wrong with that script? I'm not Linux-Guru enough to read trough that
> script and find the error alone :(
> >
> > So please would anyone give me a hint or tell me what to do, to get BIND
> running.
> >
> > Thanks in advance :)
> >
> > Florian
> >
> > Mit freundlichen Grüßen
> >
> > Florian Schmidt
> >
> > Centric altro GmbH
> > GB IT-Services
> > Mittelbacher Straße 3
> > 09224 Chemnitz
> > Germany
> >
> > Phone       +49 371 88 17016
> > Fax +49 371 88 17460
> > florian.schmidt-8gWyIKKAVPLU1N6mKAjURQ@xxxxxxxxxxxxxxxx
> > www.centric-it.de
> >
> > Geschäftsführung: Thomas Vallbracht-Theßeling, Gerard Sanderink ~ Sitz der
> Gesellschaft: Oberhausen
> > Registergericht: Duisburg HRB 17807 ~ Steuer-Nr.: 124/5704/1303 ~ USt.-Id.-
> Nr.: DE246840541
> >
> > -------------------------------------
> > The information included in this message is personal and/or confidential and
> intended
> > exclusively for the addressees as stated. This message and/or the 
> > accompanying
> documents
> > may contain confidential information and should be handled accordingly. If 
> > you
> are not the
> > intended reader of this message, we urgently request that you notify Centric
> immediately and
> > that you delete this e-mail and any copies of it from your system and 
> > destroy any
> printouts
> > immediately.
> > It is forbidden to distribute, reproduce, use or disclose the information 
> > in this e-
> mail to third
> > parties without obtaining prior permission from Centric. We expressly point 
> > out
> that there are
> > risks associated with the use of e-mail. Centric and the companies within 
> > the
> group shall not
> > accept any liability whatsoever for damage resulting from the use of e-mail.
> Legally binding
> > obligations can only arise for Centric by means of a written instrument, 
> > signed by
> an authorized
> > representative of Centric.
> > -------------------------------------
> >
> >
> > _______________________________________________
> > rhelv5-list mailing list
> > rhelv5-list-H+wXaHxf7aLQT0dZR+AlfA@xxxxxxxxxxxxxxxx
> > https://www.redhat.com/mailman/listinfo/rhelv5-list
> 
> 
> _______________________________________________
> rhelv5-list mailing list
> rhelv5-list-H+wXaHxf7aLQT0dZR+AlfA@xxxxxxxxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/rhelv5-list