On 09/15/2010 02:10 PM, Papp Tamás wrote:
>
>On 2010.09.15. 9:18, Daniel Lezcano wrote:
>> On 08/31/2010 12:07 PM, Papp Tamás wrote:
>>
>> [ ... ]
>>
>>> Sure I can do this. What should I write in the report exactly and
>>> what is the correct email address I write to?
>>>
>>> - kernel version
On 2010.09.15. 9:18, Daniel Lezcano wrote:
> On 08/31/2010 12:07 PM, Papp Tamás wrote:
>
> [ ... ]
>
>> Sure I can do this. What should I write in the report exactly and
>> what is the correct email address I write to?
>>
>> - kernel version (2.6.32.x)
>> - system (Ubuntu)
>> - container was un
On 08/31/2010 12:07 PM, Papp Tamás wrote:
[ ... ]
> Sure I can do this. What should I write in the report exactly and what
> is the correct email address I write to?
>
> - kernel version (2.6.32.x)
> - system (Ubuntu)
> - container was unstoppable(?) even if there were no processess
> - the way
Serge E. Hallyn wrote, On 2010. 08. 31. 15:26:
> Quoting Papp Tamás (tom...@martos.bme.hu):
>
>> Serge E. Hallyn wrote, On 2010. 08. 31. 4:06:
>>
>>> Quoting Daniel Lezcano (daniel.lezc...@free.fr):
>>>
On 08/31/2010 12:23 AM, Serge E. Hallyn wrote:
> Quoting
"Serge E. Hallyn" writes:
> Quoting Ferenc Wagner (wf...@niif.hu):
>> "Serge E. Hallyn" writes:
>>
>>> Quoting Daniel Lezcano (daniel.lezc...@free.fr):
>>>
On 08/31/2010 12:23 AM, Serge E. Hallyn wrote:
> Quoting Daniel Lezcano (daniel.lezc...@free.fr):
>
>> http://git.ker
Quoting Serge E. Hallyn (serge.hal...@canonical.com):
> > >Without a bug, an SRU ain't gonna fly.
> >
> > Sure I can do this. What should I write in the report exactly and
> > what is the correct email address I write to?
> >
> > - kernel version (2.6.32.x)
> > - system (Ubuntu)
>
> and that it'
Quoting Ferenc Wagner (wf...@niif.hu):
> "Serge E. Hallyn" writes:
>
> > Quoting Daniel Lezcano (daniel.lezc...@free.fr):
> >
> >> On 08/31/2010 12:23 AM, Serge E. Hallyn wrote:
> >>
> >>> Quoting Daniel Lezcano (daniel.lezc...@free.fr):
> >>>
> http://git.kernel.org/?p=linux/kernel/git/next
Quoting Papp Tamás (tom...@martos.bme.hu):
>
> Serge E. Hallyn wrote, On 2010. 08. 31. 4:06:
> >Quoting Daniel Lezcano (daniel.lezc...@free.fr):
> >>On 08/31/2010 12:23 AM, Serge E. Hallyn wrote:
> >>>Quoting Daniel Lezcano (daniel.lezc...@free.fr):
> On 08/30/2010 02:36 PM, Serge E. Hallyn wr
On 08/31/2010 12:07 PM, Papp Tamás wrote:
>
> Serge E. Hallyn wrote, On 2010. 08. 31. 4:06:
>> Quoting Daniel Lezcano (daniel.lezc...@free.fr):
>>> On 08/31/2010 12:23 AM, Serge E. Hallyn wrote:
Quoting Daniel Lezcano (daniel.lezc...@free.fr):
> On 08/30/2010 02:36 PM, Serge E. Hallyn wrot
Serge E. Hallyn wrote, On 2010. 08. 31. 4:06:
> Quoting Daniel Lezcano (daniel.lezc...@free.fr):
>
>> On 08/31/2010 12:23 AM, Serge E. Hallyn wrote:
>>
>>> Quoting Daniel Lezcano (daniel.lezc...@free.fr):
>>>
On 08/30/2010 02:36 PM, Serge E. Hallyn wrote:
> Qu
Daniel Lezcano wrote, On 2010. 08. 30. 15:05:
> Ah, interesting. You killed the container's init and the processes
> were still there ? If it's the case, I suppose there is a kernel bug.
> Did you check if there is a kernel BUG in the /var/log/message ?
The is no BUG in the log.
I'm sorry, I'
Ferenc Wagner wrote, On 2010. 08. 31. 11:47:
> I'm not sure what an SRU is, is that something Ubuntu-specific? I'd
> appreciate instead going through sta...@kernel.org, so that everybody
> benefits from this backporting effort. New 2.6.32.y stable releases are
> automatically incorporated by mos
"Serge E. Hallyn" writes:
> Quoting Daniel Lezcano (daniel.lezc...@free.fr):
>
>> On 08/31/2010 12:23 AM, Serge E. Hallyn wrote:
>>
>>> Quoting Daniel Lezcano (daniel.lezc...@free.fr):
>>>
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commit;h=13aa9a6b0f2371d2ce0de57c2ede62
Quoting Daniel Lezcano (daniel.lezc...@free.fr):
> On 08/31/2010 12:23 AM, Serge E. Hallyn wrote:
> >Quoting Daniel Lezcano (daniel.lezc...@free.fr):
> >>On 08/30/2010 02:36 PM, Serge E. Hallyn wrote:
> >>>Quoting Papp Tamás (tom...@martos.bme.hu):
> Daniel Lezcano wrote, On 2010. 08. 30. 13:08
On 08/31/2010 12:23 AM, Serge E. Hallyn wrote:
> Quoting Daniel Lezcano (daniel.lezc...@free.fr):
>
>> On 08/30/2010 02:36 PM, Serge E. Hallyn wrote:
>>
>>> Quoting Papp Tamás (tom...@martos.bme.hu):
>>>
Daniel Lezcano wrote, On 2010. 08. 30. 13:08:
> Usual
Quoting Daniel Lezcano (daniel.lezc...@free.fr):
> On 08/30/2010 02:36 PM, Serge E. Hallyn wrote:
> >Quoting Papp Tamás (tom...@martos.bme.hu):
> >>Daniel Lezcano wrote, On 2010. 08. 30. 13:08:
> >>>Usually, there is a mechanism used in lxc to kill -9 the process 1 of
> >>>the container (which wipe
On 08/30/2010 03:01 PM, Ferenc Wagner wrote:
> Daniel Lezcano writes:
>
>> The cgroup is not removed automatically by the cgroup infrastructure
>> when all the tasks die, it's how the cgroup is implemented. So it is
>> up to lxc-start to remove the cgroup after the pid 1 of the container
>> exits.
On 08/30/2010 02:20 PM, Papp Tamás wrote:
>
> Daniel Lezcano wrote, On 2010. 08. 30. 13:08:
>> The cgroup is removed by lxc-start, but this is not a problem,
>> because it will be removed (if empty), when running lxc-start again.
>
> If I understand well, this happened to me now.
>
>>
* the
Daniel Lezcano writes:
> The cgroup is not removed automatically by the cgroup infrastructure
> when all the tasks die, it's how the cgroup is implemented. So it is
> up to lxc-start to remove the cgroup after the pid 1 of the container
> exits. If lxc-start was killed, this directory will not be
On 08/30/2010 02:36 PM, Serge E. Hallyn wrote:
> Quoting Papp Tamás (tom...@martos.bme.hu):
>
>> Daniel Lezcano wrote, On 2010. 08. 30. 13:08:
>>
>>> Usually, there is a mechanism used in lxc to kill -9 the process 1 of
>>> the container (which wipes out all the processes of the container
Daniel Lezcano writes:
> On 08/30/2010 12:40 PM, Papp Tamás wrote:
>
>> In the tasks file I saw three processes: udevd, init and one more, which
>> I don't remember. I killed them all, but the cgroup still exists.
>
> The cgroup is removed by lxc-start, but this is not a problem, because
> it wi
On 08/30/2010 02:11 PM, Ferenc Wagner wrote:
> Daniel Lezcano writes:
>
>
>> On 08/30/2010 12:40 PM, Papp Tamás wrote:
>>
>>
>>> In the tasks file I saw three processes: udevd, init and one more, which
>>> I don't remember. I killed them all, but the cgroup still exists.
>>>
>> T
Quoting Papp Tamás (tom...@martos.bme.hu):
> Daniel Lezcano wrote, On 2010. 08. 30. 13:08:
> > Usually, there is a mechanism used in lxc to kill -9 the process 1 of
> > the container (which wipes out all the processes of the containers)
> > when lxc-start dies.
>
> It should wipe out them, but i
Daniel Lezcano wrote, On 2010. 08. 30. 13:08:
> The cgroup is removed by lxc-start, but this is not a problem, because
> it will be removed (if empty), when running lxc-start again.
If I understand well, this happened to me now.
>
>>> * the state of the processes of the containers (stopped or
On 08/30/2010 12:40 PM, Papp Tamás wrote:
>
> Daniel Lezcano wrote, On 2010. 08. 30. 11:26:
>> Hmm, too bad :) I was about to ask you some informations about the
>> processes of the containers.
>
> Well, I was happy too early.
>
>> If that happens again, can you check/report the following :
>>
>>
Daniel Lezcano wrote, On 2010. 08. 30. 11:26:
> Hmm, too bad :) I was about to ask you some informations about the
> processes of the containers.
Well, I was happy too early.
> If that happens again, can you check/report the following :
>
> * the content of the tasks file in the cgroup direc
On 08/30/2010 11:13 AM, Papp Tamás wrote:
> Papp Tamás wrote, On 2010. 08. 30. 10:41:
>
>> hi!
>>
>> I cannot stop a container.
>>
>> I tried everything, as running lxc-stop many times, destroy&create&stop,
>> nothing helped.
>>
>> The directory /cgroup/ is still exist.
>>
>> How can I destroy
Papp Tamás wrote, On 2010. 08. 30. 10:41:
> hi!
>
> I cannot stop a container.
>
> I tried everything, as running lxc-stop many times, destroy&create&stop,
> nothing helped.
>
> The directory /cgroup/ is still exist.
>
> How can I destroy it? I need a way which doesn't affect the other
> contain
hi!
I cannot stop a container.
I tried everything, as running lxc-stop many times, destroy&create&stop,
nothing helped.
The directory /cgroup/ is still exist.
How can I destroy it? I need a way which doesn't affect the other
containers.
Thank you,
tamas
---
29 matches
Mail list logo
