the rule say ACCEPT!).
On 2.6.34 /sys is not containerized (you see the
host /sys/class/net devices), but it is containerized
on 2.6.35 (you see own container net devices only)...
May be the network problem is related to /sys change.
My 2 cents.
--
A bientôt
==
Jean-M
ons for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> Lxc-users mailing list
> Lxc-users@lists.sourceforge.net
> h
idea (duplicating&forwarding is done by tools as
rsyslogd).
>
> After we start getting flexible with syslog, the next request will be for
> audit flexibility. I don't even know how our netlink support suffices for
> that right now.
>
> (So, this all does turn into a big deal
ip filtering superset).
So CONT:printk must be writing too in the
"namespaced" ring buffer.
--
A bientôt
==
Jean-Marc Pigeon Internet: j...@safe.ca
SAFE Inc.
o me, as long /proc/kmsg is not existing
(/dev/null) in the CONT file tree.
--
A bientôt
==========
Jean-Marc Pigeon Internet: j...@safe.ca
SAFE Inc.
could
propagate up to the HOST)? suggestion?
--
A bientôt
======
Jean-Marc Pigeon Internet: j...@safe.ca
SAFE Inc.
specific
CONT problem???
My 3 cents.
Seems to me we are very close to have a "production"
container, thanks to all contributor...
--
A bientôt
=======
