Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
Something like having a single kernel ring buffer (like now), that a single daemon would listen to, but have per namespace buffers that would be feed by that daemon according with user-space rules.
Stepping closer to practical containers: "syslog" namespaces
Posted Dec 10, 2012 0:54 UTC (Mon) by dlang (✭ supporter ✭, #313)
I would say that this filtering should probably be happening in userspace, where the tools like rsyslog already support very extensive logic for doing this.
This includes the ability to deliver to additional copies of rsyslog that are running inside your namespace containers
Posted Dec 13, 2012 5:38 UTC (Thu) by eternaleye (guest, #67051)
Posted Dec 13, 2012 5:41 UTC (Thu) by eternaleye (guest, #67051)
Posted Dec 13, 2012 9:43 UTC (Thu) by nlucas (subscriber, #33793)
As for not being transparent, I'm talking of a ring-buffer per container, so it's fully transparent for the applications. dmesg will output the namespace ring-buffer contents.
The initial namespace "syslog" daemon would dispatch messages from the unfiltered ring-buffer to the other namespaces ring-buffers. The difference would be that the syslog(2) syscall would be namespace aware and return messages only from the current namespace ring-buffer.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds