File descriptor limit on CentOS 7

Asked Feb 27 '16 at 01:35

Active Feb 27 '16 at 14:23

Viewed 2,498 times

I am having hard time understanding resource limits (ulimit) with systemd. As I understand it, systemd brings some additional complexities to setting file descriptor limit.

/etc/security/limits.d/99-name.conf

couchbase hard nofile 100000
couchbase soft nofile 100000

/etc/systemd/system/[SERVICE_NAME].service.d/limits.conf

[Service]
LimitNOFILE=100000

I found this and this, but it rises more questions than answers.

Which of the above is correct and why (or is there some other way, or should I set both)?
Can I use ulimit command?
How do I verify that the limit is really set for a daemon?
What about daemons, which relies on ulimit?

edited Feb 27 '16 at 14:23

030

5,901
13
68
110

asked Feb 27 '16 at 01:35

NefariousOctopus

The systemd service drop-in should be working. – Michael Hampton Feb 27 '16 at 01:36
@MichaelHampton So the "/etc/security/limits.d/" way is now deprecated? – NefariousOctopus Feb 27 '16 at 01:40
I don't remember if it's deprecated or not, but I certainly don't use it anymore. – Michael Hampton Feb 27 '16 at 01:41

File descriptor limit on CentOS 7

0 Answers0