Re: enbd 2.4.32/kernel 2.6.12.3 pid file problem

In article <[email protected]> you wrote:
> myckpidfile(struct nbd_pidfile * self) {
> 
>      int otherpid;
>      int mypid = getpid();
>      int myppid = getppid();
> 
>      sleep(2);
>     ^^^^^^^^^

Thinking about it, I don't think it is racing with itself.  All I can
imagine is that you are starting it with some generic daemon starter
that writes its own pid in the pidfile, and which hangs around just long
enough to see the parent of this daemon process die (after it has
launched its daemon child).

That would mean that the extra 2s wait would allow the parent (which
nowadays runs second after a fork) to die off, the daemon launcher to
die, and this process to see a pid entry that corresponds to no known
live process, which can hence be overwritten.

So .. how are you starting the enbd-client?

Peter