You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The systemd units of the deb packages set LimitNOFILE=1000000, which is VERY high. Even on modern systems, the hard limit is usually at 524288, the default at 1024, e.g. since the select syscall does not work with higher values.
Hence I am wondering how many open files to expect on a self-hosted instance, and also whether the signaling server keeps them open after the peers connected via P2P or relay server, or whether it disconnects after the peers have established a connection with each other?
Of course I do understand that RustDesk's own public servers must allow such numbers of connections, hence raised limits.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The systemd units of the deb packages set
LimitNOFILE=1000000, which is VERY high. Even on modern systems, the hard limit is usually at 524288, the default at 1024, e.g. since theselectsyscall does not work with higher values.Hence I am wondering how many open files to expect on a self-hosted instance, and also whether the signaling server keeps them open after the peers connected via P2P or relay server, or whether it disconnects after the peers have established a connection with each other?
Of course I do understand that RustDesk's own public servers must allow such numbers of connections, hence raised limits.
Beta Was this translation helpful? Give feedback.
All reactions