Well, just have to mention one problem I encountered, to help others avoid it. I said that the installation program seemed to read all my old configuration stuff and put it into the new configuration directory. Fine.
But, the instructions said to start up with apachectl, which I did. Everything seemed to work fine until I tried to log in from work. My password protection scheme with cgi scripts stopped working. I got all kinds of errors, permissions denied, odd prefixes added onto the path of my scripts, etc. Nothing I did seemed to help much. I finally discovered there was an old version of apachectl lying around my system, God only knows from where, since I wasn't using it to start apache before. It was pointing to some non-existent or old configuration file. I removed it, now, all it fine. Geez. A lot of aggravation over a newbie mistake. Blush. Joel Oe Sun, Jun 01, 2003 at 06:01:42PM -0400, Joel Hammer wrote: > Just to share a good experience. > > I decided to put my web page back on line to share some wedding pictures. > > So, I thought I better install the latest version of apache, for seurity > reasons. So,I got the latest version of apache, ran the three minute > configuration approach (decide where to put it. I took their suggestion), > compiled it and installed it, and voila, everything worked on the > first try. It even found my old settings in /etc/http/conf. Total time > to install was about 5 minutes. > > Now, that was a nice experience, and it wasn't even Debian (Caldera 2.4). > > Now, why can't it always be that easy? > > Joel > > > _______________________________________________ > Linux-users mailing list > [EMAIL PROTECTED] > Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users _______________________________________________ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
