netns: add documentation on how to go back on default netns #590
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
svinota
reviewed
Mar 1, 2019
| @@ -222,6 +222,11 @@ def setns(netns, flags=os.O_CREAT, libc=None): | |||
| - O_CREAT -- create netns, if doesn't exist | |||
| - O_CREAT | O_EXCL -- create only if doesn't exist | |||
|
|
|||
| Note that "main" netns as no name. But you can access it with:: | |||
|
Another way is to open |
|
Probably I have to dump it also to the docstring. |
svinota
added a commit
that referenced
this pull request
Mar 1, 2019
- pushns() -- save the current netns - popns() -- restore the last saved - dropns() -- discard the last saved Bug-Url: #590
|
As an idea, looks at the commit — e7810d9 |
|
Thank you! |
|
Thank you for the issue. I had to implement it a long time ago, but didn't. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I didn't find any reference in the documentation for this annoying thing. There is perhaps a better way, but in all cases I think that it's a good idea to add documentation on it.