http://bugs.winehq.org/show_bug.cgi?id=59851 --- Comment #3 from quasar quasar <quasarhasanewemail@proton.me> ---
Do I assume correctly that these three bugs are related?
nope! this bug is separate as I could replicate it with ulimit -Hn set in rc.conf to 1048576. Per https://bugs.winehq.org/show_bug.cgi?id=56250#c3, Brendan McGrath wanted to report that bug, but it was never done as far as I know. (In reply to kolAflash from comment #2)
I understood these other bug reports in a way, that only the hard limit on open files (-Hn) is relevant. Correct? yes! raising ulimit -Hn solves this, having a ulimit -Hn of 4096 while not having ntsync loaded also fixes this
I understood you in a way, that you're using the default hard limit by Gentoo? If yes, Gentoo maybe choose the limit a bit low. So you may ask Gentoo to raise the default limit. Or if Gentoo doesn't explicitly sets a limit, from which upstream component the limit is inherited - maybe Bash or the Linux kernel. I'm using the default gentoo limit, I'll try to file an issue with them or maybe change the gentoo wiki so that it is clearer that using ntsync means that you have to raise your ulimit -Hn
The only thing I guess Wine could do, is to offer a better mechanism to notify the user if the limit has been hit.
Mostly to document things properly: Can you check which hard limit is roughly needed (2^x) to make things work?
I can try, but I believe that Zebediah Figura's guidance on the issue is sufficient. Especially since the default Debian/Fedora limit is 1048576/2 https://github.com/ValveSoftware/wine/blob/b8fdff8e1f855b5276ec4ddca0f31b279... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.