Trent W. Buck writes:
This post describes my attempts to get clean shutdown of Ubuntu 10.04
containers. The goal here is that a shutdown -h now of the dom0
should not result in a potentially inconsistent domU postgres database,
cf. a naive lxc-stop.
As this is largely working for me, I have
Hi Gordon,
On 12/03/2010 05:59 PM, Gordon Henderson wrote:
On Fri, 3 Dec 2010, Matt Rechenburg wrote:
Hi Lxc team,
actually I would vote against a loop mount.
I would vote to allow the local systems administrator the choice of what
suits them best.
fully agree with you on
Cuma 12 Kasım 2010 günü (saat 12:05:29) Daniel Lezcano şunları yazmıştı:
On 11/09/2010 09:33 PM, Brian K. White wrote:
If I understood correctly, you are using the git head which is 0.7.3 + 1
patch, right ?
After your container is started, what gives the ouput of lxc-ps --lxc ?
We're
Quoting Trent W. Buck (t...@cybersource.com.au):
Unfortunately, lxc 0.7's utmp detect requires /var/run to NOT be a
tmpfs. The shipped lxc-ubuntu script works around this by deleting the
ifstate file and not mounting a tmpfs on /var/run, but to me that is
simply waiting for something else to
On 12/6/2010 2:42 AM, Trent W. Buck wrote:
This post describes my attempts to get clean shutdown of Ubuntu 10.04
containers. The goal here is that a shutdown -h now of the dom0
should not result in a potentially inconsistent domU postgres database,
cf. a naive lxc-stop.
As at Ubuntu 10.04 with
On 12/6/2010 3:01 AM, Trent W. Buck wrote:
Trent W. Buck writes:
This post describes my attempts to get clean shutdown of Ubuntu 10.04
containers. The goal here is that a shutdown -h now of the dom0
should not result in a potentially inconsistent domU postgres database,
cf. a naive
On Mon, 2010-12-06 at 12:38 -0500, Brian K. White wrote:
On 12/6/2010 2:42 AM, Trent W. Buck wrote:
This post describes my attempts to get clean shutdown of Ubuntu 10.04
containers. The goal here is that a shutdown -h now of the dom0
should not result in a potentially inconsistent domU
On 12/6/2010 3:34 PM, Michael H. Warfield wrote:
On Mon, 2010-12-06 at 12:38 -0500, Brian K. White wrote:
On 12/6/2010 2:42 AM, Trent W. Buck wrote:
This post describes my attempts to get clean shutdown of Ubuntu 10.04
containers. The goal here is that a shutdown -h now of the dom0
should
Serge E. Hallyn serge.hal...@canonical.com
writes:
Quoting Trent W. Buck (t...@cybersource.com.au):
Unfortunately, lxc 0.7's utmp detect requires /var/run to NOT be a
tmpfs. The shipped lxc-ubuntu script works around this by deleting the
ifstate file and not mounting a tmpfs on /var/run, but
Brian K. White br...@aljex.com writes:
On 12/6/2010 2:42 AM, Trent W. Buck wrote:
I use the latter in my customized /etc/init.d/lxc stop rule.
Note that the lxc-wait's SHOULD be parallelized, but this is not
possible as at lxc 0.7.2 :-(
Sure it is.
Sorry, I meant lxc-wait(8) cannot be
Michael H. Warfield m...@wittsend.com
writes:
Yeah, that's something where I wish we had an onboot and/or disabled
config file like OpenVZ does. So you can have some configured but that
don't autoboot when you boot the system. As that stands, you would have
to rename or remove the config
Michael H. Warfield m...@wittsend.com
writes:
Ubuntu 10.04 simply REQUIRES /var/run to be a tmpfs; this is hard-coded
into mountall's (upstart's) /lib/init/fstab.
Are you absolutely SURE about this? I was under the impression this was
under control of the /etc/default/rcS file and the
Brian K. White br...@aljex.com writes:
On 12/6/2010 3:01 AM, Trent W. Buck wrote:
Trent W. Buck writes:
This post describes my attempts to get clean shutdown of Ubuntu 10.04
containers. The goal here is that a shutdown -h now of the dom0
should not result in a potentially inconsistent domU
I rewrote my init script, too, and now I'm pretty happy. Example
interactions below. In the second case, I've dialled the timeout down
to 2s to simulate hung containers.
r...@omega:~# /etc/init.d/lxc restart
Stopping LXC containers: krb-client failed!
Killing LXC containers: kdc
14 matches
Mail list logo
