Public bug reported:
Setting the maximum number of open files via pam's
/etc/security/limits.conf (setting nofile) does only work for values
less than 1024, not above
This seems to work on Gentoo, Red Hat and SuSE quite well so I started
to look why it does not in ubuntu.
I found out that a patch applied durcing build is causing this:
in
debian/patches-applied/027_pam_limits_better_init_allow_explicit_root
you find the following on line 59:
+ pl->limits[i].limit.rlim_max = 1024;
which seems to set the maximum for RLIMIT_NOFILE to 1024 which IMO is
non-sense.
We have many servers that have it set to 65536 for big applications.
If I increase this rlim_max value, the default is still 1024 but I can rise it
to limit.rlim_max -1
Please fix this by setting a reasonable value here. The kernel maximum is 2^20
= 1024*1024 = 1048576
(See "sysctl fs.nr_open" or "cat /proc/sys/fs/nr_open")
So I suggest setting it to 1024*1024 instead of 1024 value to not have a
synthetic limit here
See attached patch for the patch which fixes it.
-Marc
** Affects: pam (Ubuntu)
Importance: Undecided
Status: New
--
nofile limit cannot be increased, only decreased
https://bugs.launchpad.net/bugs/327597
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
