parent and child process

[orthanc]

okay i have written the follwing c program. i have one query. if the parent process is killed shouldn't the child process also be killed. because when i execute the program, after the parent gets killed, the child process is executed after a delay of 10 sec (as given by sleep)

#include<stdio.h>
#include<signal.h>

int main&#40;&#41;
&#123;
 int a=10,b=10;
 
 
 
 if&#40;fork&#40;&#41;&#41; 
 &#123;
  /* Parent process */
  
        printf&#40;"\n\n"&#41;;
  system&#40;"ps"&#41;;
  
  
  printf&#40;"\n Values of a and b in the parent process &#58; %d, %d",a,b&#41;;


  printf&#40;"\n Process id &#58; %d\n\n",getpid&#40;&#41;&#41;; 
  printf&#40;"\n\n\n"&#41;;
                  kill&#40;getpid&#40;&#41;,SIGKILL&#41;;

  
 &#125;
 else
 &#123;
  /* The Child Process */
  sleep&#40;10&#41;;
  printf&#40;"\n\n"&#41;;
  system&#40;"ps"&#41;;

  a++;
  b+=5;
  printf&#40;"\n"&#41;;
  printf&#40;"\n Process id of Child %d ",getpid&#40;&#41;&#41;;
  
  printf&#40;"\n Process id of Parent %d ", getppid&#40;&#41;&#41;; 

  
  printf&#40;"\n\n Values of a and b in child process &#58; %d,%d",a,b&#41;;
  


 &#125;

 return 0;
&#125;

[Morgoth]

Have you looked up what a process does when it recieves a SIGKILL?
If the process calls exit(0) upon recieving SIGKILL, then the child processes are automatically inherited by process 1.

[scm]

Would you want to die when your parent dies?

You could arrange for the parent to catch signals (except 9, obviously) and terminate its child (you'd have to save the return value from the fork(), of course).

[scm]

Have you looked up what a process does when it recieves a SIGKILL?
If the process calls exit(0) upon recieving SIGKILL, then the child processes are automatically inherited by process 1.

All orphaned processes are inherited by the init process regardless of how their parent terminates.

[mohit dhawan]

i think the child dies only if it shares the same process space as the parent

[the_unforgiven]

i think the child dies only if it shares the same process space as the parent

No.
Linux implements fork() as "copy-on-write" - most modern Unices do it the same way..
So, as long as you don't do exec() after fork(), both the processes still share the proc space.
Even then, when the parent terminates (without explicitly killing the child), the child is inherited by init (pid 1) - as was told by scm.

You can find the detailed discussion of this topic in W. Richard Stevens' "Advanced Programming in the Unix environment" and Maurice J. Bach's "The design of the UNIX operating system".