Control: forcemerge -1 917168 917173 Control: severity -1 grave Am 23.12.18 um 18:27 schrieb Baptiste BEAUPLAT: > Dear maintainers, > > This issue seems related to #917168, feel free to merge it. > > For the 100% cpu, I think the problem is here in kinit: > > https://github.com/KDE/kinit/blob/master/src/kdeinit/kinit.cpp#L163
Thanks, that helps a lot, Baptiste! For reference, it's related to https://github.com/systemd/systemd/issues/10921 In v240, rlimit is bumped to INT_MAX in PID 1. For processes that are spawned by PID 1, the limits are set differently though, so the unlimited rlimit for PID 1 should have no effect on other processes. Problem is, pam_limits.so in Debian ships a custom patch, which reads the limits from PID 1 and set those for login sessions. So, ultimately, it's both a bug in pam_limits but also kinit, which should behave more sensibly if rlimit is set to a high value. We can work around that in systemd though, which is what I plan to do for the time being. For a (temporary) workaround you can create a file /etc/security/limits.d/systemd.conf containing: * hard nofile 524288 This will make pam_limits behave properly. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
