Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: "Chris R. Jones" <chris-SqNQQPNds68nxqbYAscKCQ@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: Re: Containers syslog support?
Date: Tue, 14 Apr 2009 09:21:14 -0500	[thread overview]
Message-ID: <20090414142113.GA6072@us.ibm.com> (raw)
In-Reply-To: <20090413215315.GA28487-SqNQQPNds68nxqbYAscKCQ@public.gmane.org>

Quoting Chris R. Jones (chris-SqNQQPNds68nxqbYAscKCQ@public.gmane.org):
> Hello again,
> 
> Another question on containers.  This time, for syslog.  Is there any
> containers support to isolate syslog entries for different containers?
> That is, is there any way I can run two different syslogd processes in
> two different containers, in such a way that each syslogd process only
> sees and logs events generated by processes in it's own container?
> 
> Are syslog messages covered under one of the other namespaces (pids, utsname, sysv ipc, network, users), or is there a seperate namespace for them.
> 
> Thanks,
> Chris

You can run syslogd in two different containers if they have different
network namespaces, bc /dev/log should be different for each.  So if
user-space software is using syslog(3) it's msgs should stay inside the
container.  I haven't played with it, though.  If you run a quick
(presumably trivial) test, pls let us know how it goes.

(Of course kernel (printk) messages will go to the klogd in the initial
network namespace, as they should.)

-serge

      parent reply	other threads:[~2009-04-14 14:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 21:53 Containers syslog support? Chris R. Jones
     [not found] ` <20090413215315.GA28487-SqNQQPNds68nxqbYAscKCQ@public.gmane.org>
2009-04-14 14:21   ` Serge E. Hallyn [this message]

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=20090414142113.GA6072@us.ibm.com \
    --to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=chris-SqNQQPNds68nxqbYAscKCQ@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox