Bug#505894: apache2-mpm-prefork: Default ports.conf contains VirtualHost that may conflict with current configuration

To: Thomas R Bailey <siggma@trbailey.net>
Cc: 505894@bugs.debian.org
Subject: Bug#505894: apache2-mpm-prefork: Default ports.conf contains VirtualHost that may conflict with current configuration
From: Stefan Fritsch <sf@sfritsch.de>
Date: Mon, 17 Nov 2008 21:21:17 +0100
Message-id: <[🔎] 200811172121.17857.sf@sfritsch.de>
Reply-to: Stefan Fritsch <sf@sfritsch.de>, 505894@bugs.debian.org
In-reply-to: <[🔎] 20081116164309.19075.47521.reportbug@moya>
References: <[🔎] 20081116164309.19075.47521.reportbug@moya>

On Sunday 16 November 2008, Thomas R Bailey wrote:
> The latest update for Apache2 causes Virtualhost warning messages
> when starting or stopping apache2 using init.d script. This appears
> to be caused by including virtualhost definitions in ports.conf.


Please read /usr/share/doc/apache2.2-common/NEWS.Debian.gz . Does this 
help or do you need more information?

Reply to:

References:
- Bug#505894: apache2-mpm-prefork: Default ports.conf contains VirtualHost that may conflict with current configuration
  - From: Thomas R Bailey <siggma@trbailey.net>

Prev by Date: Bug#505894: apache2-mpm-prefork: Default ports.conf contains VirtualHost that may conflict with current configuration
Next by Date: Bug#506060: The DocumentRoot should be specified without a trailing slash.
Previous by thread: Bug#505894: apache2-mpm-prefork: Default ports.conf contains VirtualHost that may conflict with current configuration
Next by thread: Bug#505894: marked as done (apache2-mpm-prefork: Default ports.conf contains VirtualHost that may conflict with current configuration)
Index(es):
- Date
- Thread