tree 63fb8ca636108b358012da9cf8e005e9569a501b
parent 8cd1dbae32d9303caac3a473d3332f17bc98c921
author Gregory P. Smith <greg@krypto.org> 1603566455 -0700
committer GitHub <noreply@github.com> 1603566455 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJflHt3CRBK7hj4Ov3rIwAAdHIIAJt4tkF4YOW4aU8C9ioJ9CHP
 +ePnljXzP6jU7DReGGbWZwqm8OPbTrubDgQBDD5xn1BpA0nt4dtVGeBdWj8NxLPW
 k5Xr/JhaIaI48w6if/YhFC/18Ot0jQ3Cv0YGseSM8CrW5ByYlMyCG9jyLa/LAQBK
 kOI8zl5LYVBvgMe9ELpjOwR85kviE4IJQkENGCqxOoFUEmZcJodKjiiuF22cWZNo
 SuIFVFURVgITS3egIDbX6a74/HMojL642XJNCEz8szIPdiSDskcCK1IyHe1bWxH4
 3Sr9+wgZ1XKgn9sSvplxnYnu4XcUiAYkNJXcWHBsXQvm9Si+e2sa3/ob0zIob1s=
 =mYft
 -----END PGP SIGNATURE-----
 

bpo-35823: Allow setsid() after vfork() on Linux. (GH-22945)

It should just be a syscall updating a couple of fields in the kernel side
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.

A breadcrumb _suggesting_ that it is not allowed on Darwin/macOS comes from
a commit in emacs: https://lists.gnu.org/archive/html/bug-gnu-emacs/2017-04/msg00297.html
but I don't have a way to verify if that is true or not.
As we are not supporting vfork on macOS today I just left a note in a comment.