This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: exec()'s behavior when ppid == 1


At 09:10 PM 6/2/2003 -0400, Christopher Faylor wrote:
>On Mon, Jun 02, 2003 at 08:21:33PM -0400, Pierre A. Humblet wrote:
>>Chris,
>>
>>When Windows spawns a Cygwin process A, A has ppid 1 and ppid_handle 0.
>>If process A execs B, Cygwin keeps A alive. If B then execs C, B stays 
>>alive too. When C terminates, B and A follow suit and Windows goes on its
way.
>>So far so good.
>>
>>Now suppose that A forks X and A terminates. Windows goes on its way
>>right away.
>>Meanwhile X (which now has ppid 1 but a non zero ppid_handle) execs B
>>and X is kept alive. If B execs C, B is also kept alive. When C 
>>terminates, B and X follow suit.
>>
>>Q: Why does it help to keep X and B alive until C terminates?
>
>I'd prefer this patch, if it still works as desired.
>It seems to in my limited testing.

Right, that's cleaner. It seems to work fine here also.

Pierre


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]