[systemd-devel] pam_limits: Could not set limit for ...: Operation not permitted

[Lennart Poettering]

On Tue, 10.02.15 20:16, Kai Krakow (hurikhan77 at gmail.com) wrote:

> Then the question is: Why or what does try to start a user session in the 
> first place? I don't think KDE does this as it's not there yet (at least in 
> KDE 4.x). And I didn't enable a user at ...service (but shouldn't it work then 
> when started from the normal service startups in systemd).

logind maintains one user at .service instance per-user as long as she or
he is logged in at least once. The service is basically ref-counted by
the user's session.

> I don't consider this a bug, but my main problem with this is I have no idea 
> how to track that down.

Do you have any weird kernel patch applied, something that is supposed
to improve security or so?

> >> I suppose for the same reason, rtkit-daemon cannot give RT priority to
> >> itself...
> > 
> > This is unrelated. The kernel RT cgroup API is really just awfully
> > broken, ignore this.
> 
> Maybe just turn off the RT_FIFO feature in the kernel for the time
> being?

Nah, just ignore that log msg...

Lennart

-- 
Lennart Poettering, Red Hat