I compiled Bind 9.2.2 on 2.4.19-gentoo-r10 and at first and it worked, however, an update to 2.4.20-gentoo-r2 resulted in: * Starting chrooted named... named: -u not supported on Linux kernels older than 2.3.99-pre3 or 2.2.18 when using threads [ !! ] I was able to fix this by commenting out the threads option in the ebuild for Bind. Then: The /etc/init.d/named start script would successfully run ( [ok] ), but the following two lines were in /var/log/daemon.log Apr 13 22:42:08 www named[31793]: capset failed: Operation not permitted Apr 13 22:42:08 www named[31793]: exiting (due to early fatal error) /etc/init.d/named zap. To fix this I had to change the econf line(s) in the ebuild to: econf --sysconfdir=/etc/bind \ --localstatedir=/var \ --disable-threads \ --disable-linux-caps \ --with-libtool \ ${myconf} Bind now works Reproducible: Always Steps to Reproduce: 1. Compile 2.4.20-gentoo-r2 2. Compile Bind 9.2.2 3. Try to run bind Actual Results: See details Expected Results: Should've worked :]
how about reemerge bind ? it works fine on my system with the config you reported
I recompiled Bind many times as well as the kernel. The only thing that worked was the fix I posted here.
did you try etc-update ? maybe the init script changed
The last time I did etc-update my system's configuration files were radically changed. Regardless, why would the init script change if its the SAME version used on 2.4.19 and 2.4.20? Especially when not changing the default ebuild.
try reemerge
net-dns/bind selected: none protected: 9.2.2 omitted: none >>> clean: No packages selected for removal. >>> Regenerating /etc/ld.so.cache... >>> Auto-cleaning packages ... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. * IMPORTANT: 50 config files in /etc need updating. * IMPORTANT: 7 config files in /usr/X11R6/lib/X11/xkb need updating. * Type emerge --help config to learn how to update config files. root@www pri # /etc/init.d/named stop * Stopping named... [ ok ] root@www pri # /etc/init.d/named start * Starting chrooted named... named: capset failed: Operation not permitted [ !! ] root@www pri # /etc/init.d/named start * Starting chrooted named... named: capset failed: Operation not permitted [ !! ] Haven't I said that I tried to reemerge already??
Created attachment 10771 [details] Log of the emerge that results in faulty installation
IMPORTANT: 50 config files in /etc need updating. * IMPORTANT: 7 config files in /usr/X11R6/lib/X11/xkb need updating. please run #etc-update
etc-update has a nasty habit of overwriting important files, such as /etc/fstab, /etc/apache/conf/apache.conf, etc. Here's the diff between the new and what I have. root@www init.d # diff ._cfg0000_named named 66c66 < \ No newline at end of file --- > ~~ root@www conf.d # diff ._cfg0000_named named 7c7 < CPU="1" --- > CPU="2" 13c13 < # CHROOT="/chroot/dns" --- > CHROOT="/chroot/dns"
does it work now ?
I have it working by --disable threads and --disable-linux caps... which is the whole point of the bug report. Nothing else worked.
fact is, it's working here, AS-IS kernel-guys maybe you could solve this
well, this cannot be reproduced. but, i do know this is an issue if you use lids and do not disable thread and caps you will have the issues you list. are you patching the kernel with stuff from http://www.lids.org/ ??? Thanks, Jay
well, this does not seem to be a reproducible issue and no further information has been provided. can't fix without more info. Jay
if you'd like have a look to bug #21255
db issue
I try the same thing to solve the problem and have gentoo root # ebuild econf --sysconfdir=/etc/bind --localstatedir=/var --disable-threads --disable-linux-caps --with-libtool ${myconf} !!! Name error in : missing a version or name part. !!! Error: PF is null ''; exiting. gentoo root # /etc/init.d/named start * Starting named... named: capset failed: Operation not permitted [ !! ] gentoo root # etc-update Scanning Configuration files... Exiting: Nothing left to do; exiting. :)
Problem was fis just tipe in console: gentoo conf.d #/etc/init.d/named start named: capset failed: Operation not permitted gentoo / #modprobe capability gentoo / #/etc/init.d/named start * Starting named... [ ok ] gentoo / # In my case was fix ;)
