Somebody may have a better idea, but knowing you may lose the session you generally would want to start any jobs with nohup and make sure any output of the job is sent to log files for later processing when you check and see the job has ended. You might consider a job execution framework such as Apache Airflow that would handle all the job creation and management for you with a web page management dashboard.
On Tue, Nov 8, 2022 at 1:42 PM American Citizen <website.read...@gmail.com> 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? > > > >
