Re: Where is default Loaded Modules configuration ???

Michael D Schleif wrote: When I goto: I get a list of loaded modules. [...] Here is an example that confuses me. Without any PerlRequire, I find this is already loaded: Package Version Modified File CGI 3.00Sat Nov 15 02:07:41

Re: Where is default Loaded Modules configuration ???

Michael D Schleif <[EMAIL PROTECTED]> [2003:12:17:22:37:36-0600] scribed: > I am running Debian: > ># COLUMNS=120 dpkg -l '*apache*' | grep ^i | cut -c 1-50 >ii apache 1.3.29.0.1-2 >ii apache-common1.3.29.0.1-2 >ii apache-utils

Re: [mp2] Apache::Cookie

Joe Schaefer <[EMAIL PROTECTED]> writes: > It looks to me like there may be a problem in apreq_cookie.c > (it may not be computing the "expires" date correctly for Netscape > cookies). Which version of libapr are you using? If you're using the latest libapr, this patch to libapreq2 should fix t

Where is default Loaded Modules configuration ???

I am running Debian: # COLUMNS=120 dpkg -l '*apache*' | grep ^i | cut -c 1-50 ii apache 1.3.29.0.1-2 ii apache-common1.3.29.0.1-2 ii apache-utils 1.3.29.0.1-2 ii libapache-mod-jk 3.3a-4woody1

Re: introducing new code with no perceived user delays?

justin wrote: [...] by the way, is modperl2 on apache2 quite ok for heavy production use by now? As long as you test your applications before you upgrade your production server, chances are that you will be just fine. If not, let us know what are the problems and we will fix them. You will want

Re: introducing new code with no perceived user delays?

Rob Nagler wrote: Brian Hirt writes: Once everything is running on the new mod perl, i shut down the original mod perl application. There is about 0.5 seconds of lag while the proxy reloads the rules. We use proxies, but instead of modifying the proxy config, we use a Rewrite rule of the form

Re: introducing new code with no perceived user delays?

Brian Hirt writes: > Once everything is running on the > new mod perl, i shut down the original mod perl application. There is > about 0.5 seconds of lag while the proxy reloads the rules. We use proxies, but instead of modifying the proxy config, we use a Rewrite rule of the form: Rewrite

Re[2]: introducing new code with no perceived user delays?

Well what I do, for some reason I can't remember, is to preload everything (all CPAN etc modules) *except* dev code, in startup.pl Then the children end up loading dev code on the first request and getting fatter .. I might be wrong but most of my VM usage after 10 minutes heavy running appears

Re: introducing new code with no perceived user delays?

justin wrote: [...] SB> Second, you could write a similar to Apache::SizeLimit handler module, which SB> will determine when to terminate the process, but the problem is that you need SB> to reload the parent server anyway if you don't rely on Apache::Reload. Penny drops -- I can do this in my o

Re[2]: introducing new code with no perceived user delays?

SB> What you want to do is to shutdown servers if some timestamp file SB> has changed, but you want to do it at random. First of all don't you SB> think it's a problem if different servers will run different code SB> sets? Yes, sure, for changes where old and new running at the same time, I would

Re: introducing new code with no perceived user delays?

justin wrote: One registry module checks for a new file before a request starts. Another Registry class does no checking at all. Apache::Reload checks a file on disk before the request, or ALL module timestamps. None of these solutions are satisfactory. If code is rolled out, 10+ modperl processes

Re: introducing new code with no perceived user delays?

The way i do this is having a lightweight apache proxy on port 80. My mod perl application listens on a different port and receives requests from the proxy. When i need to roll out new code, i start up a 2nd mod perl application on a 3rd port, update the rules for the proxy to go to the new

introducing new code with no perceived user delays?

One registry module checks for a new file before a request starts. Another Registry class does no checking at all. Apache::Reload checks a file on disk before the request, or ALL module timestamps. None of these solutions are satisfactory. If code is rolled out, 10+ modperl processes all reloading

Re: Apache::Singleton

On Wed, 17 Dec 2003 09:32:41 -0800 "Chris Ochs" <[EMAIL PROTECTED]> wrote: > I'm just trying to see how Apache::Singleton works. If my code is not > understandable, that's how far off I probably am from knowing how it works.. > That was why I asked if someone had a complete sample. A typical usa

Re: [mp2] libgd (and freetype) problem with ModPerl::Registry

Kaiko Kaur wrote: On Wed, Dec 10, 2003 at 11:05:33AM -0800, Stas Bekman wrote: Kaiko Kaur wrote: [...] I recompiled freetype library and gd library and have result: # ldd /usr/lib/libgd.so libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x4003b000) libfreetype.so.6 => /usr/lib/libfreetype.so.

Re: Perl warn failures

