You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's how to catch CTRL_CLOSE_EVENT in Windows (end task or close console window). There was some effort to translate this to SIGTERM but requires blocking which isn't compatible with the signal.Notify model.
The right way to stop a service would be sc stop or net stop and I believe these stop signals are sent during reboot/shutdown, I'll have to double check. If they are this is probably just "interesting" and adding this would help in the case of someone killing the process instead of stopping the service gracefully.
The text was updated successfully, but these errors were encountered:
On Windows, the CTRL_CLOSE_EVENT, CTRL_LOGOFF_EVENT, and CTRL_SHUTDOWN_EVENT events now generate a syscall.SIGTERM signal, similar to how Control-C and Control-Break generate a syscall.SIGINT signal.
Here's how to catch
CTRL_CLOSE_EVENT
in Windows (end task or close console window). There was some effort to translate this toSIGTERM
but requires blocking which isn't compatible with thesignal.Notify
model.The right way to stop a service would be
sc stop
ornet stop
and I believe these stop signals are sent during reboot/shutdown, I'll have to double check. If they are this is probably just "interesting" and adding this would help in the case of someone killing the process instead of stopping the service gracefully.The text was updated successfully, but these errors were encountered: