On 26/06/2011 16:46, Mihamina Rakotomandimby wrote: > Hi all, > > I usually launch my containers with 'sudo lxc-start -n<name>'. > The problem with this is the fact it doesn't get my back to a shell > prompt. > To have what I want, I have to workarround, with screen or end the > command line with '&'. > > More globally, if the containers configuration files are all stored > in /etc/lxc/, with the basename same as the container name, How to > make /etc/lxc/ scanned for '*.conf' file and then all VMs started? > > If it's necessary, I'm running Debian Squeeze. > may be you can try -d option :
'sudo lxc-start -d -n<name>' ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
