Limit for nofile set too high

[reswild]

I went through my server logs the other day, and I noticed that my auth log was being filled up with endless warnings about su: pam_limits(su-l:session): Could not set limit for 'nofile' to soft=2097152, hard=2097152: Operation not permitted; uid=0,euid=0 I can see that this was caused by this commit from a few months ago: https://github.com/omega8cc/boa/commit/7227341116e4039e4fe4b8af978c888559eecc21

It appears that 1048576 is the highest value my system will accept as a nofile limit, so I manually edited /etc/security/limits.conf, and restored the previous values.

[EdNett]

Thanks for the fix; I had the same problem.

[omega8cc]

@reswild what is your virtualization system and host?

_{Sent with GitHawk}

[reswild]

@omega8cc I had the issue on both Hetzner and DigitalOcean. I believe they both use KVM.

[lexsoft00]

Same thing

Mar 3 06:34:27 lon su: pam_limits(su-l:session): Could not set limit for 'nofile' to soft=2097152, hard=2097152: Operation not permitted; uid=0,euid=0

OVH VPS Model VPS vps2020-elite-8-16-160 vCores 8 Memory 16 GB Storage 160 GB

[omega8cc]

This should be reverted and made configurable.

_{Sent with GitHawk}

[omega8cc]

This has been reverted in 5.2.0 release.