systemd has taken over cron too? I suppose that is a logical extension,
but still...
--
paul moore
www.paul-moore.com
On January 9, 2015 4:01:29 PM Dominick Grift <dac.override@xxxxxxxxx> wrote:
On Fri, 2015-01-09 at 15:55 -0500, Paul Moore wrote:
> On Friday, January 09, 2015 02:13:29 PM Dave Jones wrote:
> > On Fri, Jan 09, 2015 at 08:06:49AM -0500, Stephen Smalley wrote:
> > > We already reduced that message to KERN_DEBUG. Is that not sufficient?
> >
> > That doesn't really help with the flooding of dmesg, so no.
> > I should also note that it's not just logging in that creates a new
> > session, it also seems to be getting triggered by cron jobs, or
> > whatever the systemd replacement is.
>
> I wonder if this is cron/systemd/whatever creating a new namespace and
> mounting a new tmpfs in the namespace? If yes, I wonder if we could
limit the
> messages to the initial namespace ... ?
>
It is systemd logind creating sessions (e.g. creating /run/user/$UID and
mounting a tmpfs on it)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
_______________________________________________
Selinux mailing list
Selinux@xxxxxxxxxxxxx
To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx.
To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
