nsopenssl 3.0 beta 10 is available on http://scottg.net. Kick the tires.
/s.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of
your
I found out that the problem is not in the saving of the file, but in
the return of the utf-8 file from the filesystem.
I found out that using
ns_returnfile [encoding convertto [encoding system] $filename]
would allow aolserver to find the utf-8 filename from the filesystem and
return the
This is only a problem on AOLserver 4.0 (at least). It works on
AOLserver3.3+ad13.
This leads me to suspect that there might be a charset issue that is in
3.3+ad13 that isn't in 4.0.
Dave
On Thu, Jan 08, 2004 at 03:20:09PM -0500, Dave Bauer wrote:
I found out that the problem is not in the
I was running nsd v.3.4.2 on a fairly active website
(FreeBSD 4.x os) for a few weeks and had some
trouble with the nsd process growing. I was restarting
the process every few days as it grew to 40-60Mb.
I posted a couple messages on this list about
v4.0 and using port 80 as I was trying to run
Forgot to mention that you'll have to get around the fact that
ServerPort is no longer a valid name in the config -- OpenACS will have
an issue with that.
Since you can now have multiple drivers per virtual server, and drivers
for each virtual server, you'll have to figure out a way for OpenACS to
Thanks Scott,
Yes, I am running some small cgi stuff, so that is likely it.
I didn't see a tarball for v3.5.9 on the sourceforge site,
and not being much of a manual CVSer, not sure how I
would checkout v35bp. Would it be:
cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/aolserver
co
Almost -- you need the -r flag to identify the branch:
cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/aolserver login
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/aolserver \
co -r aolserver_v35_bp aolserver
/s.
On Jan 8, 2004, at 6:16 PM, John Shafto wrote:
Thanks Scott,
Yes, I am running
On 2004.01.08, John Shafto [EMAIL PROTECTED] wrote:
I was running nsd v.3.4.2 on a fairly active website
(FreeBSD 4.x os) for a few weeks and had some
trouble with the nsd process growing. I was restarting
the process every few days as it grew to 40-60Mb.
40-60MB is nothing. I'd worry if
There is a good, if inconspicuous, mention of AOLserver in the Feb LJ. On
page 46, in the feature on the Magnatune record label, the statement is made:
Apache 2 running PHP and OpenSSL serves all the HTML pages. When Magnatune
was Slashdotted, I found that Apache could not keep up with the load
On 2004.01.08, Lamar Owen [EMAIL PROTECTED] wrote:
Wow, somebody who really uses the right tool for each job. Apache for the
HTML and PHP stuff, AOLserver for machine-gunning images out, and Mathopd for
serving very large files at high speeds.
I assume that first sentence was dripping with
I was running nsd v.3.4.2 on a fairly active website
(FreeBSD 4.x os) for a few weeks and had some
trouble with the nsd process growing. I was restarting
the process every few days as it grew to 40-60Mb.
40-60MB is nothing. I'd worry if your nsd grows beyond 2GB.
Doing what?
This
On 2004.01.08, John Shafto [EMAIL PROTECTED] wrote:
40-60MB is nothing. I'd worry if your nsd grows beyond 2GB.
Doing what?
Just about anything. If your stacksize is set to, say, 1 MB ... and
you've got 20 threads for handling connections, you're looking at a nsd
footprint of at least 20
On Thu, 2004-01-08 at 21:33, John Shafto wrote:
I was running nsd v.3.4.2 on a fairly active website
(FreeBSD 4.x os) for a few weeks and had some
trouble with the nsd process growing. I was restarting
the process every few days as it grew to 40-60Mb.
40-60MB is nothing. I'd
On Thu, Jan 08, 2004 at 09:15:49PM -0500, Lamar Owen wrote:
There is a good, if inconspicuous, mention of AOLserver in the Feb LJ. On
page 46, in the feature on the Magnatune record label, the statement is made:
Apache 2 running PHP and OpenSSL serves all the HTML pages. When Magnatune
was
[Dossy]
40-60MB is nothing. I'd worry if your nsd grows beyond 2GB.
Doing what?
Just about anything. If your stacksize is set to, say, 1 MB ... and
you've got 20 threads for handling connections, you're looking at a nsd
footprint of at least 20 MB. 40-60 MB is very reasonable for a
15 matches
Mail list logo
