Re: Calls to system() blocks return of SIGCHLD signal

2004-10-07 Thread Christopher Faylor
On Thu, Oct 07, 2004 at 11:30:42AM -0500, Brian Ford wrote: >On Wed, 6 Oct 2004, Christopher Faylor wrote: > >> On Wed, Oct 06, 2004 at 12:24:48PM -0400, Remy Gauthier wrote: >> >We have noticed (on V1.5.10-1 and V1.5.11-1) that after a call to >> >system(), the handlers were not being called after

Re: Calls to system() blocks return of SIGCHLD signal

2004-10-07 Thread Brian Ford
On Wed, 6 Oct 2004, Christopher Faylor wrote: > On Wed, Oct 06, 2004 at 12:24:48PM -0400, Remy Gauthier wrote: > >We have noticed (on V1.5.10-1 and V1.5.11-1) that after a call to > >system(), the handlers were not being called after the child process > >stopped. This program has this behaviour (

Re: Calls to system() blocks return of SIGCHLD signal

2004-10-06 Thread Christopher Faylor
On Wed, Oct 06, 2004 at 12:24:48PM -0400, Remy Gauthier wrote: >We manage synchronous events through calls to system(), and >asynchronous events via fork() and a SIGCHLD handler. We have noticed >(on V1.5.10-1 and V1.5.11-1) that after a call to system(), the >handlers were not being called after

Calls to system() blocks return of SIGCHLD signal

2004-10-06 Thread Remy Gauthier
We manage synchronous events through calls to system(), and asynchronous events via fork() and a SIGCHLD handler. We have noticed (on V1.5.10-1 and V1.5.11-1) that after a call to system(), the handlers were not being called after the child process stopped. This program has this behaviour (remov