Written documentation rarely matches the version and environment you are running in. I suspect your plan was doomed from the start.
I make backup copies of configurations suffixed by the date (and if necessary a serial number). When I try something, I can easily get back to a version that worked. When I am content with a configuration, a "diff" of the two files and a few short notes does wonders later. Webmin almost works and if you follow the step above, leads to a fairly efficient tool for manipulating apache behavior. For the most part, the packagers put together a fairly rational set of options. I remember when apache/php/mysql did not work out of the box.. Now with maybe a tweak or two, servers work great almost out of the box. But... Systems don't work. When they appear to work, it is because they are based on an earlier system which also appeared to work but really didn't work either. Jim Tarvid On Tuesday 17 December 2002 09:07 pm, you wrote: > I installed apache as part of an 8.2 Mandrake install. Everything about > the install went great and when I configured my router and a DNS server (on > another box), I was able to see the default web page on the server. > > I wanted to learn something about the application so I bought the O'Reilly > book and started working through it. My plan was to use "apachectl stop" > to stop the conf that was set up by Mandrake, create my own conf using > O'Reilly exercises in the book and test the exercises by starting the test > confs using "httpd -f /usr/www/site.first/conf/httpd.conf -d > /usr/www/site.first/htdocs". Is there anything fundamentally wrong with > this plan? > > Everything worked for a couple of exercises but now, a couple of weeks > later, I'm having trouble getting anything to work. Was there something > setup during the installation/compile that prohibits is keeping it from > working using the steps above? > > Thanks for any help in advance. Carter
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
