--- Original Message ---
On Tuesday, November 15th, 2022 at 1:51 PM, American Citizen
wrote:
> Using the setsid() CLI command is exactly the right choice here. I have
> restarted the Plasma desktop after logging out and back in and the
> programs were still running attached to pid 1 (
Using the setsid() CLI command is exactly the right choice here. I have
restarted the Plasma desktop after logging out and back in and the
programs were still running attached to pid 1 (as desired)
What needs to happen now is to fix that annoying memory leak in
plasmashell task
Thanks for th
Or automatically launch screen from within your .profile.
https://stackoverflow.com/a/20515245
I also alias exit so that I remember to detach instead of exit:
[ ${STY} ] && alias exit="echo You are in a screen: ${STY}."
And I can use \exit if I really want to exit.
Regards,
- Robert
On Mon, N
fwiw, i am a `screen` addict. i do a lot of builds on distant systems
over ssh, and try to always remember to start screen.
randy
Is magma.exe the math application listed here?
http://magma.maths.usyd.edu.au/magma/download/x86_64-linux/
According to your process list that you posted, it looks like you use X11 with
KDE plasma. You load up konsole, which starts bash and then you start magma.exe
from there.
Likely it does s
The setsid() command does exactly what I need when starting programs of
this type
See https://www.man7.org/linux/man-pages/man1/setsid.1.html about this
Now, just to figure out a way to detach the parent from these children
safely.
Hi:
I did a quick look on the internet for how to detach a child process
from the parent, but I am afraid that the present running condition of
my tasks are such that disown does not work anymore, nor does nohup work
upon starting the child to prevent the parent from really interrupting
the c
