Follow-up Comment #11, bug #22351 (project gnustep):
"If there is a problem running out of file descriptors, then a fix would be
to use fewer of them"
I agree that what I did is not a perfect solution.
The root of the problem is that the polling in that method for a connection
is causing the process to block because the file descriptors allowed for that
process are quickly used up. This happens because, at least on linux, the
send and receive ports are created by making special files in /tmp.
Riccardo also verified that it's the file descriptors on his NetBSD box by
using the code prior to my change and setting the number of allowed file
descriptors to the maximum.
Giving the server time to come up and register itself means that we'll do
less polling and, thus, use fewer file descriptors.
Nevertheless, it does address the issue on a number of platforms where this
problem was occurring. I suggest we leave the present "hack" in place until a
proper fix is found. GC.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?22351>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep
