Opened 6 years ago
Last modified 6 years ago
#1421 new enhancement
worker_rlimit_nofile description is not clear
|Reported by:||Owned by:|
Currently documentation for "worker_rlimit_nofile" configuration parameter says
Changes the limit on the maximum number of open files (RLIMIT_NOFILE) for worker processes.
Изменяет ограничение на максимальное число открытых файлов (RLIMIT_NOFILE) для рабочих процессов.
It's not clear whether the limit is applied for each worker separately, or it's the maximum number of files which can be opened by all workers in total.
There is the same issue with "worker_rlimit_core" parameter.
Change History (1)
comment:1 by , 6 years ago
Note: See TracTickets for help on using tickets.
Both directives clearly reference to corresponding OS limits,
RLIMIT_CORE. Quoting setrlimit() description as available in POSIX:
That is, both limits are for a given process - unless your OS does something completely non-standard. And this should be immediately obvious for anybody who understands what
We may consider linking to something appropriate for ones who don't know what
RLIMIT_NOFILEmeans. Though I don't think that the above link to POSIX is appropriate here, mostly because POSIX structure suggests that linking there might not be a good idea (and I believe opengroup.org even asked an email before providing access to onlinepubs), and I'm not aware of other good and OS-neutral links.
(Also, clearly there is no such thing as a core file size limit for "all workers in total", it simply doesn't make sense.)