Re: [patch] SIGCHLD and the forked calls controller

2004-03-24 Thread Angus Leeming
Angus Leeming wrote: > I do believe that we've got there. Attached is the final patch with > a description of the design embedded in forkedcontr.C. > > I'll commit this tomorrow to give everybody a fair chance to > complain loudly. > > Many thanks to John Levon for holding my hand through all th

Re: [patch] SIGCHLD and the forked calls controller

2004-03-24 Thread Angus Leeming
Kuba Ober wrote: >> > I have a slightly guilty feeling that this patch will need to be >> > re-implemented in a native Win32 port (SIGCHLD is not supported >> > on Windows.) Any ideas about how it would look? > > I am repeating myself, for which I shall accept reasonable > punishment (tm), yet is

Re: [patch] SIGCHLD and the forked calls controller

2004-03-24 Thread Kuba Ober
> > I have a slightly guilty feeling that this patch will need to be > > re-implemented in a native Win32 port (SIGCHLD is not supported on > > Windows.) Any ideas about how it would look? I am repeating myself, for which I shall accept reasonable punishment (tm), yet is there anything wrong with

Re: [patch] SIGCHLD and the forked calls controller

2004-03-24 Thread Angus Leeming
John Levon wrote: > I couldn't know less about Windows. Less than what? Less than me? Naa. That'd be negative amounts of know. -- Angus

Re: [patch] SIGCHLD and the forked calls controller

2004-03-24 Thread John Levon
On Wed, Mar 24, 2004 at 11:48:51AM +, Angus Leeming wrote: > No, of course not. Let's assume that I was confused and move on. Are > you happy for me to commit the patch? If so, I'll do so this evening. Why not? > I have a slightly guilty feeling that this patch will need to be > re-impleme

Re: [patch] SIGCHLD and the forked calls controller

2004-03-24 Thread Angus Leeming
John Levon wrote: > On Wed, Mar 24, 2004 at 11:21:44AM +, Angus Leeming wrote: > >> I thought that I read that the handler could be implemented as a >> separate thread? > > You'd be one up on me if POSIX allows this. Do you have a reference? No, of course not. Let's assume that I was confus

Re: [patch] SIGCHLD and the forked calls controller

2004-03-24 Thread John Levon
On Wed, Mar 24, 2004 at 11:21:44AM +, Angus Leeming wrote: > I thought that I read that the handler could be implemented as a > separate thread? You'd be one up on me if POSIX allows this. Do you have a reference? cheers john

Re: [patch] SIGCHLD and the forked calls controller

2004-03-24 Thread Angus Leeming
John Levon wrote: > On Wed, Mar 24, 2004 at 10:55:11AM +, Angus Leeming wrote: > >> 1 if (current_child == -1) >> 2 return; >> >> // Block the SIGCHLD signal. >> 3 sigprocmask(SIG_BLOCK, &newMask, &oldMask); >> >> // Wait for an existing signal to finis

Re: [patch] SIGCHLD and the forked calls controller

2004-03-24 Thread John Levon
On Wed, Mar 24, 2004 at 10:55:11AM +, Angus Leeming wrote: > 1 if (current_child == -1) > 2 return; > > // Block the SIGCHLD signal. > 3 sigprocmask(SIG_BLOCK, &newMask, &oldMask); > > // Wait for an existing signal to finish being processed. > 4 w

Re: [patch] SIGCHLD and the forked calls controller

2004-03-24 Thread Angus Leeming
Angus Leeming wrote: > I do believe that we've got there. Attached is the final patch with > a description of the design embedded in forkedcontr.C. > > I'll commit this tomorrow to give everybody a fair chance to > complain loudly. > > Many thanks to John Levon for holding my hand through all th

Re: [patch] SIGCHLD and the forked calls controller

2004-03-24 Thread John Levon
On Wed, Mar 24, 2004 at 10:31:02AM +, Angus Leeming wrote: > > By all means burn my extremities, but I believe that tinyurl URLs > > are cached, and expire after a certain time. > > At the very top of http://tinyurl.com : > > Welcome to TinyURL!? > > Are you sick of posting URLs in emails o

Re: [patch] SIGCHLD and the forked calls controller

2004-03-24 Thread Angus Leeming
John Levon wrote: > On Tue, Mar 23, 2004 at 10:40:27PM +, Angus Leeming wrote: > >> I do believe that we've got there. Attached is the final patch with >> a description of the design embedded in forkedcontr.C. > > By all means burn my extremities, but I believe that tinyurl URLs > are cached

[patch] SIGCHLD and the forked calls controller

2004-03-23 Thread Angus Leeming
I do believe that we've got there. Attached is the final patch with a description of the design embedded in forkedcontr.C. I'll commit this tomorrow to give everybody a fair chance to complain loudly. Many thanks to John Levon for holding my hand through all this. -- AngusIndex: src/ChangeLog

Re: [patch] SIGCHLD and the forked calls controller

2004-03-23 Thread John Levon
On Tue, Mar 23, 2004 at 10:40:27PM +, Angus Leeming wrote: > I do believe that we've got there. Attached is the final patch with a > description of the design embedded in forkedcontr.C. By all means burn my extremities, but I believe that tinyurl URLs are cached, and expire after a certain t