[lxc-devel] [PATCH] Various fixes for Fedora/CentOS/OpenSUSE templates and systemd.

[Michael H. Warfield]

On Wed, 2014-10-01 at 11:34 -0400, Stéphane Graber wrote:

[snip]

> > Would this be better if this paralleled autodev an we only disabled kmsg
> > by default if and when systemd was detected as the init system?  The
> > situation is very analogous to the autodev situation.  If a user were to
> > switch from say upstart to systemd and autodev is not specified in the
> > config, we default that to enabled when we detect systemd as the init
> > system at run time.  We could also default kmsg to 0 in the case of
> > systemd being the run time init system manager to prevent journald from
> > going into it's console message loop and burning CPU.  Would that work
> > better for you?  Since you can switch init systems from within the
> > container and may not have access to the container config file that's in
> > the host, something should be done to cover the run time case, like we
> > do with autodev.  That's what I was attempting to do...

> I'm not very much fond of having to do per-init system config changes
> but yeah, that sounds like a reasonable way to go.

> If we start getting more and more of those cases we may want to make
> things slightly more configurable by just having LXC include some
> default configuration files based on that detection.

Oh?  Sort of like conditional includes?  If lxc.init = systemd include
systemd.conf sort of thing?  It would have to be runtime conditional but
that does make some sense at that.

> > This bug is now closed, after I explained to the originator what the
> > problem was, but it points out the problem we're seeing from having kmsg
> > being a symlink to console and having journald run crazy in the
> > container...
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=1141456
> > 
> > -- 
> > 
> > > (1) Starting a basic LXC container, which is not configured to do anything at all, *immediately* (and without delay) raises the temperature *substantially* of one of the cores.
> > > 
> > > (2) Starting a second LXC container (also not configured to do anything), does the same as (1), but on a different core (i.e. the one that that LXC uses).
> > -- 
> > 

[Big snip - this time I remembered...]

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (770) 978-7061 |  mhw at WittsEnd.com
   /\/\|=mhw=|\/\/          | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9          | An optimist believes we live in the best of all
 PGP Key: 0x674627FF        | possible worlds.  A pessimist is sure of it!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 465 bytes
Desc: This is a digitally signed message part
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20141001/f4f36d97/attachment.sig>