On May 27, 2010, at 1:04 PM, Perrin Harkins wrote:
On Thu, May 27, 2010 at 11:11 AM, Michael Schout
wrote:
My solution involved forking off a watcher process when the server
starts up.
Wouldn't it be simpler to start a separate daemon for this? You could
launch it from apachectl if you do
Curiously, I have been using Apache::Reload a lot lately and it has
been working really well most of the time.
I'm wondering if maybe another way to deal with troublesome module
reloads is to subclass Apache::Reload and override the reload process
for those specific namespaces.
On Thu, May 27, 20
On 05/27/2010 03:04 PM, Perrin Harkins wrote:
> On Thu, May 27, 2010 at 11:11 AM, Michael Schout wrote:
>> My solution involved forking off a watcher process when the server
>> starts up.
>
> Wouldn't it be simpler to start a separate daemon for this?
The project this is for has apache's sandbox
Fred,
Yes, mod_perl and mod_proxy are on the same httpd.
Perrin,
For clarification, I'm using sections to create the config from info
stored in various databases but mod_rewrite and mod_proxy are doing the real
work. There are no Perl Handlers.
I think I will try writing out the config and see
On Thursday 27 May 2010 21:36:01 Joshua Johnson wrote:
> Related: and would it be possible to add config on-the-fly?
> $r->add_config() Won't let you add VirtualHosts because it operates as
> though in a directive.
>
I do most of the request config with $r->add_config(). The httpd.conf contains
On Thu, May 27, 2010 at 11:11 AM, Michael Schout wrote:
> My solution involved forking off a watcher process when the server
> starts up.
Wouldn't it be simpler to start a separate daemon for this? You could
launch it from apachectl if you don't want to run another command.
- Perrin
I second what Fred said. Also, you might consider just generating a
config file for apache with perl and not running mod_perl in the
server. I try to avoid using mod_perl for things that mod_rewrite and
mod_proxy can handle.
- Perrin
On Thu, May 27, 2010 at 3:39 PM, Fred Moyer wrote:
> It soun
It sounds like you are using mod_perl and mod_proxy on the same main
httpd, is that right?
If so, consider running another front end proxy such as apache with
the event_mpm, perlbal, ha_proxy, or nginx. Without having more
details (Devel::NYT::Prof may provide some), my guess is that you are
bloc
Hello all,
I have a question on using mod_perl to configure apache for many virtual
hosts. My problem is the high load on the apache server. I decided to go
with mod_perl to configure apache and here are the reasons (if I should be
doing this a different way, please say so. I'm open to suggestions
Hello,
I'm building ancient versions of apache and mod_perl (with perl 5.8.9)
in the following way:
tar zxf apache_1.3.41.tar.gz
cd apache_1.3.41
./configure --prefix=/APACHE-PREFIX --enable-module=so
--enable-module=access (... more --enable-module) \
--disable-module=imap --disable-module=use
On 09/11/2009 04:26 PM, Jonathan Swartz wrote:
> I'm thinking about an improved solution to recognizing module changes in
> a running server, without restarting the server.
This thread is quite old, but it inspired me to implement a similar
strategy for dealing with module changes under mod_perl.
11 matches
Mail list logo
