This is a discussion on named erroring out within the Linux Security forums, part of the System Security and Security Related category; I'm trying to set up a caching named on an RHEL 3 system. When I try to run it, ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
I'm trying to set up a caching named on an RHEL 3 system. When I try to run it, I get: Dec 15 14:05:28 hostname named[9153]: couldn't open pid file '/var/run/named/named.pid': Permission denied Dec 15 14:05:48 hostname named[9153]: exiting (due to early fatal error) strace'ing named indicates that named is Not setuid'ing, but it Is using capalities. I assume it's these capabilty restrictions that are preventing named from writing to /var/run/named, which is mode 770, and owned by the "named" user. Does anyone have any thoughts on how to make named work on this RHEL 3 system? Thanks! |
|
|||
|
Dan Stromberg wrote:
> > Dec 15 14:05:28 hostname named[9153]: couldn't open pid file > '/var/run/named/named.pid': Permission denied > > Dec 15 14:05:48 hostname named[9153]: exiting (due to > early fatal error) > > strace'ing named indicates that named is Not setuid'ing, but it Is using > capalities. I assume it's these capabilty restrictions that are > preventing named from writing to /var/run/named, which is mode 770, and > owned by the "named" user. > > Does anyone have any thoughts on how to make named work on this RHEL 3 > system? No, but if you're sure it's not a permissions issue you migt want to check the chroot environment to make sure it contains the *directory* var/run/named HTH C. |