+1 for screen, tmux, or Docker ( or screen/tmux in Docker ). They all work really well for reattaching to a running process to view the display. nohup works, but I've never had good luck with it.
Regards, - Robert On Tue, Nov 8, 2022 at 3:25 PM Russell Senior <[email protected]> wrote: > Have you tried screen (or tmux) to see if it does what you want? With > screen (I don't use tmux, so not sure), you can detach and reattach to the > session, and all your windows within that session are still there and > running. I think the limitation might be that GUI stuff isn't in the > session, so those kinds of processes aren't preserved. > > On Tue, Nov 8, 2022 at 1:41 PM American Citizen <[email protected] > > > wrote: > > > Hi: > > > > I am running the KDE Plasmashell desktop, but it has memory leaks and > > eventually I will run out of system memory. > > > > If I logout, I will lose certain running jobs, which I really want to > > keep running. > > > > However if I start a shell, and do the %jobs -l command, nothing is > > there, so I cannot use %disown -r command nor prepend nohup in front of > > some command line execution with a background exec &. > > > > Just how can I attach a nohup to certain running pids, such that if I > > have to logout of the desktop session, these jobs still keep running? > > > > So far, the examples I have seen of nohup and disown, assume that one > > has a current shell open. They don't discuss what happens after the fact? > > > > Currently, if I logout of the desktop session, or restart the desktop, I > > lose the running programs. > > > > Any idea on how to stop this? > > > > > > > > >
