Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 8026

Advanced users • Re: lxterminal commands

$
0
0
When you put a job in the background with "&", it is given a local PID starting with 1, then 2 etc. That PID is what you see in the "[1]" message.
That is properly called the shell's job number. The process ID is the bigger number outside the brackets (and in jobs -l), which is needed to kill the job from outside of the current shell.
The thing I don't understand is why the lxterminal you ran first, in the background, terminates and the new foreground one takes over control of the windows. When I try that the first background one keeps running and the second foreground command ends.
Assuming we are typing inside an lxterminal window, then every new lxterminal command, foreground or background, should promptly exit (unless given option --no-remote). It must always be the oldest instance that continues to handle the windows. There is no portable way for a new process to steal the RAM and file descriptors from an existing copy.

bash does not print any "Done"-like messages at all for foreground jobs, unless they terminate abnormally (by fatal signal). You are just supposed to notice that you have a prompt again.

Statistics: Posted by jojopi — Mon Mar 11, 2024 10:44 am



Viewing all articles
Browse latest Browse all 8026

Trending Articles