|| ||Jean-Marc Pigeon <jmp-4qkeo2rQ0gg-AT-public.gmane.org> |
|| ||containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA-AT-public.gmane.org |
|| ||container sharing /proc/kmsg??? |
|| ||Tue, 12 Jan 2010 17:09:55 -0500|
|| ||Article, Thread
I have done a small utility to build containers
using kernel API 'clone' available with kernel-2.6.31.
So far I am able to run more than 30 different
distribution (from rh7.3 -> fc12) on the same
(ftp://ftp.safe.ca/pub/linux/vzgot to know more.)
Everything is working fine...
Except seems HOST and all containers share the
SAME /proc/kmsg, meaning kernel syslog information
are scrambled (useless).
Namely, I have in iptables, reject packet logging
on the HOST, as soon rsyslog is started on one
container, I can't see my reject packet log anymore.
Also, container have their own iptables with reject
packet logging which are not displayed too.
Am I wrong/forgetting something about the /proc/kmsg
If I am right, should ALL /proc/kmsg be isolated from
How could it be done??
Jean-Marc Pigeon Internet: email@example.com
SAFE Inc. Phone: (514) 493-4280
Fax: (514) 493-1946
Clement, 'a kiss solution' to get rid of SPAM (at last)
Clement' Home base <"http://www.clement.safe.ca">
Containers mailing list
to post comments)