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
Sometimes it might be useful to be able to ssh into a server, start a python process and disconnect from the server knowing that the process will continue running.
Todo:
what does this require?
Why a server without desktop environment stops executing a task?
is the solution such that could be included in wakepy?
I did a quick look on this topic. I'm not an expert on this but it seems that the reason why a script typically stops when someone exits SSH is a SIGHUP signal which gets send to all processes when terminal window with SSH connection is closed. The typical solutions involve using nohup, screen or tmux. This is not about keeping CPU awake, but about keeping a process from not getting stopped by a HUP signal. Therefore, I kind of think this might be out of scope of wakepy. If nohup yourscript.py & just works, why would wakepy need to implement a solution? If there was a solution, should that be some separate mode, like ignore.hup ?
In order to really consider adding a ignore.hup mode, should:
List at least one real use case, and explain why wakepy would be needed instead of nohup, screen or tmux?
Is this technically possible? Would it be as simple as:
Also could be possible to make wakepy ignore SIGHUP, by default but that's probably a bit too intrusive. Another possibility would be to add some nohup=False parameter to keep.running() and keep.presenting().
Sometimes it might be useful to be able to ssh into a server, start a python process and disconnect from the server knowing that the process will continue running.
Todo:
Notes:
The text was updated successfully, but these errors were encountered: