Thanks again, Ralf. Very helpful!
One final suggestion. Using APACI might not seem so difficult to newcomers if we could
be supplied with a script or data file to edit with instructions like "uncomment the
lines you want to enable." Uncommenting lines in a file is easier because the file
serves as an automatic memory for what has been tried already.
./configure
# --compat # if you want the server config files in apache/conf. Default:
apache/etc
# --foo=bar # and so forth...
The current approach, instructions on how to manually type a command line leads to
memory lapses and misunderstanding. Certainly did in my case since the supplied
instructions for (mod_ssl + mod_perl) vs (php + mysql) didn't match my needs (mod_ssl
+ mod_perl + mysql + embperl + ...), triggering this whole saga.
At 9:15 AM -0500 11/07/1998, [EMAIL PROTECTED] wrote:
>> 3) Is there an automated way to record the APACI command line that was used
>> to generate the current running system so that new stuff can be added
>> incrementally instead of each time starting from scratch? Something
>> comparable to uncommenting lines in src/Configuration, which nicely suits
>> my (ever-failing) memory ability.
>
>A config.status file is automatically generated for you.
------------------------------------------------
Brad Cox; George Mason University; 703 361 4751; [EMAIL PROTECTED]
http://www.virtualschool.edu/mon A Project with Paradoxical Goals
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
