Delete vfork #6

Closed
opened 2024-03-07 05:10:43 +00:00 by jade · 2 comments
Owner

wait what
wait what
nix forks before calling connect or bind???
and then wait()s on the child pid? wtf?
why???

Edit: we found later that the dubious code, 43d4d75e22, was because of sockaddr_un path length limits. offensive but at least halfway understandable. but surely someone could have left a comment or ... clarified the exact case when this could be required

> wait what > wait what > nix forks before calling connect or bind??? > and then wait()s on the child pid? wtf? > why??? Edit: we found later that the dubious code, https://github.com/nixos/nix/commit/43d4d75e22ea1f7ee2936fe725c1f7ea7a5005e6, was because of sockaddr_un path length limits. offensive but at least halfway understandable. but surely someone could have left a comment or ... clarified the exact case when this could be required
Owner

and it uses vfork too in some instances, though not that specific one

and it uses vfork too in some instances, though not that specific one
jade changed title from Stop doing questionable things with fork to Delete vfork 2024-03-07 20:39:14 +00:00
jade added the
stability
label 2024-03-11 20:01:09 +00:00
Author
Owner
https://gerrit.lix.systems/c/lix/+/567
jade closed this issue 2024-04-16 03:02:31 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/lix#6
No description provided.