Quoting Tamas Papp (tom...@martos.bme.hu):
> On 05/23/2013 09:47 PM, Serge Hallyn wrote:
> >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).
On 05/23/2013 09:47 PM, Serge Hallyn wrote:
> 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 whi
Quoting Tamas Papp (tom...@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 eve
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 sem
Quoting Tamas Papp (tom...@martos.bme.hu):
> On 05/23/2013 07:34 PM, Serge Hallyn wrote:
> > Quoting Tamas Papp (tom...@martos.bme.hu):
> >> On 05/23/2013 03:39 PM, Tamas Papp wrote:
> >>> On 05/23/2013 03:35 PM, Stéphane Graber wrote:
> That looks like broken locking, though Serge would know
On 05/23/2013 07:34 PM, Serge Hallyn wrote:
> Quoting Tamas Papp (tom...@martos.bme.hu):
>> On 05/23/2013 03:39 PM, Tamas Papp wrote:
>>> On 05/23/2013 03:35 PM, Stéphane Graber wrote:
That looks like broken locking, though Serge would know for sure.
You may want to try clearing /dev/shm/
Quoting Tamas Papp (tom...@martos.bme.hu):
> On 05/23/2013 03:39 PM, Tamas Papp wrote:
> > On 05/23/2013 03:35 PM, Stéphane Graber wrote:
> >> That looks like broken locking, though Serge would know for sure.
> >> You may want to try clearing /dev/shm/*lxc* and see if that fixes the
> >> problem (n
On 05/23/2013 03:39 PM, Tamas Papp wrote:
> On 05/23/2013 03:35 PM, Stéphane Graber wrote:
>> That looks like broken locking, though Serge would know for sure.
>> You may want to try clearing /dev/shm/*lxc* and see if that fixes the
>> problem (not usually recommended as those locks are there for a
On 05/23/2013 03:35 PM, Stéphane Graber wrote:
> That looks like broken locking, though Serge would know for sure.
> You may want to try clearing /dev/shm/*lxc* and see if that fixes the
> problem (not usually recommended as those locks are there for a reason).
OK.
At this moment I'm trying to re
On 05/23/2013 01:46 AM, Tamas Papp wrote:
> On 05/23/2013 04:27 AM, Stéphane Graber wrote:
>> Oops, looks like I broke lxc-ls --fancy with my recent get_ips() API
>> change. I'll fix it directly to staging (trivial fix) and trigger a new
>> daily build, you should be able to update to a fixed packa
On 05/23/2013 04:27 AM, Stéphane Graber wrote:
> Oops, looks like I broke lxc-ls --fancy with my recent get_ips() API
> change. I'll fix it directly to staging (trivial fix) and trigger a new
> daily build, you should be able to update to a fixed package in the next
> couple of hours.
>
hi,
Altho
On 05/22/2013 07:46 PM, Tamas Papp wrote:
> On 05/23/2013 01:36 AM, Tamas Papp wrote:
>> On 05/23/2013 01:02 AM, Tamas Papp wrote:
>>> hi All,
>>>
>>> # lxc-ls --fancy
>>> Traceback (most recent call last):
>>> File "/usr/bin/lxc-ls", line 221, in
>>>ips = container.get_ips(protocol=p
On 05/23/2013 01:36 AM, Tamas Papp wrote:
> On 05/23/2013 01:02 AM, Tamas Papp wrote:
>> hi All,
>>
>> # lxc-ls --fancy
>> Traceback (most recent call last):
>> File "/usr/bin/lxc-ls", line 221, in
>>ips = container.get_ips(protocol=protocol, timeout=1)
>> TypeError: 'protocol' is an
On 05/23/2013 01:02 AM, Tamas Papp wrote:
> hi All,
>
> # lxc-ls --fancy
> Traceback (most recent call last):
> File "/usr/bin/lxc-ls", line 221, in
> ips = container.get_ips(protocol=protocol, timeout=1)
> TypeError: 'protocol' is an invalid keyword argument for this function
>
>
> # lx
hi All,
# lxc-ls --fancy
Traceback (most recent call last):
File "/usr/bin/lxc-ls", line 221, in
ips = container.get_ips(protocol=protocol, timeout=1)
TypeError: 'protocol' is an invalid keyword argument for this function
# lxc-info -n sc --state-is=running
# echo $?
1
The container is
I'm trying to use lxc in arch linux. lxc version is 0.8. Running
lxc-execute with the conf file lxc-macvlan.conf is not working. whereas if
I exclude the network part from the conf, e.g using lxc-no-netns.conf is
working fine. Errors are as follows,
#lxc-create -n test -f /usr/share/doc/lxc/exampl
16 matches
Mail list logo
