Opened 10 years ago
Closed 10 years ago
#4294 closed Bug (invalid)
open-file-limit always set to max 384
| Reported by: | AndreyPopovNew | Owned by: | |
|---|---|---|---|
| Priority: | High | Milestone: | None Set |
| Component: | Transmission | Version: | 2.31 |
| Severity: | Normal | Keywords: | open file limit |
| Cc: |
Description
OpenWRT x86 image trunk 27019 from 28 may 2011.
open-file-limit always set to max 384.
even if modify in setting.json to 65535 (also previously run ulimit -n 65535) after start transmission-daemon open-file-limit revert to 384.
P.S. in 2.22 version I can set open-file-limit to 65535
Change History (1)
comment:1 Changed 10 years ago by jordan
- Resolution set to invalid
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
It's intentional that the open file limit is bounded by FD_SETSIZE. This is necessary to prevent memory corruption errors in libcurl, see #4164 for more information.
Actually I'm wondering if the open-file-limit configuration setting is worth keeping around anymore. Perhaps libtransmission should automatically set it to the maximum allowed by FD_SETSIZE.