public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Todd Punderson <todd@doonga.net>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] bind-9.1.3-r7
Date: Thu, 07 Mar 2002 02:59:37 -0500	[thread overview]
Message-ID: <20020307020701.B6B4.TODD@doonga.net> (raw)

I did a update --world tonight and I also ran into this. It's probably 
destined for bugzilla, but I wanted to ask first.

After updating to bind-9.1.3-r7 I had a problem getting it to run. I
determined the problem to be the following. The named startup script
executes this: start-stop-daemon --start --quiet --exec /usr/sbin/named -- -u named -n 1

Since named switches to uid 'named' it doesn't have access to write to
/var/run/named.pid  However, I noticed that there is now a
/var/run/named dir that is owned by named.named...This is all well and
good but the named binary doesn't try to write it's pidfile to that
directory and bombs. I looked in the ebuild and the bind documentation
and there is a way to configure it to point to another directory: on the
configure script it needs --localstatedir=/var/run/named instead of
--localstatedir=/var  but this also means that the /etc/init.d/named
script needs to be edited to point to /var/run/named/run/named.pid for
the stop portion of it. Maybe the extra 'run' in there could be edited
out with by modifing the bind source, I didn't dig that far, I just need
it running. :)
        Also /var/bind needs to be owned by named.named in order for the zone
files to be read (since I did an upgrade, this bit me, it may not on a
new install)
-- 
Todd Punderson <todd@doonga.net>




             reply	other threads:[~2002-03-07  8:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07  7:59 Todd Punderson [this message]
2002-03-15 10:30 ` [gentoo-dev] bind-9.1.3-r7 gentoo-user
2002-03-15 12:45   ` Stefan Boresch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020307020701.B6B4.TODD@doonga.net \
    --to=todd@doonga.net \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox