wildcard(*) configuration don't work in /etc/security/limits.conf
Bug #509654 reported by
Diego Plentz
This bug report is a duplicate of:
Bug #314222: setting core dump size to above 0 does not work in /etc/security/limits.conf.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pam (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
If you change the soft and hardlimit of nofile inside /etc/security/
* soft nofile 2048
* hard nofile 4096
won't work. but this works:
jetty soft nofile 2048
jetty hard nofile 4096
root@dc-app:~# lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
visibility: | private → public |
To post a comment you must log in.
limits.conf is handled by the pam_limits PAM module which is included in the base set of modules.