libapache-mod-ssl and debian's apachectl script

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all.

I'm back with yet another question, your indulgence please. 

Under slackware, when the mod_ssl package is installed,
/usr/sbin/apachectl is replaced with a script specifically modified
for ssl, which supports the starttls option. I noticed however, that
when I installed libapache-mod-ssl under debian, the old apachectl
script included in the apache package was not modified or
replaced. So, I edited the apachectl script under debian, to start the
apache daemons with the "-DSSL" flag, which did result in apache's
listening, and talking ssl on port 443. However, when apache got
upgraded during a recent dist-upgrade, the apachectl script was
replaced again, and my modification was lost. Again, if the script is
not changed, apache doesn't listen on port 443. However, if I again
modify the script to startup the daemons with the "-DSSL" flag, ssl
works just fine again.

Since I don't want to have to modify the apachectl script every time
apache gets upgraded, can someone please enlighten me as to how apache
with ssl support should be started in debian? As I imply above, my
httpd.conf/mod_ssl.conf configuration is fine, and yes, there is a
listen 443 directive in addition to the standard listen 80 directive,
it's just the lack of the -DSSL flag during startup that seems to be
the problem it seems.

As always, thanks in advance for any help, and thanks to those who
have put up with me so far.

Greg


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager at EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD4DBQFDLHPf7s9z/XlyUyARAs++AJ9MbJqXqXXL0RoPd5yE9nW30EGWjQCYs6cW
JEbHdpxeDzQGxjSKxD3YzA==
=rCu8
-----END PGP SIGNATURE-----