Hi,
> [ Christian: this should be a good starting point for adding the
> lxc.signal.{halt,reboot,kill}, etc. If you don't have time, I'll
> get back to looking at that later. Thanks! ]
Will do that in the next few days.
> Also if the container is not running, return -2. Currently
> lxc-stop will return 0, so you cannot tell the difference
> between successfull stopping and noop.
That should be documented in the manpage. Btw. -2 is 254 if you want to
check against it in the shell, since only 8 bits are kept of the return
code.
Also, from looking at lxcapi_shutdown, the -s option currently doesn't
really work, because if timeout > 0, it will always kill the container.
But this is something I can fix in an additional patch on top of that.
-- Christian
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Lxc-devel mailing list
Lxc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-devel
