On Thu, Apr 30, 2015 at 07:08:13PM +0200, Daniel Baumann wrote: > On 04/30/15 08:50, Guido Günther wrote: > > * lxc is lacking error reporting > > if you start it via initscript and have no error-logging, then indeed > you don't see any error. > > > * doesn't wait for libvirt to come up - it's debatable wether this would > > be a good thing > > no; both the initscript and the systemd unit have network as a depends - > there's nothing more we can do on the lxc (or any other service that > requires network to be up) side. > > > I would totally agree that libvirt has a bug if the lxc container would > > be libvirt managed (via lxc://) but this isn't the case. > > right; but the user is abusing libvirt here to setup his bridge, rather > than to configure it normally. it's up to you though if you want to > 'allow' users to use libvirt like that or not.
We we won't lose anything if we add a "Should-Start: libvirtd", do we? Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
