Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an error in my error logs that I am trying to figure out but I don't know what to be looking for when it says Child Process.

I understand that its a process done by a parent, but that's an obvious explanation. What does it mean?

Its usage in my error log: child process 1276 still did not exit, sending a SIGKILL

share|improve this question

migrated from Oct 17 '12 at 9:32

This question came from our site for professional and enthusiast programmers.

to find out what is the application which runs as child process, do ps -p 1276 or, in general, ps -p PID – Victor Sorokin Oct 16 '12 at 18:48
ahh, and the child process is the process which was spawned by your process (which seems to be php application) – Victor Sorokin Oct 16 '12 at 18:49
what does this have to do with sql and/or php? – Marc B Oct 16 '12 at 18:53
Marc, I really don't know what causes it, those were two of my guesses. – Daniel Fein Oct 16 '12 at 19:05

Very very basically, "processes" are running programs. They're referenced by a number, usually called a "process ID" or "PID". That's the "1276" in the error message.

A "child process" is a process started by some other process (which is the "parent process"). There's really not much more to it than that, in this case.

What this error message means, is that the parent process tried to tell one of its children to end (probably by sending a SIGTERM signal to it) and that didn't work. So the parent process got mean and sent a SIGKILL.

(Some signals can be ignored. SIGTERM is technically one of those; it's a sort of "please exit now" message; a process should clean up and exit upon seeing it. SIGKILL is more like "DIE, foul process! DIEEE!!!", and can't be ignored or even handled, so the receiving process can't clean up or anything -- it just dies. Since it's so potentially messy, it's generally only used for cases where stubborn processes refuse to end politely.)

share|improve this answer
+1. Apache 1.x had a similar comment in the code: "die child scum" :) – Jack Oct 17 '12 at 2:12

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.