Bug#366843: apache postinstall script insists of (quietly) setting ServerName (to localhost)
Package: apache
Version: 1.3.33-6sarge1
Severity: grave
When upgrading apache (or dpkg-reconfiguring it), ServerName directive
is set to some value (defaults to `localhost'). Before upgrade the
configuration was perfectly valid, with ServerName taken from hostname
apache is running on. After upgrades, ServerName is set to invalid
'localhost'.
Usually I keep local modifications in another file (httpd.conf.local) -
stuff like MinSpareServers, mod_proxy configs (if any) etc - it's easy
to overwrite those even if set in the default httpd.conf. But I can't
"unset" ServerName which is being forcedly set in httpd.conf.
There's some words about "black magic" in
/usr/share/apache/postinst.common wrt setting ServerName. I probably
can just remove the text postinst.common searches for, to avoid this
issue, but.. that required me about an hour to figure it all out!.. ;)
Why the ServerName is being set in the first place, anyway? Setting it
quietly is bad (hence Severity set to "grave" - it silently brokes valid
configuration), but why to set it at all?
Thanks.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.16-i686
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Versions of packages apache depends on:
ii apache-common 1.3.33-6sarge1 support files for all Apache webse
ii debconf 1.4.30.13 Debian configuration management sy
ii dpkg 1.10.28 Package maintenance system for Deb
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libdb4.2 4.2.52-18 Berkeley v4.2 Database Libraries [
ii libexpat1 1.95.8-3 XML parsing C library - runtime li
ii libmagic1 4.12-1 File type determination library us
ii logrotate 3.7-5 Log rotation utility
ii mime-support 3.28-1 MIME files 'mime.types' & 'mailcap
ii perl 5.8.4-8sarge4 Larry Wall's Practical Extraction
-- debconf information excluded
Reply to: