1 Answer
1

It means the process has received a STOP signal, and won't do anything much until it receives a CONT signal, not even terminate.

The most common source of STOP signals is the user hitting ^z while the process is in the foreground, and the common way to send a CONT afterwards is typing fg or bg which continue the process in the foreground and background respectively.

Another way to send STOP to a process is kill -STOP $pid. Similarly, CONT can be sent to a process with kill -CONT $pid.

Since you sent TERM signals to the processes, I assume you want them to terminate. For that to happen, the processes must receive CONT signals. You can send those by typing kill -CONT 8754 8767 in a terminal window.

Would sending a CONT signal allow the script to run until it had completed? Or would it cause the script to terminate immediately?
–
JonMar 21 '12 at 14:26

The process continues what it was doing (before STOP) upon receiving a CONT. If you sent a TERM (by kill $pid for example) while it was stopped, however, it will then (belatedly) respond to that TERM and terminate.
–
EroenMar 21 '12 at 14:48

Hmm, so I sent a TERM by running kill 8754 which should cause the process to eventually terminate right? Do you know which state a process would be in while it's getting round to terminating? Given that the process entered the STOP state, as if it had received a STOP signal from kill -STOP 8754, could that also happen if it was sent a TERM signal?
–
JonMar 21 '12 at 16:28

A stopped process will not terminate due to a TERM signal until it is continued. It will terminate immediately if it receives a KILL signal, even while stopped. I assume a process will be in Run state when it terminates. I'm not very familiar with PHP, and don't know how to tell why a process stopped, sorry. Generally, though, processes don't stop but terminate when they receive TERM.
–
EroenMar 21 '12 at 16:49