containerized syslog

Matt Helsley matthltc at
Sat Feb 13 08:03:20 PST 2010

On Sat, Feb 13, 2010 at 07:58:13AM -0800, Matt Helsley wrote:


> Your comments seem good. However, I do have an issue with the
> idea of finding a single syslog corresponding to the netns for
> a hypothetical printk in iptables.
> What happens with:
> /* in init_syslog_ns */
> clone(CLONE_SYSLOG) /* syslog_ns 1 */
> clone(CLONE_SYSLOG) /* syslog_ns 2 */
> <do something with iptables in the netns which triggers a printk>
> Even though that same printk is relevant to three "syslogs", it'll
> only go to one, correct? If so, my feeling is that nsprintk
> shouldn't take a syslog_ns directly. It should take some other
> form of namespace and then write to the syslog of all the

Sorry, I don't think I worded this clearly. "some other form" means a
non-syslog_ns which is "relevant" to the printk e.g. a netns for
iptables code.

	-Matt Helsley

More information about the Containers mailing list