[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: vfork()

Vfork is a combination of fork() and exec().

So the pid has to be different...unless CLONE_PID flag is set...[which 
is normally done by kernel] after vfork() the child and parent have 
different address space....

Ketan

Rupa wrote:
>  
> 
> Hello,
>   I have a small doubt regarding the working of vfork() system call. 
> when a call to vfork() is made, the child process created will be 
> sharing the address space of the parent. I want to know whether the pid 
> returned by the vfork() is same as the pid of parent. Because in case of 
> fork() system call, child process differs from the parent by pid. I want 
> to know regarding pid in case of vfork() system call.
> 
>  
> 
> If I am wrong correct me.
> 
>  
> 
> Thanks in advance,
> Rupa
> 


-- 


In order to get a fully working kernel, you have to follow the steps 
below: -
Walk around your computer widdershins 3 times, chanting "Linus is 
overworked, and
he makes lousy patches, but we love him anyway". Get your spuouse to do 
this too
for extra effect. Children are optional. - Apply the patch included in 
this mail -
Call your system "Super-67", and don't forget to unapply the patch 
before you later
applying the official 1.3.68 patch. - reboot (Linus Torvalds, announcing 
another kernel patch.)

	

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/