[bind10-dev] How to avoid multiple xfrout processes running at same time
zlkzhy at gmail.com
Tue Jun 1 09:30:40 UTC 2010
My question is: how to make sure there is only one xfrout process running
on server?(Xfrout runs as one unix socket server).
The current implementation in trunk is: when xfrout starting, socket file
"/var/auth_xfrout_conn" will be unlinked(removed) first, but in this way you
can't stop user from starting a new xfrout process.
The other way: check whether the socket file "/var/auth_xfrout_conn" used by
xfrout exist or not when starting? The problem is if xfrout crashed last
time, and /var/auth_xfrout_conn wasn't deleted properly, you have to let
user to delete /var/auth_xfrout_conn manually. Do this make sense? (I hate
I know it's same problem with .pid file.
Waiting for better way.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bind10-dev