On Sat, Oct 28, 2000 at 06:24:32PM -0700, 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.
I don't know any which
From: Rich Salz [EMAIL PROTECTED]
rsalz There are some popular operating systems that don't let you do
rsalz FILE* fp = fdopen(getdtablesize(), "r")
rsalz :) Those are buggy C libraries -- even Sun has said it's a bug, just
rsalz that they weren't going to fix it.
The above line strikes
The above line strikes me as a typical fence-post error on the
part of the application author.
No. Some Solaris, for example, use a char (not even unsigned char!) to
store the file descriptor in their FILE structure (E.g., what KT (1st
ed.) shows as "int _fd" on page 165.
Can it be
I do still think Ben is trusting select a bit too much; real servers
that must avoid blocking really do set sockets to nonblocking mode
just in case.
- Dan
Not only just in case. Real operating systems will block when you don't
expect them to. FreeBSD, for example, can block on a
Try VC-NT for your configuration. Works much better for me.
-Original Message-
From: Tim Miranda [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 30, 2000 3:31 PM
To: [EMAIL PROTECTED]
Subject: problem compiling 0.9.6 on WinNT 4
Hi-
I'm having a problem compiling openssl 0.9.6
on
From: Rich Salz [EMAIL PROTECTED]
Subject: Re: Problem with 1024 file descriptors
Date: Mon, 30 Oct 2000 13:48:44 -0500
Message-ID: [EMAIL PROTECTED]
rsalz The above line strikes me as a typical fence-post error on the
rsalz part of the application author.
rsalz
rsalz No. Some
From: frank mori hess [EMAIL PROTECTED]
fmhess I got a compiler warning while compiling version 0.9.6 which
fmhess led me to locate a bug in the dgst.c file. On line 227, there
fmhess is a comparision
fmhess
fmhess if(out_bin == -1)
fmhess
fmhess where out_bin is a variable of type char.
Richard Levitte - VMS Whacker wrote:
rsalz Also, have you looked at bio/bss_fd.c?
rsalz
rsalz Sure, but the issue is what OpenSSL uses interally, as I hope
rsalz my example showed.
Oh, absolutely. What I wanted to point out is that there is a BIO
that uses file descriptors, which
Oh, absolutely. What I wanted to point out is that there is a BIO
that uses file descriptors, which makes the need for a flag to
bss_file.c completely needless and one complication too many. To
solve said problem, one should use the file descriptor BIO instead of
the stream BIO...
Except
IMHO we should ideally have console and file I/O all handled by BIOs in
such a way that any platform specific changes only need to be made in
one place.
Totally agree.
Wouldn't it be neat if all of openssl (except bio-file) could compile w/o
stdio.h? :)
Rich Salz wrote:
IMHO we should ideally have console and file I/O all handled by BIOs in
such a way that any platform specific changes only need to be made in
one place.
Totally agree.
Wouldn't it be neat if all of openssl (except bio-file) could compile w/o
stdio.h? :)
Yes. (On
Matti Aarnio wrote:
On Sat, Oct 28, 2000 at 06:24:32PM -0700, 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.
From: Tim Miranda [EMAIL PROTECTED]
miratim F:\openssl-0.9.6perl util\mkdef.pl 16 libeay
miratim 1ms\libeay16.def
miratim Use of uninitialized value at util\mkdef.pl line 514.
miratim Use of uninitialized value at util\mkdef.pl line 515.
miratim Use of uninitialized value at util\mkdef.pl line
13 matches
Mail list logo
