Server refuses to start if .pid exists

[rethinkdb]

Server refuses to start if .pid exists

[frank-trampe]

Hi there.

This is expected behavior. Although less necessary for our product since it detects an instance using its data store automatically and also fails if requested ports are already in use, this helps to interface with init scripts and the like which demand this sort of strict behavior (creating the pid file only if it is not already present and deleting it only on clean exit).

If you are just trying to get the pid of the launched daemon, you could use the $! option in the shell after launching the process into the background. Would this work for you?

[sophiebits]

Actually I've been starting it with service but it's been crashing (#38) and leaving the .pid file.

[sophiebits]

I guess this behavior is fine, just a little inconvenient.

[coffeemug]

Yep, all unix software behaves this way. I think it will get a lot less annoying when #38 is worked out.