Re: [cobalt-developers] couldn't create pid file '/var/run/named.pid'

[shimi <shimi@xxxxxxxxxxxxxxxx>]

On Mon, 16 Jul 2001, cpaul wrote:

> 
> 
> thanks Frank
> 
> is doing this considered risky?

besides the fact that every user in the system can put files there,
execute them and that?

b.t.w. he's wrong, read-writeable for all is 666, 777 is
read-write-execute for all.

This error SHOULD not happen, and I don't suspect this error to be in
permissions, but in the fact the enviroment is chrooted (type man chroot
for more info about that)

The reason I say what I say is, that when a file matches the owner, and is
read-writable by the owner, of the *path* to the file is not blocked by
the hirarchy, and in your case, it isn't (there are read-execute
permssions for "other" in the upper directories to that file) - the file
is ALWAYS writeable.

It's like your home directory. You can't write in /home, but you can write
in a directory underneath it, right? :-)

HTH,

- shimi.
> 
> 
> 
> Hello Chris,
> 
> make the directory /var/run read-writeable for all "chmod 777 /var/run". 
> Then named can create his pid-file there.
> 
> greets frank