Bug#303777: marked as done (kernel-image: Bind9 from woody fails to start; capset failed: Operation not permitted)
Your message dated Sun, 10 Apr 2005 20:22:58 +0200
with message-id <20050410182258.GD32118@sputnik.stro.at>
and subject line Bug#303777: kernel-image: Bind9 from woody fails to start; capset failed: Operation not permitted
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 8 Apr 2005 18:24:51 +0000
>From t0@nickhill.co.uk Fri Apr 08 11:24:51 2005
Return-path: <t0@nickhill.co.uk>
Received: from (d.me) [213.152.57.82]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DJy9y-0006cO-00; Fri, 08 Apr 2005 11:24:50 -0700
Received: from [127.0.0.1] (d [127.0.0.1])
by d.me (Postfix) with ESMTP
id E1E9A586C2; Fri, 8 Apr 2005 19:24:38 +0100 (BST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: t0@nickhill.co.uk
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: kernel-image: Bind9 from woody fails to start;
capset failed: Operation not permitted
X-Mailer: reportbug 3.8
Date: Fri, 08 Apr 2005 19:24:38 +0100
Message-Id: <[🔎] 20050408182438.E1E9A586C2@d.me>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.4 required=4.0 tests=BAYES_00,HAS_PACKAGE,
NO_REAL_NAME autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: kernel-image
Version: 2.6.11-3
Severity: important
Bind9 from Debian woody will not start when run with this kernel. It does work
with kernel 2.6.10 and previous.
#/etc/iniit.d/bind9 start
Starting domain name service: namednamed: capset failed: Operation not permitted
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15)
---------------------------------------
Received: (at 303777-done) by bugs.debian.org; 10 Apr 2005 18:23:00 +0000
>From max@stro.at Sun Apr 10 11:23:00 2005
Return-path: <max@stro.at>
Received: from baikonur.stro.at [213.239.196.228]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DKh5I-0006xh-00; Sun, 10 Apr 2005 11:23:00 -0700
Received: from sputnik (stallburg.stro.at [128.131.216.190])
by baikonur.stro.at (Postfix) with ESMTP id 611865C001
for <303777-done@bugs.debian.org>; Sun, 10 Apr 2005 20:22:59 +0200 (CEST)
Received: from max by sputnik with local (Exim 4.50)
id 1DKh5H-0005jZ-0R
for 303777-done@bugs.debian.org; Sun, 10 Apr 2005 20:22:59 +0200
Date: Sun, 10 Apr 2005 20:22:58 +0200
From: maximilian attems <debian@sternwelten.at>
To: 303777-done@bugs.debian.org
Subject: Re: Bug#303777: kernel-image: Bind9 from woody fails to start; capset failed: Operation not permitted
Message-ID: <20050410182258.GD32118@sputnik.stro.at>
References: <[🔎] 20050408182438.E1E9A586C2@d.me> <[🔎] 20050409192949.GC24735@sputnik.stro.at> <[🔎] 425963F5.5080108@nickhill.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[🔎] 425963F5.5080108@nickhill.co.uk>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by Amavis (ClamAV) at stro.at
Delivered-To: 303777-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
On Sun, 10 Apr 2005, Nick wrote:
> modprobe capability
> and entering the line
> capability
> in /etc/modules
> allows bind9 to start.
ok great, thanks for your feedback.
closing this bug therefor.
a++ maks
Reply to: