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
It's not designed in this way. You certainly could give script permissions to kill websocketd and do this upon exit on Linux/OSX but instead (if you want one-time run) you could leave signal in form of some empty file or other way... then refuse to proceed with the script if that file present.
It is possible to quit websocketd when the executed script ends?
The text was updated successfully, but these errors were encountered: