I had a very very similar problem.
ns_param maxthreads 5
ns_param minthreads 5
with minthreads 0, (and sometimes 1 or 2) it exhibited the same
behavior.
On Mon, 2004-05-03 at 02:02, Bart Teeuwisse wrote:
> Notice: prebind: bound: 192.168.1.2:80
> Notice: prebind: bound: 192.1
I've been staring at this problem for a while now and can't seem to place my
finger on it.
I've compiled nsopenssl 3.x (CVS HEAD) against OpenSSL 0.9.7d, loading
nsopenssl in AOLserver 4.0 r3 appears to go flawless. Except for a OpenSSL
memory callback warning. The port nsopenssl listens to (443)
On 2004.05.02, Andrew Piskorski <[EMAIL PROTECTED]> wrote:
> On Sun, May 02, 2004 at 06:22:14PM +0200, Bernd Eidenschink wrote:
>
> > lsof -p
>
> And another good way seems to be:
>
> cat /proc/$NSD_PID/maps | grep ssl
Oh, see, that'll teach me to reply to a message without reading all the
replie
On 2004.05.02, Andrew Piskorski <[EMAIL PROTECTED]> wrote:
> Under Linux, is there some more general way to answer the question,
> "Exactly what shared libraries is this running process actually
> using?" Some command line tool, or a particular thing to check under
> gdb? Or some C function which
On Sun, May 02, 2004 at 06:22:14PM +0200, Bernd Eidenschink wrote:
> lsof -p
And another good way seems to be:
cat /proc/$NSD_PID/maps | grep ssl
--
Andrew Piskorski <[EMAIL PROTECTED]>
http://www.piskorski.com/
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, sim
On Sun, May 02, 2004 at 06:22:14PM +0200, Bernd Eidenschink wrote:
> lsof | grep nsd
> lsof -p
Ah, very nice, that gives the full path the OpenSSL lib actually being
used. Thanks, Bernd.
--
Andrew Piskorski <[EMAIL PROTECTED]>
http://www.piskorski.com/
--
AOLserver - http://www.aolserver.com
Hi Andrew,
> Under Linux, is there some more general way to answer the question,
> "Exactly what shared libraries is this running process actually
> using?" Some command line tool, or a particular thing to check under
> gdb? Or some C function which I could call from inside AOLserver
> itself?
I have multiple versions of the OpenSSL libraries installed on a Linux
box. Now, I know which OpenSSL library I'm TELLING nsopenssl to use,
but I would really like a way to verify, at run time, precisely which
OpenSSL library AOLserver and nsopenssl are actually using.
(Especially since cutting ov
