I don't know of a generic way this could be done in lxc. However, for your
specific containers, you could redirect console to a file and have a script
watch for a login prompt there?
-serge
Quoting Jäkel, Guido (g.jae...@dnb.de):
> Hi,
>
> i would like to have an discussion about an additional
Hi Daniel,
I've refreshed github.com/hallyn/lxc from your upstream tree, gone back
through our current ubuntu lxc package, and pushed all the patches from
debian and ubuntu which seemed appropriate. The result builds and
passes my containers tests (at lp:~serge-hallyn/+junk/lxc-test). Most
of th
On Jun 28, 2012, at 5:38 PM, Jonathan Carter (highvoltage) wrote:
> So what's been happening is that Stéphane is writing nice Python bindings for
> LXC in C. Currently my hacky script is calling the rest of the current LXC
> scripts. My goal is to redo rlxc as a nice Python script that uses that
Hi David,
On Jun 28, 2012, at 5:35 PM, Ward, David - 0663 - MITLL wrote:
> Just FYI, current git now allows you to list running containers
> only with the '--active' flag to lxc-ls.
when I type in lxc-ls manually, I guess I will want to add --active for
90 percent of the time.
I already saw the
Hi Stefan!
On 28/06/2012 10:49, Stefan Schlesinger wrote:
> I'm new to LXC and have been using OpenVZ until now.
>
> Something which I immediately missed, when I played around with the LXC
> CLI tools the first time, was that neither lxc-ls nor lxc-list provide
> a nice overview of the current sta
On 28/06/12 10:49, Stefan Schlesinger wrote:
Hello,
I'm new to LXC and have been using OpenVZ until now.
Something which I immediately missed, when I played around with the LXC
CLI tools the first time, was that neither lxc-ls nor lxc-list provide
a nice overview of the current status of your h
Hello,
I'm new to LXC and have been using OpenVZ until now.
Something which I immediately missed, when I played around with the LXC
CLI tools the first time, was that neither lxc-ls nor lxc-list provide
a nice overview of the current status of your host.
To give you an example here is how the vz
Hi,
i would like to have an discussion about an additional state for a container,
let say BOOTED . It should logical succeed the current RUNNING state.
Alternatively, there may be created an additional instrument to get information
about the following:
The change in state should reflect that t
>As the next step, I need to separately identify all the processes, being
>initiated by programs running inside the container. This
>will help me to track all the activities carried out by sandboxed application.
>
Either use the lxc-away version of the ps command named lxc-ps --name
$CONTAIN
Dear Sir,
Thank you very much for your prompt reply. I understand that a process
actually doesn't "run" inside container. I also was able to view system
calls executed by a process (using strace) initiated by a program running
inside the container. This was done by staying outside the LXC-Containe
Dear Sharma,
Because container virtualization may be roughly described as a "complex chroot
tool", a process actually don't "run" inside container. It's acting in the same
context of one-and-only kernel which have bootstrapped the host. It is just
inside a access control group, which phenotype
11 matches
Mail list logo
