On Sat, 28 Oct 2000, Dan Kegel wrote:
> I'm writing a server that will often have more than 1024
> file descriptors open. That means that any code using
> stdio might fail, since stdio.h can't handle any
> fd's higher than 1024 on some systems.
That only gives you a limit *per-process*. :-)
> I might be able to get by, since I currently don't think
> I call any OpenSSL functions that use stdio after startup,
> but it's a bit worrying.
>
> At some point, we might need to provide alternate implementations
> of the parts of OpenSSL that currently use stdio...
> has this issue been discussed before?
Not that I recall, but please do. I'm curious how wide-spread the need for
programs are that run more than 1024 file descriptors and can't spread
them across processes (usually at those volumes you end up forking from a
master process that holds open IPC connections to the "children"). I'm
particularly curious if these apps are also doing SSL (which is usually
*way* too fat and blocky to want to cram that much into a single process).
Anyway, in principle, I can't see why this would be a big obstacle to
using a non-stdio interface - you should just need to create alternative
BIOs (or BIO_METHODs, more to the point). Mind you, I've never felt the
need to do that nor even use the network-aware BIOs at all myself, so I
take what I say with a dose of salt. Have you tried doing this yet?
Cheers,
Geoff
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
