Re: Preventing propagation of SIGINT to Parent Process - Problem with the child

Originally Posted by
arvidjaar
Actually this seems to be bash-specific and starting with 5.0 bash changed behavior to pretend it also received SIGINT if child received SIGINT. By default it terminates bash. Out of curiosity I checked two shells that were installed besides bash here - mksh and dash. mksh runs both bash process and sleep in the same process group (even though it has -m option), so shell simply gets SIGINT when ^C is pressed. dash runs sleep in different process group so only sleep is killed by ^C but dash sends itself SIGINT in this case and so also terminates.
Too sophisticated for me. It is far from my knowledge.
Any way thank you for taking care of my questions.
Thanks for helping. JCD
__________
server leap 15.0 -- ASUS g75vw KDE leap 15.2 -- ASUS G731GV KDE leap 15.2 -- acer aspire s13 win 10 home -- HP Omen win 10 home - scan EPSON V500 - Brother HL2250DN - Samsung CLP-325W
Bookmarks