Open fohrloop opened 3 months ago
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:
import logging
import signal
logger = logging.getLogger(name)
def handler(signum, frame): logger.warning(f"Received {signum} signal. Doing nothing.")
signal.signal(signal.SIGHUP, handler)
Related: https://github.com/fohrloop/wakepy/issues/203
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: