1
  1. Are there processes, once suspended (by ctrl-z), can't run correctly after resume (by fg)? What kinds are they?
  2. Are there processes that can't be suspended at all? What kinds are they?

I just want to know if it is always safe to suspend a process.

Thanks.

Improve this question
13
  • Tim, from your other question about top, I am curious what your stopped processes are. what does ps -e -o state,pid,cmd | grep ^T, show, if anything?
    – Doug Smythies
    Apr 25, 2015 at 2:04
  • see unix.stackexchange.com/questions/198478/… What do you mean by grep ^T?
    – Tim
    Apr 25, 2015 at 2:10
  • Well, a process in uninterruptible sleep can't be stopped, woken up, killed, or otherwise affected. Process state T, which is what Doug is asking for, is "stopped, either by a job control signal or because it is being traced" (see man ps).
    – muru
    Apr 25, 2015 at 2:15
  • @muru: you mean suspension doesn't work on them, or they can be suspended but will not run correctly after suspension?
    – Tim
    Apr 25, 2015 at 2:17
  • @Tim Nothing works on them. They are effectively immune to everything except whatever caused the uninterruptible sleep (which is usually waiting for some resource).
    – muru
    Apr 25, 2015 at 2:18

1 Answer 1

Reset to default
1

Full screen terminal applications ( think nano ) that are badly written/broken can fail to resume properly in that they don't repaint the screen correctly after its contents changed while the program was suspended. Well behaved applications notice when they have been suspended and resumed and will repaint the screen properly. That's about it.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .