# Too many open files

**URL:** <https://www.debian-fr.org/t/too-many-open-files/91521>\
**Category:** Support Debian\
**Tags:** système, limit, bookworm\
**Created:** [Septembre 9, 2025, 9:31 UTC](https://www.debian-fr.org/t/too-many-open-files/91521 "2025-09-09T09:31:25Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![red0queen](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/r/b5e925/32.png) [@red0queen](https://www.debian-fr.org/u/red0queen)\
**Post date:** [Septembre 10, 2025, 9:36 UTC](https://www.debian-fr.org/t/too-many-open-files/91521/15 "2025-09-10T09:36:08Z")

</div>

Je viens de trouver ça. Il semble que cette limite soit codé en dur dans transmission, et pas moyen de la changer depuis sa conf. Donc pas le choix que de faire une bidouille depuis un script qui va vérifier la valeur et la changer si besoin… grrr…

Merci pour votre aide ! D’en discuter avec d’autres m’a bien aidé !

> <https://github.com/transmission/transmission/issues/309>
>
> Hello,
> if i read
> 
> \`\`\`
> $ git grep FD\_SETSIZE
> CMakeLists.txt: set(CMAK…E\_${L}\_FLAGS "${CMAKE\_${L}\_FLAGS} -DFD\_SETSIZE=1024")
> gtk/tr-prefs.c: w = new\_spin\_button (TR\_KEY\_peer\_limit\_per\_torrent, core, 1, FD\_SETSIZE, 5);
> gtk/tr-prefs.c: w = new\_spin\_button (TR\_KEY\_peer\_limit\_global, core, 1, FD\_SETSIZE, 5);
> libtransmission/fdlimit.c: /\* set the open-file limit to the largest safe size wrt FD\_SETSIZE \*/
> libtransmission/fdlimit.c: const int new\_limit = MIN (limit.rlim\_max, FD\_SETSIZE);
> qt/PrefsDialog.cc: #include \<winsock2.h\> // FD\_SETSIZE
> qt/PrefsDialog.cc: #include \<sys/select.h\> // FD\_SETSIZE
> qt/PrefsDialog.cc: ui.torrentPeerLimitSpin-\>setRange (1, FD\_SETSIZE);
> qt/PrefsDialog.cc: ui.globalPeerLimitSpin-\>setRange (1, FD\_SETSIZE);
> third-party/miniupnp/receivedata.c: n = select(FD\_SETSIZE, &socketSet, NULL, NULL, &timeval);
> \`\`\`
> 
> you force the max number of file descriptors to 1024.
> 
> now, let's say i have a systems where i could run transmission with more than \_just\_ 1024 fds, wouldnt it be fantastic if i could specify it either as a configuration option (or using ulimit in the init script)?
> 
> is there any reason to hardcode this value at compile time and not make it dynamically changable by the users (unless you want to prevent to have them shot themselves in the foot, but that could happen anyway)
> 
> thanks for considering

---

_[View the full topic](https://www.debian-fr.org/t/too-many-open-files/91521)._