Yes, I agree your fix is nice - and needed. Please do upload it (as I'm
out most of this week).
Thanks!
Note that Jon will do a new libcgroup release in debian this week. I'll
merge and test it next week.
--
You received this bug notification because you are a member of Ubuntu
Server Team, wh
On Mon, Mar 05, 2012, Serge Hallyn wrote:
> This is should be independent of the libvirt-cgconfig-wait job. That
> doesn't actually explicitly start libvirt-bin. Are you on precise?
Yes, I'm on precise
> Note that really libcgroup and libvirt do not work together anyway, due
> to a race at sta
Hi Loic,
> Since some time, libvirt-bin fails upgrading at the time "start
libvirt-bin" is run during upgrades; I have start_libvirtd="no" in
/etc/default/libvirt-bin.
This is should be independent of the libvirt-cgconfig-wait job. That
doesn't actually explicitly start libvirt-bin. Are you on
Actually last comment was wrong, testing confirms that sleep *gets*
killed when the stop condition is met.
I still don't know what happens with my libvirt-bin startup issue, but
at least the cgred-wait changes seem correct since the other -wait is
also using a different syntax.
--
You received t
/etc/init/libvirt-cgconfig-wait.conf will immediately exit if cgconfig
is already considered "running"; however if that's not the case, it will
go into a "sleep" case which wont be interrupted even when cgconfig
actually starts: AIUI, the stop statement only prevents startup, but
wont kill a runnin
Aha, during my last upgrade libvirt-bin started after two minutes, which
seems to be exactly the TIMEOUT set in /etc/init/libvirt-cgconfig-
wait.conf.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libcgroup in Ubuntu.
https://bugs.lau
