Re: [PLUG] a question regarding something like nohup or disown
On Tue, Nov 8, 2022 at 11:31 PM Kevin Williams wrote: > Russell, > > Yes, tmux works the same way. > > Rich, > > tmux and screen are command line applications that launch and manage > sub-shells (a shell in a shell). You can remote into a server, like your > shell at your web host, start editing a file, open another window and view > a man page, and then detach from the tmux or screen session, log out of the > remote session, and come back to your running text editor and opened man > page later by reattaching to the same tmux or screen session. > > tmux even supports splitting a terminal window into multiple panes and run > apps side by side or top and bottom. I don’t know if screen supports side > by side. > I think screen does support side-by-side, but I don't use it so I can't say for sure. Tmux does not support serial consoles natively though, which I use extensively, and that is why tmux is dead to me. ;-) > > On Tue, Nov 8, 2022 at 9:28 PM, Tomas Kuchta > wrote: > > > I am curious what distro are you running? > > > > I am running openSuSE and usually clock up about half year on the KDE > > session before some update forces reboot. I keep it running 24/7 to pull > > emails local, monitor environment (temp/humidity), VPN, remote desktop, > > other services. I have not experienced memory leaks. > > > > Tomas > > > > On Tue, Nov 8, 2022, 21:41 American Citizen > > 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? > >> > >> > >> > >>
Re: [PLUG] PLUG Venue Options
Okay, to follow up with results of my poll (now that several days have gone by and new responses have tailed off): 21 people responded who (selection bias) all thought PLUG living into the future was important. 15 of 21 said they were ready to return to in-person meetings 5 of 21 said "maybe" 1 of 21 said "no" (not ready to return to in-person meetings 5 of 21 said they could help recruit speakers! the rest were lame-o's (just teasing!) 11 of 21 said that location was important to them 10 of 21 said that location was not important to them There were 13 responses to the free-form location "constraints" question: 2 of the 13 basically said "I can't make it because of conflicts" of the remaining 11, they said a combination of this (I'm paraphrasing/lumping a little): 2 people preferred the west side, one of which went further to eschewed downtown; 3 people said they preferred a central location; 3 people said they desired convenient parking; 5 people specifically desired good public transportation. I made some exploratory overtures about a particular downtown location, but it's looking rather a longshot at the moment (still no replies). Given an actual in-hand venue and no obvious alternatives at the moment (unless someone has other suggestions), I propose we try out Michael's location and go from there. How do people feel about that? -- Russell Senior russ...@personaltelco.net On Thu, Nov 3, 2022 at 3:18 PM Russell Senior wrote: > Hi folks! > > I'm interested in getting a virtual show of hands on who is ready to start > meeting in person again and who isn't. I put together a very short Google > Form (4 or 5 questions), or you can reply here or to me privately. Here's > the form: > > > https://docs.google.com/forms/d/e/1FAIpQLSc58ccHKEQrlDoJDud-iRTw9I8jsHIAovb8-MAnGzFYahrD_A/viewform > > On Thu, Nov 3, 2022 at 11:08 AM Michael Dexter > wrote: > >> All, >> >> I have spent months inquiring about the future of PSU as a PLUG venue >> and have nothing conclusive. >> >> I know that public transportation is important to many of you. >> >> Please advise if this address is easily accessible for you: >> >> 5500 SW Dosch Rd, Portland, OR 97239 >> >> It is off Beaverton-Hillsdale Highway near Hillsdale. >> >> Michael Dexter >> PLUG Volunteer >> >
Re: [PLUG] a question regarding something like nohup or disown
Russell, Yes, tmux works the same way. Rich, tmux and screen are command line applications that launch and manage sub-shells (a shell in a shell). You can remote into a server, like your shell at your web host, start editing a file, open another window and view a man page, and then detach from the tmux or screen session, log out of the remote session, and come back to your running text editor and opened man page later by reattaching to the same tmux or screen session. tmux even supports splitting a terminal window into multiple panes and run apps side by side or top and bottom. I don’t know if screen supports side by side. On Tue, Nov 8, 2022 at 9:28 PM, Tomas Kuchta wrote: > I am curious what distro are you running? > > I am running openSuSE and usually clock up about half year on the KDE > session before some update forces reboot. I keep it running 24/7 to pull > emails local, monitor environment (temp/humidity), VPN, remote desktop, > other services. I have not experienced memory leaks. > > Tomas > > On Tue, Nov 8, 2022, 21:41 American Citizen > 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? >> >> >> >>
Re: [PLUG] a question regarding something like nohup or disown
I am curious what distro are you running? I am running openSuSE and usually clock up about half year on the KDE session before some update forces reboot. I keep it running 24/7 to pull emails local, monitor environment (temp/humidity), VPN, remote desktop, other services. I have not experienced memory leaks. Tomas On Tue, Nov 8, 2022, 21:41 American Citizen 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? > > > >
Re: [PLUG] a question regarding something like nohup or disown
+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 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 > > 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? > > > > > > > > >
Re: [PLUG] a question regarding something like nohup or disown
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 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? > > > >
Re: [PLUG] a question regarding something like nohup or disown
On Tue, 8 Nov 2022, Michael Ewan wrote: Somebody may have a better idea, ... screen? tmux? Rich
Re: [PLUG] a question regarding something like nohup or disown
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 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? > > > >
[PLUG] a question regarding something like nohup or disown
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?
