Missing fork() handling and pitfalls #10
Etiķetes
Nav etiķešu
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Nav atskaites punktu
Nav atbildīgo
1 dalībnieki
Paziņojumi
Izpildes termiņš
Izpildes termiņš nav uzstādīts.
Atkarības
Nav atkarību.
Atsaucas uz: crtxcr/exile.h#10
Notiek ielāde…
Atsaukties uz šo jaunā problēmā
No description provided.
Dzēst atzaru "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We don't do fork()/clone() ourselves, opening the door for many pitfalls, e. g. we inherit open file descriptories which may enable bypassing of the policies we set. Otoh, some open fd's may actually be desired.
We must either offer a safe fork()/clone() or check that the current process is in a reasonable state and/or transform to that state.