After installing the new Kernel 2.6.4-rc1, named dies with a 'capset failed: Operation not permitted' error. This is on one of my primary Nameservers :-( Even tried the bind code from ISC. Message is from .. bind-9.2.3/bin/named/unix/os.c - 'function linux_setcaps' Reproducible: Always Steps to Reproduce: 1. Install Linux 2.6.4-rc1 2. Try and run 'named' 3. Actual Results: # named -g named: capset failed: Operation not permitted Expected Results: named should have run ???? Can't figure why no one else has reported this. Copied the 2.6.4-r1 kernel over to a Slackware 9.1 machine, and recompiled. Same thing happened. I think its a change in 2.6.4 Linuix Capabilities, Threads or Securities around changing your user ID or similar.
did you try 2.6.5-rc2 ?
to merge direct ebuilds, just emerge /path/to/foo.ebuild
I had the same issues with versions of 2.6 kernel, I didn't report it as a bug here because it appeared to be a kernel thing rather than a gentoo bug. I have just tried sys-kernel/mm-sources 2.6.5_rc2-r3, compiling it with genkernel and named now starts without errors.
Agreed - Seems to be more to do with the Kernel being used - and possibly how its compiled. Running 2.6.5-rc2 gives no problem. If 'named' ever has a 'capset' (an error in requesting certain capabilities from the Kernel - ie setting some sort of ulimit or user id) then try a different Kernel or Release Canidate.
I edited "/usr/portage/net-dns/bind/bind-9.2.2-r3.ebuild" and added one line in the econf section: --disable-linux-caps \ This is the critical configure-parameter resposible for the bug. When I re-emerged bind, it finally started. I have kernel 2.6.5-r1 (or r2).
