Don't terminate vmd(8) when we lost the control connection.

When a start vm request is received from vmctl via the control socket,
vmd's control process forwards it to the parent to trigger the action.
A response is received later, in an async way, and send back to vmctl
that is supposed to wait for it.  But now, if vmctl got terminated
before receiving the response, vmd fails to find the control
connection.  In this case it should not abort, print and warning, and
ignore the error.  The fix is a simple as changing a return (-1) to a
return (0).

This fixes an issue that was reported by mlarkin@

0 files changed, 0 insertions, 0 deletions