Try turning it off and on again

Processes can make their own processes. If you know of such a secondary process, you might still want to terminate the one at the top.

Something like that?

Processes in most operating systems (I'll use Linux, because it's what I know and because...Lemmy) are organized in a tree like structure. There's some initial very low level code used to start the OS, and every other process spawns from that, which is to say they tell the operating system "Hey, please make this process I'm gonna tell you about - allocate resources for it, etc." The operating system creates it and binds that new child process to the first one. The process that spawned the other process is called its parent. The process that just got spawned is called a child. You could also call them root and leaf processes, I suppose, but nobody really does that. Sometimes you want to get rid of all the child processes a process spawns, but leave the running process intact. Sometimes you want to kill the process that spawned everything and also cleanup anything it might have created. There are lots of programming scenarios in which you might want to do either. It really depends on how your application is designed and what it's doing.

That all said, there's a command in Linux called "kill" and you can tell it the process id, process group id, etc. to kill a process or a process group. You can also manipulate what are called SIGNALS. Signals are a whole thing in Linux. They're basically small values you can send to processes at any time and the operating system forces the process to perform some action whenever it receives one of them. SIGTERM basically stands for "SIGNAL: TERMINATE PROCESS." So if you "trap" the SIGTERM, you can basically tell the operating system - whenever this parent process receives a SIGTERM, ignore it. The other processes in the process group - the child processes - all terminate, though, when they receive it.