Thread (28 messages) flat view 28 messages, 6 authors, 2012-01-23

RE: RFC Hanging clean-up of a namespace

From: Hans Schillström <hidden>
Date: 2012-01-19 19:40:35

Date: Thu, 19 Jan 2012 12:07:09 +0100
quoted
Closing of a namespace (container) can be delayed by ~ 2 minutes
due to tcp timers ex tcp time wait (and of cource other things too).

I think there should be some kind of "forced close" of the Network stack
in ex free_nsproxy()
I think this is unwise.

Keeping the timewait sockets around is necessary to absorb any lingering
packets in the network meant for those sockets.

If you truncate this activity, and then try to create another socket with
the same ID you'll run into the very problems time-wait is meant to
solve.

It's an unfortunate delay, but one you will have to live with.
I think the whole clean up is to weak of the name space, there is too many things that
can go wrong and they do.

I was more thinking of a way to make a forced close, 
ex by cleaning the stack where time wait was one point.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help