www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "G. Roderick Singleton" <ge...@pathinc.net>
Subject RE: general/3063: Virtual host set-up impossible with existing docs
Date Thu, 19 Nov 1998 16:04:23 GMT
I have yet to get multiple httpd's up and running.  I think this results
from each new httpd seeing a running copy and subsequently not starting.  I
have not found a solution as yet.  Off-line conversations with various
support people did not lead to a working solution.

Please keep the ticket open until February 1st 1999.  On that date close it


> -----Original Message-----
> From: lars@apache.org [mailto:lars@apache.org]
> Sent: Saturday, November 14, 1998 12:33 PM
> To: apache-bugdb@apache.org; gerry@pathinc.net; lars@apache.org
> Subject: Re: general/3063: Virutal host setup impossible with existing
> docs
> [In order for any reply to be added to the PR database, ]
> [you need to include <apbugs@Apache.Org> in the Cc line ]
> [and leave the subject line UNCHANGED.  This is not done]
> [automatically because of the potential for mail loops. ]
> [If you do not include this Cc, your reply may be ig-   ]
> [nored unless you are responding to an explicit request ]
> [from a developer.                                      ]
> [Reply only with text; DO NOT SEND ATTACHMENTS!         ]
> Synopsis: Virutal host setup impossible with existing docs
> Comment-Added-By: lars
> Comment-Added-When: Sat Nov 14 09:32:49 PST 1998
> Comment-Added:
> [This is a standard response.]
> This Apache problem report has not been updated recently.
> Please reply to this message if you have any additional
> information about this issue, or if you have answers to
> any questions that have been posed to you.  If there are
> no outstanding questions, please consider this a request
> to try to reproduce the problem with the latest software
> release, if one has been made since last contact.  If we
> don't hear from you, this report will be closed.
> If you have information to add, BE SURE to reply to this
> message and include the apbugs@Apache.Org address so it
> will be attached to the problem report!

View raw message