On 6/1/2010 4:39 AM, Andrew Godziuk wrote:
>
> I'm wondering if it's possible for an Apache module to change global
> config structures.
If you don't do this during startup, beware. You are exploding memory by
taking what were copy-on-write shadow pages of the original parent process,
and mungin
On Tue, Jun 1, 2010 at 11:39, Andrew Godziuk wrote:
> What I want to achieve is injecting new vhosts without Apache restart.
> Of course I'm aware that the changes would fully take effect after all
> workers have recycled, but for me - it's still better than a restart.
Andrew, wouldn't you be bet
On Tue, Jun 1, 2010 at 11:47 AM, William A. Rowe Jr.
wrote:
> If you don't do this during startup, beware. You are exploding memory by
> taking what were copy-on-write shadow pages of the original parent process,
> and munging X copies where X is the number of worker processes you have.
> And if
On Tue, Jun 1, 2010 at 11:51 AM, Ben Noordhuis wrote:
> Andrew, wouldn't you be better off with something like
> mod_vhost_alias, as-is or as leitmotiv? Propagating configuration
> changes to all workers is rather difficult, especially with pre-fork
> MPMs.
Unfortunately, I need some suexec mech
On 1 Jun 2010, at 10:39, Andrew Godziuk wrote:
> I'm wondering if it's possible for an Apache module to change global
> config structures.
Basically, no, not without a restart. Though there are some aspects of
configuration you can change on the fly.
> What I want to achieve is injecting new v
