Isaku Yamahata 4d72093de5 netns: ip netns exec <name> kill doesn't make sense ...

It seems confusing netns with pidns.
Although 'ip netns exec' doesn't make sense,
'ip netns exec <netns> kill <pid>' itself success as expected.
But as side effects, dentry of /proc/<pid>/ns/net becomes young,
which increases the possibility to fail to delete netns. That's not good.

Fixes: Bug #1158589
Change-Id: I9aa717ccb86d8bf00bb1e707d39bfb65d043532b
Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>

2013-03-25 15:00:48 +09:00

..

__init__.py

Replace "OpenStack LLC" with "OpenStack Foundation"

2013-03-13 15:06:24 -04:00

daemon.py

Fix i18n messages

2013-01-22 11:42:15 +08:00

dhcp.py

netns: ip netns exec <name> kill doesn't make sense

2013-03-25 15:00:48 +09:00

external_process.py

netns: ip netns exec <name> kill doesn't make sense

2013-03-25 15:00:48 +09:00

interface.py

Replace "OpenStack LLC" with "OpenStack Foundation"

2013-03-13 15:06:24 -04:00

ip_lib.py

Replace "OpenStack LLC" with "OpenStack Foundation"

2013-03-13 15:06:24 -04:00

iptables_firewall.py

Ensure max length of iptables chain name w/o prefix is up to 11 chars.

2013-03-01 23:50:55 +09:00

iptables_manager.py

Ensure that lockfile are defined in a common place

2013-03-21 05:42:06 +00:00

ovs_lib.py

Fix i18n messages

2013-01-22 11:42:15 +08:00

utils.py

LBaaS Agent Reference Implementation

2013-02-27 21:49:57 -05:00