This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients Yonatan Goldschmidt, gregory.p.smith, izbyshev, koobs, pablogsal, ronaldoussoren
Date 2020-10-24.18:12:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
regarding excluding the setsid() case: I was being conservative as I couldn't find a reference of what was and wasn't allowed after vfork.

I found one thing suggesting that on macOS setsid() was not safe after vfork().  But that appeared to be a Darwin-ism.  I expect that is not true on Linux as it should just be a syscall updating a couple of fields in the process info.  Confirming, in glibc is appears to be a shim for the setsid syscall (based on not finding any code implementing anything special for it) and in uclibc (*much* easier to read) it is clearly just a setsid syscall shim.

I'll make a PR to undo the setsid restriction given we're Linux only.
Date User Action Args
2020-10-24 18:12:19gregory.p.smithsetrecipients: + gregory.p.smith, ronaldoussoren, koobs, izbyshev, pablogsal, Yonatan Goldschmidt
2020-10-24 18:12:19gregory.p.smithsetmessageid: <>
2020-10-24 18:12:19gregory.p.smithlinkissue35823 messages
2020-10-24 18:12:19gregory.p.smithcreate