[Kit, next time you start a new thread, make sure you don't reply to one of the existing posts, but start a new one afresh. By replying to an existing post you insert a totally unrelated thread into an existing one, which confuses mail clients and some archive software. Thank you.] Kit DeKat wr

Re: Apache::Cookie->fetch

Paul Flinders wrote: Another porting issue for mod_perl2, admittedly this is a libapreq2 change but it might be worth including in the mod_perl porting documentation as anyone porting an application might well run into it (well, I did) Apache::Cookie->fetch in libapreq2 requires that the request ob

Re: Apache::Singleton

- Original Message - From: "Stas Bekman" <[EMAIL PROTECTED]> To: "Chris Ochs" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, December 17, 2003 10:11 AM Subject: Re: Apache::Singleton > Chris Ochs wrote: > > I'm just trying to see how Apache::Singleton works. If my code is

Re: Apache::Singleton

Chris Ochs wrote: I'm just trying to see how Apache::Singleton works. If my code is not understandable, that's how far off I probably am from knowing how it works.. That was why I asked if someone had a complete sample. BTW, if you have the "Practical mod_perl" book, pages 760-762 (appendix A) ex

Fw: Apache::Singleton

> > > > > I have a hash for the posted cgi variables but > > > that gets cleared out when it's reset anyways, and I have about 30 > global > > > variables that I just set explicitly at the start of the code. > > > > That sounds fine. Eventually you should probably look at turning those > > into

Re: Apache::Singleton

Chris Ochs wrote: Actually I don't think I will use Singleton, it just seems like a lot more work then it's worth for me. It's more useful for handling access to an object, like a Template Toolkit instance for example. I have a hash for the posted cgi variables but that gets cleared out when it's

Re: Apache::Singleton

I'm just trying to see how Apache::Singleton works. If my code is not understandable, that's how far off I probably am from knowing how it works.. That was why I asked if someone had a complete sample. Actually I don't think I will use Singleton, it just seems like a lot more work then it's worth

Re: Perl warn failures

Hello again, On Wed, 17 Dec 2003, Kit DeKat wrote: > >Are you using mod_perl? > > yes i am, i have perl environments defined in the conf file and various other > factors that are identical between all servers as well. Please read http://perl.apache.org/maillist/email-etiquette.html and please

Re: [mp2] Apache::Cookie

"Swen Schillig" <[EMAIL PROTECTED]> writes: > Hi * > > I have a problem with Apache::Cookie setting the > expiration value correctly. > Meaning whatever I specify, the default value is used instead ( which > is now or -1) ! [...] > Am I doing something wrong or is this a known bug ?? Bug, prev

Re: Apache::Singleton

Chris Ochs wrote: Here is the code that I cant' get working, maybe it is easier to just correct what I have so far... I'm afraid I can't tell what you're trying to do here. One big problem with this code is that you're putting the request object ($r, by convention) into a global. Don't do that

Re: Perl warn failures

Hi there, On Wed, 17 Dec 2003, Kit DeKat wrote: > The old app-server was R7.3/P5.6.1/A1.3.23 (Redhat/Perl/Apache versions) > and through CVS migrated to a the new app-server, which is > R9.0/P5.8.0/A2.0.48 and afterwards our scripts starting > freezing/timeouts/partial data retrieval. H.

Perl warn failures

Summary: Perl pages 'lock up' silently on R9.0/P5.8.0/A2.0.48 with NameVirtualHosts and unique error_log's for each project name. The 'lock up' appears at warn statements, but only after many calls to warn. If the scripts or loops are small, they work and warn message are seen, but if there are

Re: [mp2] Apache::Cookie

Hi * I have a problem with Apache::Cookie setting the expiration value correctly. Meaning whatever I specify, the default value is used instead ( which is now or -1) ! The other paramters (like path) are set correctly ! The same syntax works just fine with CGI::Cookie (ok, beside the $r object) m

Re: Problems with Multiple PerlTransHandlers

On Tue, 16 Dec 2003 11:55:38 -0500, Patrick LeBoutillier wrote: > What is happening is even if one handler returns OK, the other ones are > still invoked. > > I was able to get around this by creating a meta handler as such: > > PerlTransHandlerApache::ASP::MetaTransHandler >

Re: [mp2] libgd (and freetype) problem with ModPerl::Registry

On Wed, Dec 10, 2003 at 11:05:33AM -0800, Stas Bekman wrote: > Kaiko Kaur wrote: > [...] > >I recompiled freetype library and gd library and have result: > ># ldd /usr/lib/libgd.so > >libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x4003b000) > >libfreetype.so.6 => /usr/lib/libfreetype.so

Apache::Cookie->fetch

Another porting issue for mod_perl2, admittedly this is a libapreq2 change but it might be worth including in the mod_perl porting documentation as anyone porting an application might well run into it (well, I did) Apache::Cookie->fetch in libapreq2 requires that the request object is passed to it

Re: Install as DSO problems

Hi there, On Wed, 17 Dec 2003 [EMAIL PROTECTED] wrote: > I am running Solaris 9, perl 5.6.1, apache 1.3.22. > I am trying to install mod_perl as a DSO [snip] First, please read the documentation to see what other information you should supply, you'll find useful links at the bottom of any messag