Yes, it's hardcoded. FD_SETSIZE should be the maximum number of file descriptors you can ever have open. On my Linux box here, FD_SETSIZE is 1024, and I can't ulimit -n any more than this. Cheers, Simon On 27 October 2005 15:18, Joel Reymont wrote:
Actually, I think I was just hitting the top range of FD_SETSIZE, about 8000 on that machine.
Does FD_SETSIZE get hardcoded into ghc-built binaries? That is if I increase the available descriptors per process with uname -n, will it be taken into account?
Thanks, Joel
On Oct 26, 2005, at 10:04 AM, Simon Marlow wrote:
lockFile uses FD_SETSIZE as its idea of the maximum value of a file descriptor. If you can get file descriptors outside this range, then the above error would ensue. Not sure if this is the case on FreeBSD... seems odd if it is. Can you try a truss/ktrace and see the values of your file descriptors?