0

Do you know the Windows shutdown process is implemented? Does it has some criteria to avoid inter-process communication problems between child and parent processes?

This question originated from an suspicious (apparent) coincidence situation on a script terminating successfully and shutdown of the machine [over-described on the original written question replied by Falcon Kirtaran].

jpmartins
  • 1,404
  • 2
  • 12
  • 14
  • This question was written on 2am local time, I was tired. Sorry about that. Basically I want to know more about the details of the shutdown process of windows. – jpmartins Apr 14 '12 at 16:26
  • Re-written the question, now it is a real question. Thanks. – jpmartins Apr 14 '12 at 16:43

1 Answers1

1

I am not really sure what you are asking. However, if you are interested in why the process appeared to terminate as though it was just about to finish normally, it's because windows first sends a signal to all the running programs as though the user exited them normally (eg. by pressing the X button in the top right of the window). If they do not close within a set period of time, the system will either force-terminate them or give the user the option to do so ("end task").

Falcon Momot
  • 25,244
  • 15
  • 63
  • 92
  • Thanks for the reply. Does windows first signals the child process and then the parent ones? Is there any order or sequence to the termination process, or are the signal sent in parallel from an arbitrary sequence? – jpmartins Apr 14 '12 at 16:25
  • 1
    @jpmartins: Windows does not distinguish between parent and child processes. All processes are considered peers. The shutdown message is not sent in any particular order. – Harry Johnston Apr 14 '12 at 23:47