named failed to start in 2.6.3
 

werid, today I compile and install kernel 2.6.3 on my work box IBM P3. Everything look fine, however when I tries to start bind "/etc/rc.d/init.d/named start " it fails to start :(
giving me message "Starting named: Capset failed: Operation not permitted"

however when do have 2.6.3 kernel at my home box however my named is working cool there

I search the net but didn't get any help :(

anyone with solution please

bind named capset and permissions in kernel 2.6.x with LSM compiled into kernel
 

The answer to this is unobvious to anyone not using the LSM or SE linux patches

i got this from a translated spanish user group:

try modprobe capability
and restart named , it should bind to the socket and set its uid properly

at least it did for me with kernel 2.6.6.rc1

incidently if you dont compile kernel 2.6.x with the security enhancements such as SElinux and LSM you dont need to do this. you may want to recompile if this is your desktop system and not a server.

good luck

madhav

This worked great for me.

modprobe capability gave me the module not found error. EVEN THOUGH I am positive I included SElinux into my kernel. sorry to put it so bluntly, but what the **** is going on??

PS: I'm using Gentoo's developmental kernel gentoo-linux-2.6.9-r1 aka gentoo-dev-sources.

working! :)
 

'modprobe capability' worked for me :)
uname -a:
Linux 2.6.7-10.0.aur.9 #1 Thu Aug 12 05:01:38 EDT 2004 i686 i686 i386 GNU/Linux

thanks for saving my time :)

Hi,
I had the same problem but I was able to start it manually:
# cd /etc/init.d
# sh named stop
# sh named start ===> OK

That means it was started too "early" in the boot sequence. So - without any further investigation - I moved the S55named
to S61named in the directory /etc/rc5.d. My boot sequence is now as follows: S55cups, S55sshd, S56xinetd, S58ntpd, S60nfs,
S61named and it works without any problem.
Regards,
Andreas Huppert

wait a minute... this is going to sound really stupid but it turns out that I really DIDN'T have capability installed in my kernel. so I had to update my kernel anyway, so I did that then I included capability and it works now...