| |||||||||||||
Stepping closer to practical containers: "syslog" namespacesStepping closer to practical containers: "syslog" namespacesPosted Dec 6, 2012 19:43 UTC (Thu) by mhelsley (subscriber, #11324)Parent article: Stepping closer to practical containers: "syslog" namespaces
It seems to me that all of this assumes only one namespace could be relevant to any given printk. I don't think that's a safe assumption -- it might be that multiple namespaces with differing user/syslog namespaces are relevant to the same printk. What should happen then?
(Log in to post comments)
Stepping closer to practical containers: "syslog" namespaces Posted Dec 7, 2012 2:22 UTC (Fri) by Beolach (subscriber, #77384) [Link]
Possibly w/ multiple nsprintk() calls, specifying all of the relevant namespaces (1 in each call). Assuming you can identify them... but hopefully that wouldn't be difficult (if it's not possible, then maybe it is a safe assumption that the message is only relevant to one namespace).
|
|||||||||||||