Right now, there is one lxc-start process per container running (that has renamed itself in lxc 1.1.4 to [lxc-monitor]) to act as the interface to the container for various LXC tools.
I'd like that process to exit once the container is up and running. I do not want to ever stop the container, connect to its console, freeze it or run any other LXC tools. I just want the container to be started and left to run within the environment that lxc-start set up for it. So, is it possible to get it to exit cleanly but leave the containers to run unsupervised, and if so, how? I did just try "kill -9" on the [lxc-monitor] process to see if the container could survive the loss, but whilst (busybox's) init is still running, the shells attached to tty devices inside the containers did not survive. -- Stewart Brodie Senior Software Engineer Espial UK _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
