On 02/04/2010 04:19 PM, Serge E. Hallyn wrote:
> I still like your syslog command 11, but assuming we want to keep the
> syslog_ns on nsproxy, I think we really need to stick to clone/unshare.
Yes. let's keep the namespace creation API consistent. this is complex
enough.
C.
-
Quoting Daniel Lezcano (daniel.lezc...@free.fr):
> Serge E. Hallyn wrote:
> >Quoting Daniel Lezcano (daniel.lezc...@free.fr):
> >>Serge E. Hallyn wrote:
> >>>Quoting Jean-Marc Pigeon (j...@safe.ca):
> Hello,
>
>
> >I was wondering out loud about the best design to solve his proble
Serge E. Hallyn wrote:
> Quoting Daniel Lezcano (daniel.lezc...@free.fr):
>
>> Serge E. Hallyn wrote:
>>
>>> Quoting Jean-Marc Pigeon (j...@safe.ca):
>>>
Hello,
> I was wondering out loud about the best design to solve his problem.
>
> If we t
Quoting Jean-Marc Pigeon (j...@safe.ca):
> Hello,
>
> [...]
> > >
> > > The prink keeps writing in the global ring buffer and the syslog(2)
> > > writes to the "namespaced" ring buffer.
> > >
> > > Does it makes sense ?
> >
> > Yeah, it's a nice alternative. Though (1) there is something to be
Hello,
[...]
> >
> > The prink keeps writing in the global ring buffer and the syslog(2)
> > writes to the "namespaced" ring buffer.
> >
> > Does it makes sense ?
>
> Yeah, it's a nice alternative. Though (1) there is something to be said for
> forcing a new ring buffer upon clone(CLONE_NEWUSE
Quoting Daniel Lezcano (daniel.lezc...@free.fr):
> Serge E. Hallyn wrote:
> >Quoting Jean-Marc Pigeon (j...@safe.ca):
> >>Hello,
> >>
> >>
> >>>I was wondering out loud about the best design to solve his problem.
> >>>
> >>>If we try to redirect kernel-generated messages to containers, we have
> >>
Hello
[..]
>
>
> We have:
> * Commands to sys_syslog:
> *
> * 0 -- Close the log. Currently a NOP.
> * 1 -- Open the log. Currently a NOP.
> * 2 -- Read from the log.
> * 3 -- Read all messages remaining in the ring buffer.
>
Serge E. Hallyn wrote:
> Quoting Jean-Marc Pigeon (j...@safe.ca):
>> Hello,
>>
>>
>>> I was wondering out loud about the best design to solve his problem.
>>>
>>> If we try to redirect kernel-generated messages to containers, we have
>>> several problems, including whether we need to duplicate the
Quoting Jean-Marc Pigeon (j...@safe.ca):
> Hello,
>
>
> >
> > I was wondering out loud about the best design to solve his problem.
> >
> > If we try to redirect kernel-generated messages to containers, we have
> > several problems, including whether we need to duplicate the messages
> > to the
Hello,
>
> I was wondering out loud about the best design to solve his problem.
>
> If we try to redirect kernel-generated messages to containers, we have
> several problems, including whether we need to duplicate the messages
> to the host container. So in one sense it seems more flexible to
Quoting Daniel Lezcano (daniel.lezc...@free.fr):
> Jean-Marc Pigeon wrote:
> > Hello,
> >
> > On Tue, 2010-02-02 at 04:16 +0100, Michael Holzt wrote:
> >
> >>> Tried 2.6.33-rc6 to check container, 3 bugs show up.
> >>> (test done on x86_64, Pentium(R) Dual-Core CPU E5400)
> >>>
> >> I
Jean-Marc Pigeon wrote:
> Hello,
>
> On Tue, 2010-02-02 at 04:16 +0100, Michael Holzt wrote:
>
>>> Tried 2.6.33-rc6 to check container, 3 bugs show up.
>>> (test done on x86_64, Pentium(R) Dual-Core CPU E5400)
>>>
>> I guess this should better go on the containers mailing list,
>>
Hello,
On Tue, 2010-02-02 at 04:16 +0100, Michael Holzt wrote:
> > Tried 2.6.33-rc6 to check container, 3 bugs show up.
> > (test done on x86_64, Pentium(R) Dual-Core CPU E5400)
>
> I guess this should better go on the containers mailing list,
> as this are kernel related problems?
> Tried 2.6.33-rc6 to check container, 3 bugs show up.
> (test done on x86_64, Pentium(R) Dual-Core CPU E5400)
I guess this should better go on the containers mailing list,
as this are kernel related problems?
Regards,
Michael
--
It's an insane world, but i'm proud to be a part of i
Hello,
Tried 2.6.33-rc6 to check container, 3 bugs show up.
(test done on x86_64, Pentium(R) Dual-Core CPU E5400)
#1: Critical / fixed?:
Already reported: system hang very badly if you start
a container (clone) while cloneflag is set with at least
15 matches
Mail list logo
