Hi there, I found two little bugs in lxc-start and lxc-shutdown and provided some trivial patches that should go in after rc1.
lxc-start: If pinning the rootfs doesn't work (for example, if the rootfs doesn't exist and readlink() that is used to get the parent directory fails) it will not remove the network interfaces, causing subsequent starts to also fail. lxc-shutdown: Probably due to set -e, lxc-shutdown with -t didn't work properly anymore, the attached patch fixes that. (By the way, is there any reason why lxc-shutdown doesn't use lxc-wait and does this strange own timeout logic with a 1s polling loop? In case there is no real reason, I propose changing it after 0.9 final and use my bugfix for now, just to be sure not to introduce some strange regressions.) -- Christian ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
