[lxc-devel] [PATCH] Add a non-null group for autobooting

Michael H. Warfield mhw at WittsEnd.com
Fri May 2 21:55:41 UTC 2014


On Fri, 2014-05-02 at 23:50 +0200, Christian Seiler wrote:
> Hi,

> > We use upstart instances for the containers so they show up in "initctl
> > list" as separate jobs which can be stopped or restarted.

> Btw. we could do something similar for the systemd case if we implement
> the autostart functionality with a generator (in that case, the generate
> could also detect whether we have to wait for the bridge or not for each
> container individually, so that containers with for example empty
> networking can be started faster) and use transient units for manually
> started backgrounded containers.

I've stated before that I really want to avoid the generator case as it
just simply does not have the level of granularity that we can provide.
Right now, calling lxc-autostart with the appropriate parameters does
the right thing.

> I'll see if I can hack something together over the weekend.

Give it your best shot taking into account order, groups, and delays.
I'll look it over.  It has to be congruent with the other init systems.

> Regards,
> Christian

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: 482 bytes
Desc: This is a digitally signed message part
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20140502/69959bda/attachment.sig>


More information about the lxc-devel mailing list