You are not logged in.
Pages: 1
Is it okay to run
nohup makepkg -s? Or what's the right way to leave compilation going when the session logs off? Is there anything that users should be mindful of?
Last edited by abc12345 (2022-09-12 14:26:22)
Offline
To add, I found this thread where someone wanted to start compilation on a remote server, disconnect, and let it run: https://bbs.archlinux.org/viewtopic.php?id=150906
But I don't think it applies to my question because the actual session on the remote server that runs makepkg is not terminated/logged off when the user disconnects from the remote server. And I can't even get makepkg going in the background to start with (without even logging off).
Offline
Becuse makepkg will most likely require some stdin (first)
You could ctrl+z it, then bg %1 and disown %1
You still want to use its logging capabilities (-L) to get an idea what happened while you were not paying attention.
Also look into tmux or gnu screen which allow to de- and re-attach terminal sessions.
Offline
You could get around interaction (when using -s/-r for handling dependencies) by using --noconfirm. But I agree that screen/tmux are the way to go.
Offline
Pages: 1