Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dev/clone2 #133

Merged
merged 2 commits into from
Nov 4, 2024
Merged

Dev/clone2 #133

merged 2 commits into from
Nov 4, 2024

Conversation

sevenautumns
Copy link
Collaborator

No description provided.

| CloneFlags::CLONE_NEWNS
| CloneFlags::CLONE_NEWIPC
| CloneFlags::CLONE_NEWNET,
None,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should think about tracking and reporting which child exited unexpectedly. Not for this PR, but in general. We could assign a new signal for each child.

clone3 requires an additional dependency and is fairly noisy to use.
clone2 instead, makes the program more readable.
@dadada dadada closed this Nov 4, 2024
@dadada dadada reopened this Nov 4, 2024
@dadada dadada merged commit 8884c9a into main Nov 4, 2024
24 checks passed
@dadada dadada deleted the dev/clone2 branch November 4, 2024 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants