News for hackers. Stuff that matters.
Re:Sequential and parallel execution of long-running shell c... by aeblyve on Thursday March 21, 2024 @11:59AM (#39780302)
I usually just need to run one big interactive job on a server, in which case I just do

tmux my-command Ctrl-b d (detach) logout, go to bed, sleep, whatever log back into the server, tmux attach

Would there be an advantage to using this over that?

Re:Sequential and parallel execution of long-running shell c... by eddd-ddde on Thursday March 21, 2024 @01:46PM (#39781926)
Probably not in practice. You do save that ctrl-b keypress tho.
Re:Sequential and parallel execution of long-running shell c... by kjkjadksj on Sunday March 24, 2024 @12:18PM (#39808111)
Ampersand also works, no tmux needed
Re:Sequential and parallel execution of long-running shell c... by renewiltord on Sunday March 24, 2024 @01:55PM (#39808885)
Does it? I must have always configured differently but sighup. Usually have to disown preventing sighup!
Re:Sequential and parallel execution of long-running shell c... by ec109685 on Sunday March 24, 2024 @02:20PM (#39809070)
Prefix with nohup
Re:Sequential and parallel execution of long-running shell c... by Nukesor on Thursday March 21, 2024 @04:43PM (#39784155)
Nope. Pueue is designed to handle your usecase times 5+.

I'm still using it for your usecase, as I'm already used to the interface by now :D.

Re:Sequential and parallel execution of long-running shell c... by Alifatisk on Sunday March 24, 2024 @10:08AM (#39807326)
Your usecase reminds me of GNU screen
Re:Sequential and parallel execution of long-running shell c... by squigz on Sunday March 24, 2024 @12:51PM (#39808361)
They're both terminal multiplexers. In my experience tmux is a much better experience though