Author zarkdav
Recipients zarkdav
Date 2010-06-30.15:54:54
SpamBayes Score 0.282655
Marked as misclassified No
Message-id <1277913297.34.0.963310724242.issue9127@psf.upfronthosting.co.za>
In-reply-to
Content
http://pastie.org/1025197

Is it deemed acceptable that setting up one's own SIGCHLD handler breaks communicate()?

I did not find it in the documentation.

With the above workaround one can mix communicate() processes with processes spawned in the background that one's too lazy to wait for.
History
Date User Action Args
2010-06-30 15:54:57zarkdavsetrecipients: + zarkdav
2010-06-30 15:54:57zarkdavsetmessageid: <1277913297.34.0.963310724242.issue9127@psf.upfronthosting.co.za>
2010-06-30 15:54:55zarkdavlinkissue9127 messages
2010-06-30 15:54:54zarkdavcreate