On Sun, Feb 03, 2019 at 09:47:25AM +0100, Stéphane Graber wrote:
> Hi,
>
> Yes, this is normal and as pointed out already, can be tweaked with
> dmesg_restrict.
>
> There was some interest a while back in implementing a logging
> namespace, which would solve this cleanly, but it's never been
On 3/02/19 3:54 PM, Tomasz Chmielewski wrote:
> On 2019-02-03 11:51, Richard Hector wrote:
>> Hi all,
>>
>> I've noticed that some log messages that really belong to the host (like
>> those from monthly RAID checks, for example) can appear in arbitrary
>> containers instead - so they're spread all
Hi,
Yes, this is normal and as pointed out already, can be tweaked with
dmesg_restrict.
There was some interest a while back in implementing a logging
namespace, which would solve this cleanly, but it's never been enough
of a priority for anyone to actually do the kernel work for it.
Stéphane
On 2019-02-03 11:51, Richard Hector wrote:
Hi all,
I've noticed that some log messages that really belong to the host
(like
those from monthly RAID checks, for example) can appear in arbitrary
containers instead - so they're spread all over the place.
Is that normal/fixable?
I'd say it's a
Hi all,
I've noticed that some log messages that really belong to the host (like
those from monthly RAID checks, for example) can appear in arbitrary
containers instead - so they're spread all over the place.
Is that normal/fixable?
Cheers,
Richard
