"Ralf S. Engelschall" wrote:
> When you aren't familiar with the good old "poor man's" way, why do you use
> it? But ok, when you use it you usually copy src/Configuration.tmpl to
> src/Configuration. And then you edit it.
Aaah, there was my problem. I'd already installed a non-ssl apache while waiting
for help on ssl, being impatient and all and was already editing Configuration
rather than Configuration.tmpl. Doh.
> . But when you're not familiar with
> the old configuration method, just don't use it ;-) The "Joe Average" method
> should be more easy for you...
I'va actually done several installs using the "old" method and normally with Ben
Lauries patches :-). However since you so stridently advocate the new method in
your docs and being one of Apaches core developers I thought I'd give you my opinion
on Apache's "new" way. I find it a huge pain in the butt!
I like to have control over the modules included and a relaxing stroll through a
text file commenting out appropiate lines seems a lot easier than specifying on the
command line arcane --options-whatever=yada. Especially as I'd be jumping between
terminals to be reading in another file presumable the name of each module and what
it does. And when next week I decide to add the php module I'd have to type it all
in again! I don't know if I've missed something vital here or if I'm just lazy but
it seems like a giant step backwards to me. To me a well-documented configuration
file is as good as it gets. Better than a GUI even because they have a tendency to
make you guess what your options are rather than giving an explanation for each
point.
Regards,
--Steve
ps. Just to make this even slightly on-topic congrats on the demo httpd.conf and
srm.conf that comes with mod_ssl. *Much* better than the apache-ssl equivalent.
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
