[Lxc-users] errors

[Serge Hallyn]

Quoting Tamas Papp (tompos at martos.bme.hu):
> On 05/23/2013 07:55 PM, Serge Hallyn wrote:
> >>FYI, now it works fine now with 0.9.0.0~staging~20130523-0240-0ubuntu1~ppa1~precise1 .
> >>For this I had to stop all containers then start them again.
> >Ok - I suspect what was happening was that every lxc-ls was
> >segfaulting while holding the semaphore, then the next lxc-*
> >action using the api would hang.
> >
> >>Thanks for you help guys,
> >>tamas
> >>
> >>ps.: Can I expect similar "bugs" from these changes, like this was?
> >Not sure what you mean.
> 
> Are the planned (lock file) changes going to be "risky", so it may
> happen, that, say, it starts to segfaulting again?

The lxc lock had nothing to do with the segfaulting - and no, the new
hanges will simply swap out use of named semaphore for a flock on an
open fd (so that they get auto-cleaned if process is killed).  Any
potential for segvs *should* be found while I test.

> I'm just interested, wheter it's safe to upgrade to the latest
> version in the next few days. Unfortunately there is only daily ppa
> for 0.9 tree.

raring and saucy are based on 0.9.

For the most part the daily ppa is actually very stable.  It goes
through quite a bit of automated testing before it gets published.
It's what I use on my main dev box, though when I"m working on something
that takes a few days, I sometimes end up a few days behind while I
test my feature.

I think this is the second time a bug has been exposed mainly through
lxc-list (because it uses quite a bit of the api), so lxc-list should
be added explicitly to the testsuite.

-serge