[lxc-devel] [PATCH 0/5] Signal stuff v2 and some documentation

[atp]

Hi,

Apologies if this is the wrong list.

> > Interestingly, it stays in S state until
> > I kill the container.  I'm afraid the console functionality (is there
> > any documentation for it?) may make lxc-start unsuitable for pushing
> > into the background. After all, it is an interactive foreground process
> > in that case, a real proxy towards some getty (if I understand this
> > console thingie right).  Maybe this should be handled differently to
> > application containers.  But then I'm not sure how Ctrl-C and similar
> > should be forwarded to a getty...
> 
> argh. yes, chicken-egg problem.

  The lxc.console=$(tty) thing was something I was thinking about. 

There are a couple of things I've noticed and was pondering how to fix;

1) The expectation I have from xen, kvm etc is that you can detach from
the console like lxc-console allows. i.e. 
lxc-start -C -n test 
behaves like
lxc-start -n test ; lxc-console

 - at the moment you have an interactive foreground process. 

2) If you have a getty on the console, when you start without -s
lxc.console=$(tty) it puts the system messages and the getty on the host
system console. That gets confusing when logging in on a lights out 
console. 
 
Was this what lxcd was for? 

Should it be that lxc-start always goes into the background, and holds
onto the console, which you can connect to via lxcd by specifying a flag
to lxc-console? lxc-start -s lxc.console gets replaced by lxc-start -C
which is equivalent to lxc-start ; lxc-console 

Happy to devote some time to fixing this... 

Andy
 

Andrew Phillips
Head of Systems

www.lmax.com 

Office: +44 203 1922509
Mobile: +44 (0)7595 242 900

LMAX | Level 2, Yellow Building | 1 Nicholas Road | London | W11 4AN




The information in this e-mail and any attachment is confidential and is intended only for the named recipient(s). The e-mail may not be disclosed or used by any person other than the addressee, nor may it be copied in any way. If you are not a named recipient please notify the sender immediately and delete any copies of this message. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any view or opinions presented are solely those of the author and do not necessarily represent those of the company.