shibd -h says: [...] -f force removal of listener socket. [...]
(I assume it's meant for Unix sockets only.)
However, the listener socket is unconditionally removed before creation. This breaks a handy automatic mutual exclusion, as not removing the socket would make running two daemon instances on the same socket impossible at the OS level.
Ok, got it. I found the code, and it must have been overlooked when I redid the socket handling and moved it into the library entirely. I'll see if I can come up with something.
Ferenc Wágner May 12, 2009 at 2:48 PM
Edited
Yes, I meant -f, not -t, sorry.
The point is that -f does not matter, the socket is removed anyway. Even when -f is not present.
Scott Cantor May 12, 2009 at 2:36 PM
Did you mean the -f option in the title of this issue?
I'm not following what you're suggesting either. The whole point of -f is to remove the socket when it exists. If it checked before-hand, it wouldn't be any different than not using -f.
shibd -h says:
[...]
-f force removal of listener socket.
[...]
(I assume it's meant for Unix sockets only.)
However, the listener socket is unconditionally removed before
creation. This breaks a handy automatic mutual exclusion, as
not removing the socket would make running two daemon
instances on the same socket impossible at the OS level.