Byron Nevins wrote:
> The stop-domain command that runs on the server side is asynchronous --
> it returns success in all cases and it returns instantly. Thus w/o the
> pinging you wouldn't know when the server is really dead, and you would
> have to add annoyingly over-long timeouts to scripts to be sure.
>
> stop-domain "pings" the server. When the "ping" goes unanswered --
> stop-domain exits.
Why don't you just open a connection and wait for the connection to be
closed when the server process exits?