SIGKILL again? That implies it's been KILLed before and either survived, or come back. Either way, we don't like zombie processes in these parts.
/me fetches the really big process remover/cattle prod.
And if you dare take the risk of lobbing a SIGCHLD at the parent process, most of the time, that doesn't even do anything, and now you've been through the stress of signalling a perfectly healthy parent process.
I like to analogise and anthropomorphise signals, but there's no non-depressing way to do this one. SIGCHLD is basically "clean up after your kids, even if that means tidying their corpses away".
Often the parent can't do that or doesn't know how. It's hugging them close and they'll only leave once the parent also leaves.
These things aren't even sentient and that stings a bit.
Here's how I personify the Linux kernel:
Well, that's just bleak.
The way I look at it, parent processes know they will outlast their children unless they deliberately turn them into daemons, traditionally by double forking them. Daemons live on, even when the parent dies.
Fork them kids
-9 means it's serious
Don't you xKill my PRECIOUS!
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.