All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Marc Pigeon <jmp-4qkeo2rQ0gg@public.gmane.org>
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: container sharing /proc/kmsg???
Date: Tue, 12 Jan 2010 17:09:55 -0500	[thread overview]
Message-ID: <1263334195.4745.250.camel@Mercier.safe.ca> (raw)

Hello,


	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
	host.
	(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
	sharing?

	If I am right, should ALL /proc/kmsg be isolated from
	each other???
	
	How could it be done??

-- 
A bientôt
==========================================================================
Jean-Marc Pigeon                                   Internet: jmp@safe.ca
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
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers

             reply	other threads:[~2010-01-12 22:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 22:09 Jean-Marc Pigeon [this message]
     [not found] ` <1263334195.4745.250.camel-4BUXZ/Ty1v7iqR6jatDSCA@public.gmane.org>
2010-01-13 16:32   ` container sharing /proc/kmsg??? Serge E. Hallyn
     [not found]     ` <20100113163251.GA18184-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-01-13 16:48       ` Jean-Marc Pigeon
     [not found]         ` <1263401337.4745.282.camel-4BUXZ/Ty1v7iqR6jatDSCA@public.gmane.org>
2010-01-13 17:05           ` Serge E. Hallyn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1263334195.4745.250.camel@Mercier.safe.ca \
    --to=jmp-4qkeo2rq0gg@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.