At 7:01 AM -0500 11/07/1998, [EMAIL PROTECTED] wrote:
>When it took you longer I guess you started from scratch with your old
>configuration and not with the pre-configured httpd.conf file. Because when
>you install Apache+mod_ssl via APACI you get an already pre-configured
>httpd.conf file where all SSL directives are present and setup correctly.
Thanks! I may go back to APACI now that I've more confidence with all this.
FYI I did begin with APACI (that's why there are so many certs lying
around) but bailed out because I couldn't figure out how to maintain my
other extensions that way (eperl, mysql, etc).
Also I'm confused by the fact that APACI (seems to) put everything in
different places (etc vs conf) than when using the old src technique (where
everything winds up in conf). So could someone explain...
1) Why two etc and conf directories when one conf directory might suffice?
2) Why does APACI use one and src/make the other? Is this documented anywhere?
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.
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
