Date: Sun, 31 Mar 1996 12:02:33 -0500 (EST) From: Steve Hovey <root@buffnet.net> To: "Bryan Ogawa at Work" <bogawa@netvoyage.net> Cc: dwhite@resnet.uoregon.edu, Steve <shovey@buffnet.net>, freebsd-questions@freebsd.org Subject: Re: Apache still and timeouts Message-ID: <Pine.SCO.3.91.960331120144.3724E-100000@buffnet1.buffnet.net> In-Reply-To: <Pine.NEB.3.92.960329121302.1474F-100000@digital.netvoyage.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 29 Mar 1996, Bryan Ogawa at Work wrote: > On Thu, 28 Mar 1996, Doug White wrote: > > > On Thu, 28 Mar 1996, Steve wrote: > > > > > > > > Im still having apache troubles (1.0.0) under freebsd 2.1R and I now > > > think it has to do with timeouts under apache. > > > > Try 1.0.3. New port should be in ports-current. > > > > Have it on a 2.1R box and it is running great. > > I've run it (quick tests ONLY -- we use NCSA 1.5, which I'm running now on > our 2.0.5R machine) with few problems (actually, fewer problems w/ Apache > than NCSA). The only reason I'm still running NCSA is due to minor > incompatibilities between them (and we're kinda planning on switching > everything all at once). > > One thing that I read somewhere (on this list, perhaps) is that setting : > > DNSMode Minimum Thanx but it turned out to be a problem with freebsd TCPIP - by placing my web servers on a different subnet from my users, so that the packets go thru my cisco, my problem was solved.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SCO.3.91.960331120144.3724E-100000>