Killing all processes that are run under "ip netns exec" is not acceptable. Imagine I've got many namespaces and I want to delete a small percentage of them. It is very disruptive to kill all dnsmasq and metadata processes regardless of the namespace in which they're running.
I applied this patch to my Ubuntu Precise version of iproute. It applied cleanly. I rebooted once to clear out processes that were started under the old version of "ip netns exec." Since then, I have been able to delete any namespace once the processes running under *that* namespace have been cleared out. I no longer need to stop *all* processes running under "ip netns exec" regardless of namespace.
This was the answer for me on Ubuntu Precise where I happen to be seeing the problem. I imagine if your version of iproute does not include the above patch then you will have a similar experience.
Killing all processes that are run under "ip netns exec" is not acceptable. Imagine I've got many namespaces and I want to delete a small percentage of them. It is very disruptive to kill all dnsmasq and metadata processes regardless of the namespace in which they're running.
I found a problem with the iproute utility described here: http:// permalink. gmane.org/ gmane.linux. network/ 240875
The solution was committed here: https:/ /git.kernel. org/cgit/ linux/kernel/ git/shemminger/ iproute2. git/commit/ ?id=58a3e8270fe 72f8ed92687d3a3 132c2a708582dd
I applied this patch to my Ubuntu Precise version of iproute. It applied cleanly. I rebooted once to clear out processes that were started under the old version of "ip netns exec." Since then, I have been able to delete any namespace once the processes running under *that* namespace have been cleared out. I no longer need to stop *all* processes running under "ip netns exec" regardless of namespace.
This was the answer for me on Ubuntu Precise where I happen to be seeing the problem. I imagine if your version of iproute does not include the above patch then you will have a similar experience.