list processes belonging to a network namespace
I am on Ubuntu 12.04, and the ip
utility does not have ip netns identify <pid>
option, I tried installing new iproute
, but still, the option identify doesn't
seem to be working!.
If I were to write a script (or code) to list all processes in a network-namespace, or given a PID, show which network-namespace it belongs to, how should I proceed ?
(I need info on a handful of processes, to check if they are in the right netns
)
linux process network-namespaces
add a comment |
I am on Ubuntu 12.04, and the ip
utility does not have ip netns identify <pid>
option, I tried installing new iproute
, but still, the option identify doesn't
seem to be working!.
If I were to write a script (or code) to list all processes in a network-namespace, or given a PID, show which network-namespace it belongs to, how should I proceed ?
(I need info on a handful of processes, to check if they are in the right netns
)
linux process network-namespaces
add a comment |
I am on Ubuntu 12.04, and the ip
utility does not have ip netns identify <pid>
option, I tried installing new iproute
, but still, the option identify doesn't
seem to be working!.
If I were to write a script (or code) to list all processes in a network-namespace, or given a PID, show which network-namespace it belongs to, how should I proceed ?
(I need info on a handful of processes, to check if they are in the right netns
)
linux process network-namespaces
I am on Ubuntu 12.04, and the ip
utility does not have ip netns identify <pid>
option, I tried installing new iproute
, but still, the option identify doesn't
seem to be working!.
If I were to write a script (or code) to list all processes in a network-namespace, or given a PID, show which network-namespace it belongs to, how should I proceed ?
(I need info on a handful of processes, to check if they are in the right netns
)
linux process network-namespaces
linux process network-namespaces
edited Jun 30 '15 at 22:00
Gilles
529k12810601585
529k12810601585
asked Jun 30 '15 at 9:52
vyom
133114
133114
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
You could do something like:
netns=myns
find -L /proc/[1-9]*/task/*/ns/net -samefile /run/netns/"$netns" | cut -d/ -f5
Or with zsh
:
print -l /proc/[1-9]*/task/*/ns/net(e:'[ $REPLY -ef /run/netns/$netns ]'::h:h:t)
It checks the inode of the file which the /proc/*/task/*/ns/net
symlink points to agains those of the files bind-mounted by ip netns add
in /run/netns
. That's basically what ip netns identify
or ip netns pid
in newer versions of iproute2
do.
That works with the 3.13 kernel as from the linux-image-generic-lts-trusty
package on Ubuntu 12.04, but not with the 3.2 kernel from the first release of 12.04 where /proc/*/ns/*
are not symlinks and each net
file there from every process and task gets a different inode which can't help determine namespace membership.
Support for that was added by that commit in 2011, which means you need kernel 3.8 or newer.
With older kernels, you could try and run a program listening on an ABSTRACT socket in the namespace, and then try to enter the namespace of every process to see if you can connect to that socket there like:
sudo ip netns exec "$netns" socat abstract-listen:test-ns,fork /dev/null &
ps -eopid= |
while read p; do
nsenter -n"/proc/$p/ns/net" socat -u abstract:test-ns - 2> /dev/null &&
echo "$p"
done
I used the first form (I usebash
), but I get an error when I runfind -L /proc/*/task/*/ns/net -samefile /run/netns/"$netns" find: '/proc/self/task/8964/ns/net': No such file or directory
(where8964
is current pid [$$
] ) - should I be running this in thedefault
namespace ?
– vyom
Jun 30 '15 at 12:08
@vyom, yes from the top level pid and mount namespace (though I suppose you could create netns'es in other mount namespaces which would void that command).
– Stéphane Chazelas
Jun 30 '15 at 12:25
doesn't seem to be working for me :(. I tried from/
, and I have created thenetns
, in the usual way -ip netns add
, and I can see it in/var/run/netns/
. Not sure what I am missing
– vyom
Jun 30 '15 at 12:33
@vyom, doesgrep /run/netns /proc/self/mountinfo
report anything? What kernel version are you using (uname -rs
)?
– Stéphane Chazelas
Jun 30 '15 at 12:40
2
ip netns help
lists the commandnetns pids NAME
which, as I think, is supposed to list all of the pids in a name netns.
– mikeserv
Jun 30 '15 at 22:03
|
show 9 more comments
The question specifically mentions Ubuntu 12.04, but I note that on newer distros like 16.04 there is a command that does exactly this: ip netns pids <nsname>
Unfortunately,ip netns
only works on network namespaces bind-mounted on/run/netns
(also/var/run/netns
). It is completely ignorant to any other network namespaces, either bind-mounted in other places, such as/run/docker
, and it especially is totally ignorant of/proc
.
– TheDiveO
Jun 12 '18 at 20:30
add a comment |
When running inside the container as opposed to outside, I found the -samefile trick sadly didn't work. Not sure why as it was the same inode. Anyway, this however did work, just in case it is of use to anyone:
netns=mynamespace
inode=$(ls -i /var/run/netns/$netns | cut -f1 -d" ")
pids=$(find -L /proc/[1-9]*/task/*/ns/net -inum $inode | cut -f3 -d"/" | uniq)
ps -p $pids
add a comment |
ps $(ip netns pids myns)
where myns
is your namespace
2
Pretty similar to unix.stackexchange.com/a/354038/117549
– Jeff Schaller
Aug 1 '18 at 13:06
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f213054%2flist-processes-belonging-to-a-network-namespace%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
You could do something like:
netns=myns
find -L /proc/[1-9]*/task/*/ns/net -samefile /run/netns/"$netns" | cut -d/ -f5
Or with zsh
:
print -l /proc/[1-9]*/task/*/ns/net(e:'[ $REPLY -ef /run/netns/$netns ]'::h:h:t)
It checks the inode of the file which the /proc/*/task/*/ns/net
symlink points to agains those of the files bind-mounted by ip netns add
in /run/netns
. That's basically what ip netns identify
or ip netns pid
in newer versions of iproute2
do.
That works with the 3.13 kernel as from the linux-image-generic-lts-trusty
package on Ubuntu 12.04, but not with the 3.2 kernel from the first release of 12.04 where /proc/*/ns/*
are not symlinks and each net
file there from every process and task gets a different inode which can't help determine namespace membership.
Support for that was added by that commit in 2011, which means you need kernel 3.8 or newer.
With older kernels, you could try and run a program listening on an ABSTRACT socket in the namespace, and then try to enter the namespace of every process to see if you can connect to that socket there like:
sudo ip netns exec "$netns" socat abstract-listen:test-ns,fork /dev/null &
ps -eopid= |
while read p; do
nsenter -n"/proc/$p/ns/net" socat -u abstract:test-ns - 2> /dev/null &&
echo "$p"
done
I used the first form (I usebash
), but I get an error when I runfind -L /proc/*/task/*/ns/net -samefile /run/netns/"$netns" find: '/proc/self/task/8964/ns/net': No such file or directory
(where8964
is current pid [$$
] ) - should I be running this in thedefault
namespace ?
– vyom
Jun 30 '15 at 12:08
@vyom, yes from the top level pid and mount namespace (though I suppose you could create netns'es in other mount namespaces which would void that command).
– Stéphane Chazelas
Jun 30 '15 at 12:25
doesn't seem to be working for me :(. I tried from/
, and I have created thenetns
, in the usual way -ip netns add
, and I can see it in/var/run/netns/
. Not sure what I am missing
– vyom
Jun 30 '15 at 12:33
@vyom, doesgrep /run/netns /proc/self/mountinfo
report anything? What kernel version are you using (uname -rs
)?
– Stéphane Chazelas
Jun 30 '15 at 12:40
2
ip netns help
lists the commandnetns pids NAME
which, as I think, is supposed to list all of the pids in a name netns.
– mikeserv
Jun 30 '15 at 22:03
|
show 9 more comments
You could do something like:
netns=myns
find -L /proc/[1-9]*/task/*/ns/net -samefile /run/netns/"$netns" | cut -d/ -f5
Or with zsh
:
print -l /proc/[1-9]*/task/*/ns/net(e:'[ $REPLY -ef /run/netns/$netns ]'::h:h:t)
It checks the inode of the file which the /proc/*/task/*/ns/net
symlink points to agains those of the files bind-mounted by ip netns add
in /run/netns
. That's basically what ip netns identify
or ip netns pid
in newer versions of iproute2
do.
That works with the 3.13 kernel as from the linux-image-generic-lts-trusty
package on Ubuntu 12.04, but not with the 3.2 kernel from the first release of 12.04 where /proc/*/ns/*
are not symlinks and each net
file there from every process and task gets a different inode which can't help determine namespace membership.
Support for that was added by that commit in 2011, which means you need kernel 3.8 or newer.
With older kernels, you could try and run a program listening on an ABSTRACT socket in the namespace, and then try to enter the namespace of every process to see if you can connect to that socket there like:
sudo ip netns exec "$netns" socat abstract-listen:test-ns,fork /dev/null &
ps -eopid= |
while read p; do
nsenter -n"/proc/$p/ns/net" socat -u abstract:test-ns - 2> /dev/null &&
echo "$p"
done
I used the first form (I usebash
), but I get an error when I runfind -L /proc/*/task/*/ns/net -samefile /run/netns/"$netns" find: '/proc/self/task/8964/ns/net': No such file or directory
(where8964
is current pid [$$
] ) - should I be running this in thedefault
namespace ?
– vyom
Jun 30 '15 at 12:08
@vyom, yes from the top level pid and mount namespace (though I suppose you could create netns'es in other mount namespaces which would void that command).
– Stéphane Chazelas
Jun 30 '15 at 12:25
doesn't seem to be working for me :(. I tried from/
, and I have created thenetns
, in the usual way -ip netns add
, and I can see it in/var/run/netns/
. Not sure what I am missing
– vyom
Jun 30 '15 at 12:33
@vyom, doesgrep /run/netns /proc/self/mountinfo
report anything? What kernel version are you using (uname -rs
)?
– Stéphane Chazelas
Jun 30 '15 at 12:40
2
ip netns help
lists the commandnetns pids NAME
which, as I think, is supposed to list all of the pids in a name netns.
– mikeserv
Jun 30 '15 at 22:03
|
show 9 more comments
You could do something like:
netns=myns
find -L /proc/[1-9]*/task/*/ns/net -samefile /run/netns/"$netns" | cut -d/ -f5
Or with zsh
:
print -l /proc/[1-9]*/task/*/ns/net(e:'[ $REPLY -ef /run/netns/$netns ]'::h:h:t)
It checks the inode of the file which the /proc/*/task/*/ns/net
symlink points to agains those of the files bind-mounted by ip netns add
in /run/netns
. That's basically what ip netns identify
or ip netns pid
in newer versions of iproute2
do.
That works with the 3.13 kernel as from the linux-image-generic-lts-trusty
package on Ubuntu 12.04, but not with the 3.2 kernel from the first release of 12.04 where /proc/*/ns/*
are not symlinks and each net
file there from every process and task gets a different inode which can't help determine namespace membership.
Support for that was added by that commit in 2011, which means you need kernel 3.8 or newer.
With older kernels, you could try and run a program listening on an ABSTRACT socket in the namespace, and then try to enter the namespace of every process to see if you can connect to that socket there like:
sudo ip netns exec "$netns" socat abstract-listen:test-ns,fork /dev/null &
ps -eopid= |
while read p; do
nsenter -n"/proc/$p/ns/net" socat -u abstract:test-ns - 2> /dev/null &&
echo "$p"
done
You could do something like:
netns=myns
find -L /proc/[1-9]*/task/*/ns/net -samefile /run/netns/"$netns" | cut -d/ -f5
Or with zsh
:
print -l /proc/[1-9]*/task/*/ns/net(e:'[ $REPLY -ef /run/netns/$netns ]'::h:h:t)
It checks the inode of the file which the /proc/*/task/*/ns/net
symlink points to agains those of the files bind-mounted by ip netns add
in /run/netns
. That's basically what ip netns identify
or ip netns pid
in newer versions of iproute2
do.
That works with the 3.13 kernel as from the linux-image-generic-lts-trusty
package on Ubuntu 12.04, but not with the 3.2 kernel from the first release of 12.04 where /proc/*/ns/*
are not symlinks and each net
file there from every process and task gets a different inode which can't help determine namespace membership.
Support for that was added by that commit in 2011, which means you need kernel 3.8 or newer.
With older kernels, you could try and run a program listening on an ABSTRACT socket in the namespace, and then try to enter the namespace of every process to see if you can connect to that socket there like:
sudo ip netns exec "$netns" socat abstract-listen:test-ns,fork /dev/null &
ps -eopid= |
while read p; do
nsenter -n"/proc/$p/ns/net" socat -u abstract:test-ns - 2> /dev/null &&
echo "$p"
done
edited Jul 1 '15 at 20:08
answered Jun 30 '15 at 11:31
Stéphane Chazelas
300k54564913
300k54564913
I used the first form (I usebash
), but I get an error when I runfind -L /proc/*/task/*/ns/net -samefile /run/netns/"$netns" find: '/proc/self/task/8964/ns/net': No such file or directory
(where8964
is current pid [$$
] ) - should I be running this in thedefault
namespace ?
– vyom
Jun 30 '15 at 12:08
@vyom, yes from the top level pid and mount namespace (though I suppose you could create netns'es in other mount namespaces which would void that command).
– Stéphane Chazelas
Jun 30 '15 at 12:25
doesn't seem to be working for me :(. I tried from/
, and I have created thenetns
, in the usual way -ip netns add
, and I can see it in/var/run/netns/
. Not sure what I am missing
– vyom
Jun 30 '15 at 12:33
@vyom, doesgrep /run/netns /proc/self/mountinfo
report anything? What kernel version are you using (uname -rs
)?
– Stéphane Chazelas
Jun 30 '15 at 12:40
2
ip netns help
lists the commandnetns pids NAME
which, as I think, is supposed to list all of the pids in a name netns.
– mikeserv
Jun 30 '15 at 22:03
|
show 9 more comments
I used the first form (I usebash
), but I get an error when I runfind -L /proc/*/task/*/ns/net -samefile /run/netns/"$netns" find: '/proc/self/task/8964/ns/net': No such file or directory
(where8964
is current pid [$$
] ) - should I be running this in thedefault
namespace ?
– vyom
Jun 30 '15 at 12:08
@vyom, yes from the top level pid and mount namespace (though I suppose you could create netns'es in other mount namespaces which would void that command).
– Stéphane Chazelas
Jun 30 '15 at 12:25
doesn't seem to be working for me :(. I tried from/
, and I have created thenetns
, in the usual way -ip netns add
, and I can see it in/var/run/netns/
. Not sure what I am missing
– vyom
Jun 30 '15 at 12:33
@vyom, doesgrep /run/netns /proc/self/mountinfo
report anything? What kernel version are you using (uname -rs
)?
– Stéphane Chazelas
Jun 30 '15 at 12:40
2
ip netns help
lists the commandnetns pids NAME
which, as I think, is supposed to list all of the pids in a name netns.
– mikeserv
Jun 30 '15 at 22:03
I used the first form (I use
bash
), but I get an error when I run find -L /proc/*/task/*/ns/net -samefile /run/netns/"$netns" find: '/proc/self/task/8964/ns/net': No such file or directory
(where 8964
is current pid [$$
] ) - should I be running this in the default
namespace ?– vyom
Jun 30 '15 at 12:08
I used the first form (I use
bash
), but I get an error when I run find -L /proc/*/task/*/ns/net -samefile /run/netns/"$netns" find: '/proc/self/task/8964/ns/net': No such file or directory
(where 8964
is current pid [$$
] ) - should I be running this in the default
namespace ?– vyom
Jun 30 '15 at 12:08
@vyom, yes from the top level pid and mount namespace (though I suppose you could create netns'es in other mount namespaces which would void that command).
– Stéphane Chazelas
Jun 30 '15 at 12:25
@vyom, yes from the top level pid and mount namespace (though I suppose you could create netns'es in other mount namespaces which would void that command).
– Stéphane Chazelas
Jun 30 '15 at 12:25
doesn't seem to be working for me :(. I tried from
/
, and I have created the netns
, in the usual way - ip netns add
, and I can see it in /var/run/netns/
. Not sure what I am missing– vyom
Jun 30 '15 at 12:33
doesn't seem to be working for me :(. I tried from
/
, and I have created the netns
, in the usual way - ip netns add
, and I can see it in /var/run/netns/
. Not sure what I am missing– vyom
Jun 30 '15 at 12:33
@vyom, does
grep /run/netns /proc/self/mountinfo
report anything? What kernel version are you using (uname -rs
)?– Stéphane Chazelas
Jun 30 '15 at 12:40
@vyom, does
grep /run/netns /proc/self/mountinfo
report anything? What kernel version are you using (uname -rs
)?– Stéphane Chazelas
Jun 30 '15 at 12:40
2
2
ip netns help
lists the command netns pids NAME
which, as I think, is supposed to list all of the pids in a name netns.– mikeserv
Jun 30 '15 at 22:03
ip netns help
lists the command netns pids NAME
which, as I think, is supposed to list all of the pids in a name netns.– mikeserv
Jun 30 '15 at 22:03
|
show 9 more comments
The question specifically mentions Ubuntu 12.04, but I note that on newer distros like 16.04 there is a command that does exactly this: ip netns pids <nsname>
Unfortunately,ip netns
only works on network namespaces bind-mounted on/run/netns
(also/var/run/netns
). It is completely ignorant to any other network namespaces, either bind-mounted in other places, such as/run/docker
, and it especially is totally ignorant of/proc
.
– TheDiveO
Jun 12 '18 at 20:30
add a comment |
The question specifically mentions Ubuntu 12.04, but I note that on newer distros like 16.04 there is a command that does exactly this: ip netns pids <nsname>
Unfortunately,ip netns
only works on network namespaces bind-mounted on/run/netns
(also/var/run/netns
). It is completely ignorant to any other network namespaces, either bind-mounted in other places, such as/run/docker
, and it especially is totally ignorant of/proc
.
– TheDiveO
Jun 12 '18 at 20:30
add a comment |
The question specifically mentions Ubuntu 12.04, but I note that on newer distros like 16.04 there is a command that does exactly this: ip netns pids <nsname>
The question specifically mentions Ubuntu 12.04, but I note that on newer distros like 16.04 there is a command that does exactly this: ip netns pids <nsname>
answered Mar 27 '17 at 3:50
squashed
312
312
Unfortunately,ip netns
only works on network namespaces bind-mounted on/run/netns
(also/var/run/netns
). It is completely ignorant to any other network namespaces, either bind-mounted in other places, such as/run/docker
, and it especially is totally ignorant of/proc
.
– TheDiveO
Jun 12 '18 at 20:30
add a comment |
Unfortunately,ip netns
only works on network namespaces bind-mounted on/run/netns
(also/var/run/netns
). It is completely ignorant to any other network namespaces, either bind-mounted in other places, such as/run/docker
, and it especially is totally ignorant of/proc
.
– TheDiveO
Jun 12 '18 at 20:30
Unfortunately,
ip netns
only works on network namespaces bind-mounted on /run/netns
(also /var/run/netns
). It is completely ignorant to any other network namespaces, either bind-mounted in other places, such as /run/docker
, and it especially is totally ignorant of /proc
.– TheDiveO
Jun 12 '18 at 20:30
Unfortunately,
ip netns
only works on network namespaces bind-mounted on /run/netns
(also /var/run/netns
). It is completely ignorant to any other network namespaces, either bind-mounted in other places, such as /run/docker
, and it especially is totally ignorant of /proc
.– TheDiveO
Jun 12 '18 at 20:30
add a comment |
When running inside the container as opposed to outside, I found the -samefile trick sadly didn't work. Not sure why as it was the same inode. Anyway, this however did work, just in case it is of use to anyone:
netns=mynamespace
inode=$(ls -i /var/run/netns/$netns | cut -f1 -d" ")
pids=$(find -L /proc/[1-9]*/task/*/ns/net -inum $inode | cut -f3 -d"/" | uniq)
ps -p $pids
add a comment |
When running inside the container as opposed to outside, I found the -samefile trick sadly didn't work. Not sure why as it was the same inode. Anyway, this however did work, just in case it is of use to anyone:
netns=mynamespace
inode=$(ls -i /var/run/netns/$netns | cut -f1 -d" ")
pids=$(find -L /proc/[1-9]*/task/*/ns/net -inum $inode | cut -f3 -d"/" | uniq)
ps -p $pids
add a comment |
When running inside the container as opposed to outside, I found the -samefile trick sadly didn't work. Not sure why as it was the same inode. Anyway, this however did work, just in case it is of use to anyone:
netns=mynamespace
inode=$(ls -i /var/run/netns/$netns | cut -f1 -d" ")
pids=$(find -L /proc/[1-9]*/task/*/ns/net -inum $inode | cut -f3 -d"/" | uniq)
ps -p $pids
When running inside the container as opposed to outside, I found the -samefile trick sadly didn't work. Not sure why as it was the same inode. Anyway, this however did work, just in case it is of use to anyone:
netns=mynamespace
inode=$(ls -i /var/run/netns/$netns | cut -f1 -d" ")
pids=$(find -L /proc/[1-9]*/task/*/ns/net -inum $inode | cut -f3 -d"/" | uniq)
ps -p $pids
answered Feb 15 '17 at 20:49
Neil McGill
29328
29328
add a comment |
add a comment |
ps $(ip netns pids myns)
where myns
is your namespace
2
Pretty similar to unix.stackexchange.com/a/354038/117549
– Jeff Schaller
Aug 1 '18 at 13:06
add a comment |
ps $(ip netns pids myns)
where myns
is your namespace
2
Pretty similar to unix.stackexchange.com/a/354038/117549
– Jeff Schaller
Aug 1 '18 at 13:06
add a comment |
ps $(ip netns pids myns)
where myns
is your namespace
ps $(ip netns pids myns)
where myns
is your namespace
edited Aug 1 '18 at 13:38
Kevin Lemaire
1,162524
1,162524
answered Aug 1 '18 at 12:41
L S
11
11
2
Pretty similar to unix.stackexchange.com/a/354038/117549
– Jeff Schaller
Aug 1 '18 at 13:06
add a comment |
2
Pretty similar to unix.stackexchange.com/a/354038/117549
– Jeff Schaller
Aug 1 '18 at 13:06
2
2
Pretty similar to unix.stackexchange.com/a/354038/117549
– Jeff Schaller
Aug 1 '18 at 13:06
Pretty similar to unix.stackexchange.com/a/354038/117549
– Jeff Schaller
Aug 1 '18 at 13:06
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f213054%2flist-processes-belonging-to-a-network-namespace%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown