From charset="iso-8859-1" Received: (qmail 12519 invoked from network); 20 Jun 1998 06:03:51 -0000 Message-Id: <000101bd9c11$12755b60$24ae44c6@iopc.cts.com> Date: Fri, 19 Jun 1998 23:02:57 -0700 From: "Morgan Davis" To: "Bill Blue" Cc: "Rodent of Unusual Size" , In-Reply-To: <199806200532.WAA19229@mh2.cts.com> Subject: RE: Apache Release 1.3.0 on FreeBSD 2.2.5 >Number: 2476 >Category: other >Synopsis: RE: Apache Release 1.3.0 on FreeBSD 2.2.5 >Confidential: yes >Severity: serious >Priority: medium >Responsible: coar >State: closed >Class: mistaken >Submitter-Id: unknown >Arrival-Date: Fri Jun 19 23:10:01 PDT 1998 >Last-Modified: Fri Jun 26 04:21:10 PDT 1998 >Originator: >Organization: >Release: >Environment: >Description: >How-To-Repeat: >Fix: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: coar State-Changed-When: Fri Jun 26 04:21:10 PDT 1998 State-Changed-Why: This has no business in the bugdb.. Class-Changed-From-To: sw-bug-mistaken Class-Changed-By: coar Class-Changed-When: Fri Jun 26 04:21:10 PDT 1998 Responsible-Changed-From-To: gnats-admin-coar Responsible-Changed-By: coar Responsible-Changed-When: Fri Jun 26 04:21:10 PDT 1998 Responsible-Changed-Why: Bogus message. Category-Changed-From-To: pending-other Category-Changed-By: coar Category-Changed-When: Fri Jun 26 04:21:10 PDT 1998 >Unformatted: > From: Bill Blue [mailto:bblue@cts.com] > Comments on this? totally is a server of ours that they colocate > and rent, > and they have lots of traffic. Not sure why he wanted to update what was > there... > > --Bill Yes, there appears to be some kind of problem with Apache 1.3x on FreeBSD. We had the same problems with the 1.3b7 release back in November, and we reverted to 1.3a13. I had submitted a couple of bug reports, and sent a bunch of e-mail with one of the Apache people. They're responsiveness was really good, but nothing seemed to solve the problem. When we found out that it was a major pain to install FrontPage support into 1.3x, we went back even farther to the 1.2.6 release (which was the last "official" release version before 1.3.0 came out just recently). We've had no problems since. We're likely to stay with 1.2.6 for the foreseeable future because we need FrontPage and SSL -- no odd duck by any stretch, but that does not appear to be getting much support. (See note from Apache's Ken Coar at bottom). My comment to him was to have hooks in the Apache sources that could be activated at compile time to link into a set of additional export-controlled sources (or libraries), distributed by a third party, to facilitate SSL. They could do this without breaking any export laws, because there's nothing illegal about these bytes of source: #ifdef SSL some_ssl_api_function(); #endif The same could be done for FrontPage. Oh well. --Morgan > >From: "M. D. Parker" > >Subject: Apache Release 1.3.0 on FreeBSD 2.2.5 > >To: bblue@cts.com, dcruz@wserver.allnaked.com (Allnaked and > Other Websites) > >Date: Fri, 19 Jun 1998 21:42:24 -0700 (PDT) > >Reply-To: mdpc@netcom.com > >X-Snail-Mail: P. O. Box 2558 / Vista / CA / 92085-2558 > >X-Phone-Number: +1 760 598 4793 > >X-Mailer: ELM [version 2.4 PL25] > > > >Bill, > > > >So far for the past couple of weeks, the 1.3.0 release of > >the apache web server has been running on server1 (aka totally). > >So far since experience has been that the thing has died > >leaving processes consumming lots of time with no activity > >for the outside user. > > > >I'm advising you of what I have found and wonder if you have > discovered the > >same and anyy workarounds or fixes. I have reverted to 1.3b7 > >as a result and will wait for 1.3.1 to come out (rumored > >in just a few days). > > > >Mike > > Morgan Davis wrote: > > Since the problems with 1.3b3, we had to revert to 1.2.6. I've not > had time to try 1.3bX since then. At the first chance I get, I'll > look at 1.3b7. Hopefully, it has official hooks in place for > supporting stuff like FrontPage and SSLeay. Don't bother with 1.3b7; 1.3.0 is officially released and out. As for official hooks.. no, sorry. FrontPage might be easier to hook in (I remember discussions about it in the last few months, but I don't use it and hence didn't pay attention to the details). The SSLeay stuff, though - that's a sticky wicket because of the U.S. arms restrictions. Nothing official's been done there, although Ben probably has something new and improved from before. Please reply to this message (*don't* forget to Cc the apbugs address!) when you've had a chance to try out 1.3.0. You could always try running it in parallel with your production server, just on different ports (e.g., 8087 instead of 80). > > [In order for any reply to be added to the PR database, ] > > [you need to include in the Cc line ] > > [and leave the subject line UNCHANGED. This is not done] > > [automatically because of the potential for mail loops. ] #ken P-)} Ken Coar Apache Group member "Apache Server for Dummies"