So on my ubuntu 18.04.06 it works.
What do you see if once you login to your home box, try using ssh to connect to your home box again. Then what does ulimit tell you about rtprio?
cheers
bruce
On 2021-09-29T21:29:03.000+02:00, tim Rowledge tim@rowledge.org wrote:
Running `sudo grep limit /etc/pam.d` on my ubuntubox reveals that cron, login, runuser, sshd, su and systemd-user refer to limit. login explicitly claims to defer to /etc/security/limits.conf runuser has the exact same line sshd ditto su ditto and finally systemd-user ditto So they all use `session required pam_limits.so` and that claims (according to www.man7.org/linux/man-page... [https://www.man7.org/linux/man-pages/man8/pam_limits.8.html%5D)%C2%A0to%C2%A.... Despite us doing what looks like al lthe right stuff, `ulimit -a` says my realtime priority setting is 0. To add further to the irritation, on the work server it has done the right thing and the rtprio setting is 2. Grrrrrrr. It has the same /etc/security/limits/d/squeak.conf - and indeed it works just fine on my Raspberry Pi 64bit OS. The output of the grep above is the same. In superuser.com/questions/740... [https://superuser.com/questions/740000/modify-and-apply-limits-conf-without-... The potentially big difference between the local ubuntubox and the work one is that mine is 18.04.4 and the work one is 20.04 My brian hertz. tim -- tim Rowledge; tim@rowledge.org; www.rowledge.org/tim [http://www.rowledge.org/tim] A)bort, R)etry, P)ee in drive door