----- Original Message ----- > On 01/06/16 10:20, Bastien Nocera wrote: > > >> On Sun, May 29, 2016 at 06:51:20PM -0600, Chris Murphy wrote: > >>> So there's tmux, screen, curl, wget, and probably quite a few others > >>> that don't necessarily get daemonized that are probably affected. > >> > >> I would really like to see a solution whereby tmux and screen _just > >> work_ without any required changes to user behavior. They're basically > >> commands which _indicate_ "I want a new session that persists". > > > > Really? The only times I ever used it was to access serial consoles with > > a better emulation than separate apps. > > You've obviously never had to run something that's going to take hours > or days to complete on a remote server and not wanted it to abort half > way through because of a network glitch then. Yeah, I never used nohup. *roll eyes* > That's when I use screen, either just setting running something in the > background, or leaving it connected but knowing it will continue if > anything goes wrong and I can just reattach from a new login. The screen manual says "Screen is a full-screen window manager that multiplexes a physical terminal between several processes (typically interactive shells).". It doesn't say "it persists in the session by default, always, that's always how you're going to use it". -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
