Closed xibz closed 5 years ago
@nmeyerhans - Thanks for the comments! Resolved them.
@samuelkarp - Fixed up the issues and thanks for the SIGTERM
vs SIGQUIT
explanation!
@samuelkarp - Fixed up the issues and thanks for the
SIGTERM
vsSIGQUIT
explanation!
Except that is the default behavior, but not the behavior of this application. In the signal handlers set up in machine.go (see installSignalHandlers()
), INT and TERM are translated to CtrlAltDel events to the VM, which may or may not actually translate that event into a VM termination. SIGQUIT actually results in a hard shutdown of firecracker, which is why that's what I suggested we use here.
In the signal handlers set up in machine.go (see installSignalHandlers()), INT and TERM are translated to CtrlAltDel events to the VM, which may or may not actually translate that event into a VM termination. SIGQUIT actually results in a hard shutdown of firecracker, which is why that's what I suggested we use here.
@nmeyerhans That makes sense. @xibz, SIGQUIT is appropriate to use here, but needs an explanatory comment like the one @nmeyerhans provided.
@nmeyerhans and @samuelkarp - Done
A very basic integration test that ensures that communication can occur on the unix socket.
Signed-off-by: xibz impactbchang@gmail.com
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.