Re: [PATCH] locating mutex lockfile in PID file directory

[Randy Terbush <ra...@zyzzyva.com>]

> On Wed, 22 Jan 1997, Randy Terbush wrote:
> 
> > 
> > I have the following patch that attempts to put the mutex lock
> > file in the same directory as the PID file. I've attempted to
> > test this on FreeBSD by forcing USE_FCNTL_ACCEPT_MUTEX (or whatever)
> > and it does not seem to work. I don't see why the children should
> > not be able to get a lock on this file with one execption and
> > that is permissions. We are opening as root WR_ONLY with 644 perms.
> > How could any of the child processes lock this descriptor? I'm
> > assuming they would need to be able to write the file in order to
> > lock it.  ??
> 
> But doing things the current way we don't have write access to the
> file either, right?  The difference is that currently we have write
> access to the directory while with this we don't.

Does this mean that the children are creating new files rather than
passing the file descriptor?

> What errno is it giving you?

I honestly haven't spent much time debugging yet. This is a tough
function to get to in a debugger and I have had no success attaching
to the children.