Hi, I want to contribute an observation while playing around with my "empty plain vanilla" container template: The test cyclce is to start it, open an ssh terminal session to it, leave it idle and regular shut down the container.
Now, if the containers eth0 is brought down by the shutdown, after end of the lxc process the corresponding veth is still there and the idle ssh terminal client don't notices anything. This seems to hold for long times (, maybe endless if there is no traffic?). I'm not able to rename the veth at this point; it's said to be busy. But if I do a keystroke in the terminal, after some short timeout the client quits with a broken connection message. Also, a short time the veth disappear. By the other hand if I prevent inside the container by configuration that eth0 is driven down, then right at the termination of the lxc process the ssh terminal quits and also, the veth disappears. Beside from the test, I noticed the similar effect on other "in-real-usage"-containers with connection to listeners inside: The veth stays a while until theses inbounding connection have died. Guido ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
