On Wed, 14 Oct 2009, Oswald Buddenhagen wrote:
i'm sure there is a way to influence the limit, possibly as simple as #defining __FD_SETSIZE before including sys/types.h (of course, finding that out experimentally is *way* simpler than actually reading the glibc sources :D).
I looked for something obvious, but didn't find any. The definitions of __FD_SETSIZE seem to be wired without #ifndef, and are used at once.
Has anyone actually looked at the Linux include files that I identified, and worked through how it goes in order to determine how to set a higher value?
Or even better, has anyone actually thought of asking the maintainers of glibc to fix their broken software? That would fix it for EVERYTHING, instead of kludging every single package to work around this glibc bug.
For crying out loud, if you people want everything done for you without having to do any work by yourself, then you should be using Microsoft products and not open source.
-- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list [email protected] http://mailman2.u.washington.edu/mailman/listinfo/imap-uw
