[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-hackers-public] Re: *

From: Sylvain Beucler
Subject: [Savannah-hackers-public] Re: *
Date: Sun, 21 Aug 2005 12:13:07 +0200
User-agent: Mutt/1.5.9i


Maybe we can switch to a regenerated set of <VirtualHost>s. Since
Apache can be told to reload the configuration without closing
existing connections, I don't think that would impact the
service. I'll try to make some tests about reloading 2400 virtual

Symlinks could be created at 'cvs update' time as well, reducing the
complexity of the rewrite rules.

Out of curiosity, could you tell me why only 'cvs' caused troubles?


On Sat, Aug 20, 2005 at 07:10:48PM -0400, Justin Baugh wrote:
> Sylvain,
> After many hours of working, I still cannot solve this problem. In fact,
> it has illustrated a larger problem with the tangled configuration
> relating .symlinks and how they are interpreted, and the fact that
><whatever> uses the same .symlinks
> configuration, which causes a lot of problems.
> I will need at least a few days to look at this and come up with a way
> to fix the problem. In the meantime, I put in a workaround for cvs.
> There are only a handful of projects that use .symlinks to link
> something like index.html to <project>.html, so I don't think this is so
> bad.
> The basic problem is that there are many rewrite / redirect sets that
> interact with each other strangely, and when you throw * into
> the mix, it breaks the existing (difficult to understand) configuration.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]