On Fri, Jul 20, 2012 at 11:53 AM, Stuart Yoder <b08...@gmail.com> wrote: > After I start a container with lxc-start (no -d), ctrl-C doesn''t > working for me in the container's console. > > In the documentation at http://lxc.teegra.net/ it says: > > The terminal you start a container in will often lose control-C > (you can restore that)... > > How do you restore control-C functionality to the terminal? > > When I connect to the console using lxc-console then control-C does > work...however, > perhaps a separate issue is that <Ctrl+a q> is not workint to exit the > console. Any > ideas on that?
Figured out this second issue...the screen command (which I forgot was running) was grabbing the Ctrl+a. The first issue is still there-- Ctrl+c is not working after an lxc-start in non daemon mode. Stuart ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
