Excerpts from Brian Aker's message of Tue Jan 03 18:55:34 -0800 2012: > Hi, > > On Jan 3, 2012, at 8:49 AM, Clint Byrum wrote: > > > This seems a lot more complicated than what we have now, which is a > > single call which the child calls when its ok to let the parent exit. > > A better solution is to have the child fork early after it has opened up a > pipe and have the parent report its state via the pipe (this is the sort of > method I recently added to Gearman workers so that they could be shutdown). > > Currently what we have relies on signals to be available, which is not really > the best approach.
Thats exactly what I have here: https://code.launchpad.net/~clint-fewbar/drizzle/no-sigusr1/+merge/87387 On second look, I think the way I'm handling some errors may need some work. I'm not sure perror+exit is the right thing to do on close error, though I think its pretty unlikely there'd even be an error. Anyway, I think that branch solves the problem in the way you describe. _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
