and
> DBD::Oracle. if you export it from /etc/profile then you probably don't
> need to do this (but it can't hurt, either - I do both)
>
> I don't know specifically why Apache::Reload is causing this behavior, but
> try the above and see if that clears things up
ders_out->add($cookie);
> ...
>
> If the user is surfing to different pages this works,
> but if he just hits reload the cookie is not being set by the browser
> (Netscape seems to check the date of the file or something like that)
> OR the browser gets the old cookie again
Yes i tried it also with no_cache(1),
the problem (i think) is that the page has been sent already
once without no_cache when the user hits reload.
I don't know if it would be a good idea to disable caching for all pages ..
could i just fake that the the filedate for this page has change
>I am using mod-perl, and I am in the development stages of coding. Each time
>I make a code change to a module, I must restart apache. I know there must
>be docs for this, but I cannot find them from the apache web site. Could
>someone assist me in finding those? Or if someone knows of a simple w
ically? I
would rather not have to go into each file manually and put "use
Apache::Reload".
Do I just put
PerlInitHandler Apache::Reload
in httpd.conf? Is there anything else that I have to do?
,
and if it can be turned off while still enabling Reload.
Thanks!
Bryan
On Thu, 2 Aug 2001, Sidharth Malhotra wrote:
SM> In the Apache::Reload module, if the 'require' fails, your script
SM> bails out, and your client gets status 500. The side effect is
SM> that totally unrelated scripts can fail because a bad programmer
SM> on another end of
On Thu, 2 Aug 2001, Sidharth Malhotra wrote:
> In the Apache::Reload module, if the 'require' fails, your script bails out,
> and your client gets status 500. The side effect is that totally unrelated
> scripts can fail because a bad programmer on another end of the s
--- Original Message ---
From: "Stas Bekman" <[EMAIL PROTECTED]>
To: Ron Savage <[EMAIL PROTECTED]>
Cc:
Sent: Sat, 01 Mar 2003 12:47:39 +1100
Subject: Re: [MP2] Apache::Reload date bug
>Ron Savage wrote:
>>On Tue, 25 Feb 2003 09:40:05 +1100, Stas Bekman wrote:
>
I'm trying to do some development work with mod_perl and find restarting the server a pain. So I setup Apache::Reload, but it doesn't seem to want to see my local devel directory all the time.Here's my settingsApache/2.0.40mod_perl-1.99_7Linux 2.4.20-8 (RedHat9 I think)Here
I believe they are using meta refresh tags in the html to refresh the page
on a regular interval.
Craig
On Wed, 20 Sep 2000, Michael Nachbaur wrote:
> This is off-topic, but I need an answer pretty quick, and I *am* writing this app
>using mod_perl, so its sorta related (also, I don't want th
On Wed, 20 Sep 2000, Michael Nachbaur wrote:
> This is off-topic, but I need an answer pretty quick, and I *am*
> writing this app using mod_perl, so its sorta related (also, I don't
> want the headache of re-subscribing to a new list).
>
> You know those online web-based tech support chat syste
| Plain old meta refreshes. Usually every 5 or 10 seconds or so. Perhaps
| configurable on a user and/or server basis.
You could make it even more smooth by doing a multipart document (aka server
push): finishing a HTML document but not closing the HTTP connection and
start a new document as soon
i think that this technique works with netscape but not with IE. on IE you have to
set-up channels.
Ime Smits wrote:
> | Plain old meta refreshes. Usually every 5 or 10 seconds or so. Perhaps
> | configurable on a user and/or server basis.
>
> You could make it even more smooth by doing a mult
On Wed, 20 Sep 2000, Ime Smits wrote:
> | Plain old meta refreshes. Usually every 5 or 10 seconds or so. Perhaps
> | configurable on a user and/or server basis.
>
> You could make it even more smooth by doing a multipart document (aka server
> push): finishing a HTML document but not closing the
| I was under the impression that internet explorer dropped support for
| server push...
OK, didn't know that. We should probably lawsuit them for telling us
"Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)" then ;)
Ime
> "Michael" == Michael Nachbaur <[EMAIL PROTECTED]> writes:
Michael> This is off-topic, but I need an answer pretty quick, and I
Michael> *am* writing this app using mod_perl, so its sorta related
Michael> (also, I don't want the headache of re-subscribing to a new
Michael> list).
Michael> Y
Hi
type: multipart/x-mixed-replace
use CGI::Push qw(:standard)
do_push(-next_page=>\&draw_a_page)
sub draw_a_page {
my ($q,$counter)= @_;
return undef if $counter >100;
my $time = localtime();
return start)html(),
h1('test'),
'T
A very impressive 95 lines o' Perl Randal!
Ed
"Randal L. Schwartz" wrote:
> > "Michael" == Michael Nachbaur <[EMAIL PROTECTED]> writes:
>
> Michael> This is off-topic, but I need an answer pretty quick, and I
> Michael> *am* writing this app using mod_perl, so its sorta related
> Michael>
Michael Nachbaur asked:
> This is off-topic, but I need an answer pretty quick, and I *am*
> writing this app using mod_perl, so its sorta related (also, I don't
> want the headache of re-subscribing to a new list).
>
> You know those online web-based tech support chat systems? Its
> commonly fra
usually loads,
but from time to time it gets cut in the middle.
It's not that the HTML of the page has problems, it's just that
the page content is not
loaded in its entirety.
The reload of a page has just about the same frequency of problems.
With IE (5.0) the loading of the page show
pt "use"s), then the changes will take effect automatically? I
> would rather not have to go into each file manually and put "use
> Apache::Reload".
>
> Do I just put
>
> PerlInitHandler Apache::Reload
>
> in httpd.conf? Is there anything else that I have t
covered in SYNOPSIS.
In "perldoc Apache::Reload", the DESCRIPTION has the following sections:
- StatINC Replacement
- Register Modules Implicitly
- Register Modules Explicitly
- Special "Touch" File
I just re-read it again and realized that "StatINC Replacement" i
--On 30/07/01 06:43 -0400 Philip Mak wrote:
> In "perldoc Apache::Reload", the DESCRIPTION has the following sections:
>
> - StatINC Replacement
> - Register Modules Implicitly
> - Register Modules Explicitly
> - Special "Touch" File
>
> I just
On Tue, 31 Jul 2001, Kyle Oppenheim wrote:
> Apache::Reload works by performing a stat on every file in %INC and calling
> require for all the files that changed. It's quite possible that some of
> the files in %INC are using relative paths (often '.' is in @INC). So,
Of
Bryan Coon
Sent: Wednesday, August 01, 2001 9:36 AM
To: '[EMAIL PROTECTED]'
Subject: One more small Apache::Reload question
First, thanks to all the great suggestions, it looks like it works fine.
However, now my logs are loaded with a ton of subroutine redefined warnings
(which i
> However, now my logs are loaded with a ton of subroutine redefined
warnings
> (which is normal I suppose?). I can certainly live with this in a
> development environment, but thought I would check to see if it is
expected,
> and if it can be turned off while still enabling R
Ugh! Not use to lists that reply to author.
Okay to resay what I sent to Geoffrey.
using the -I switch in the config file works, unlike the PerlSetEnv PERL5LIBGeoffrey Young <[EMAIL PROTECTED]> wrote:
>> Here's my perl.conf (sourced by httpd.conf)>> start LoadModule pe
Bruce Tennant wrote:
I'm trying to do some development work with mod_perl and find
restarting the server a pain. So I setup Apache::Reload, but it
doesn't seem to want to see my local devel directory all the time.
Here's my settings
Apache/2.0.40
mod_perl-1.99_7
please upgrade to
Here's my perl.conf (sourced by httpd.conf)
start
LoadModule perl_module modules/mod_perl.so
PerlSetEnv PERL5LIB /home/bruce/public_html/ffball/myff
on second thought, try
PerlSwitches -I/home/bruce/public_html/ffball/myff
or
PerlSwitches -Mlib=/home/bruce/public_html/ffbal
Hi Folks
Fascinating to see this on a non-Windows box.
Reloading modules after they have been editied, eg httpd like so:
PerlModule Apache::Reload
PerlInitHandler Apache::Reload
PerlSetVar ReloadAll Off
PerlSetVar ReloadModules "CGI CGI::Application ... Sweep::*"
works about 99% o
Hi folks,
I was wondering if there is a possibility to reload perl
module (and I want reloaded module in all Apache children processes) by
running reload-program once.
For example Apache::Reload must be set as PerlInitHandler, so
it's handler method is run every time request com
Hello mod_perl'ers.
I don't know if it's just me, but I'm having problems with growing
memory reallocation on a HUP or graceful (USR1) restart. I've looked
through the mailing list archives and the wonderful guide, but have
come up short of answers.
First off, the config:
Red Hat apache 1.3.
On Tue, 31 Jul 2001, Philip Mak wrote:
> On Tue, 31 Jul 2001, Kyle Oppenheim wrote:
>
> > Apache::Reload works by performing a stat on every file in %INC and calling
> > require for all the files that changed. It's quite possible that some of
> > the files in
I started using a dynamic @INC (set up in a TransHandler), and discovered
that Apache::Reload (v0.07) was not doing its job correctly in that case.
Note, changing @INC in a transhandler won't have the desired Apache::Reload
effects unless the PerlInitHandler for Apache::Reload is placed
Hi again group.
A quick question (but this might not be the right place).
If this is the wrong place to ask, please point me in the direction of the
right place.
I have a web app written using mod_perl2 and apache::ASP.
When I change the code in a perl module, I have to restart apache to make
t
Forwarding message as I didn't realize I was missing the list.
Geoffrey Young <[EMAIL PROTECTED]> wrote:
Date: Tue, 12 Aug 2003 14:18:37 -0400From: Geoffrey Young <[EMAIL PROTECTED]>To: Bruce Tennant <[EMAIL PROTECTED]>Subject: Re: Apache::Reload and INC path partialy work
Hello,
I was wondering if there is a possibility to reload PERL module compiled
into Apache
with Apache::Registry
(and I want to reload this module in all Apache children processes) by
running reload-program once.
For example Apache::Reload must be set as PerlInitHandler, so it's ha
Paul Lindner wrote:
>
> Hello mod_perl'ers.
>
> I don't know if it's just me, but I'm having problems with growing
> memory reallocation on a HUP or graceful (USR1) restart. I've looked
> through the mailing list archives and the wonderful guide, but have
> come up short of answers.
>
> First
On Thu, 20 Apr 2000, Paul Lindner wrote:
> Hello mod_perl'ers.
>
> I don't know if it's just me, but I'm having problems with growing
> memory reallocation on a HUP or graceful (USR1) restart. I've looked
> through the mailing list archives and the wonderful guide, but have
> come up short of a
> I have a static Solaris compilation, and have the same problems
> where the parent seems to grow by 1M each HUP.
that's strange, do you have PerlFreshRestart On or some sections?
otherwise, kill -HUP with a static modperl is a noop.
Hi all,
On Thu, 20 Apr 2000, Doug MacEachern wrote:
> > I have a static Solaris compilation, and have the same problems
> > where the parent seems to grow by 1M each HUP.
>
> that's strange, do you have PerlFreshRestart On or some sections?
> otherwise, kill -HUP with a static modperl is a no
Doug MacEachern wrote:
>
> > I have a static Solaris compilation, and have the same problems
> > where the parent seems to grow by 1M each HUP.
>
> that's strange, do you have PerlFreshRestart On or some sections?
> otherwise, kill -HUP with a static modperl is a noop.
You got me! I have sec
On Fri, Apr 21, 2000 at 11:28:18AM -0700, Joshua Chamas wrote:
> Doug MacEachern wrote:
> >
> > > I have a static Solaris compilation, and have the same problems
> > > where the parent seems to grow by 1M each HUP.
> >
> > that's strange, do you have PerlFreshRestart On or some sections?
> > ot
> You got me! I have sections ... but I didn't know
> it was such a crime. Pretty bizarre behavior if you ask me.
it's not a crime, but if you're running Perl code during restart there's a
strong chance you'll be growing the server size. i agree 1M is bizarre
though.
I had the same issue on Linux. My build had mod_perl compiled in static
but mod_so was also compiled in. PerlFreshRestart was off, I didn't have
any sections, and no modules were loaded dynamically. My root
process would grow by about 1MB each time it was HUPed. Something about
mod_so was cau
On Wed, Apr 26, 2000 at 08:33:07PM -0700, Douglas Leonard wrote:
> I had the same issue on Linux. My build had mod_perl compiled in static
> but mod_so was also compiled in. PerlFreshRestart was off, I didn't have
> any sections, and no modules were loaded dynamically. My root
> process would
Since memory leaks seem to be the topic du jour, I wondered if anyone
else had seen this one:
When using a modular mod_perl, I get a huge leak if I preload the 'Pg'
driver in my startup perl script thus:
#!/usr/bin/perl
use strict;
use Apache::Status ();
use Apache::DBI ();
DBI->install_driver
pache::ASP.
When I change the code in a perl module, I have to restart apache to make
the changes appear to all children.
Is there a way of avoiding this - maybe with an apache directive - so that
all modules are re-read by all children without a restart ?
Apache::Reload ships standard with mod_perl
Geoffrey Young wrote:
Richard Curtis wrote:
Hi again group.
A quick question (but this might not be the right place).
If this is the wrong place to ask, please point me in the direction of
the
right place.
you're in the right place, don't worry :)
I have a web app written using mod_pe
Waldek Grudzien wrote:
> Hello,
>
> I was wondering if there is a possibility to reload PERL module compiled
> into Apache
> with Apache::Registry
> (and I want to reload this module in all Apache children processes) by
> running reload-program once.
>
> For example
Hi Stas,
> > I was wondering if there is a possibility to
> reload PERL module compiled
> > into Apache
> > with Apache::Registry
> > (and I want to reload this module in all Apache
> children processes) by running reload-program once.
>
> Currently Apache
Sreeji K Das wrote:
> Hi Stas,
>
>
>>>I was wondering if there is a possibility to
>>
>>reload PERL module compiled
>>
>>>into Apache
>>>with Apache::Registry
>>>(and I want to reload this module in all Apache
>>
>&g
>Using Debian's static-mod_perled apache-perl eliminates the problem.
Do you mean you are using the 'so' version that comes with Debian? You
should be using the static build of apache/mod_perl
Stathy G. Touloumis wrote:
>
>
>> Using Debian's static-mod_perled apache-perl eliminates the problem.
>
>
> Do you mean you are using the 'so' version that comes with Debian?
Yes, in the case that failed. The package is called 'libapache-mod-perl'.
>
> You
> should be using the static bui
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 16 October 2002 20:25, Keith G. Murphy wrote:
> By "should", do you mean that the problems with the loadable module
> overall are so well-known that no one in his right mind should ever
> use it?
Yes. The problems with DSO mod_perl are w
Hi there,
On Wed, 16 Oct 2002, Keith G. Murphy wrote:
> do you mean that the problems with the loadable module overall are
> so well-known that no one in his right mind should ever use it?
It's not as bad as that. Significant improvements have been made in
the reliability of mod_perl as DSO an
Ged Haywood wrote:
> Hi there,
>
> On Wed, 16 Oct 2002, Keith G. Murphy wrote:
>
>
>>do you mean that the problems with the loadable module overall are
>>so well-known that no one in his right mind should ever use it?
>
>
> It's not as bad as that. Significant improvements have been made in
Juha-Mikko Ahonen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Wednesday 16 October 2002 20:25, Keith G. Murphy wrote:
>
>>By "should", do you mean that the problems with the loadable module
>>overall are so well-known that no one in his right mind should ever
>>use it?
>
>
eith G. Murphy [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 16, 2002 2:02 PM
> To: mod_perl Mailing List
> Subject: Re: Memory leak on reload when the 'Pg' driver is preloaded
>
>
> Ged Haywood wrote:
> > Hi there,
> >
> > On Wed, 16 Oct 2002, K
Hi there,
On Wed, 16 Oct 2002, Keith G. Murphy wrote:
> > Significant improvements have been made in
> > the reliability of mod_perl as DSO and nowadays there is much less
> > discussion about it on this list.
>
> Are you sure it's not because 'most everyone has silently given up on it?
Yes,
Ged Haywood wrote:
> Hi there,
>
> On Wed, 16 Oct 2002, Keith G. Murphy wrote:
>
>
>>>Significant improvements have been made in
>>>the reliability of mod_perl as DSO and nowadays there is much less
>>>discussion about it on this list.
>>
>>Are you sure it's not because 'most everyone has sil
On Wed, Oct 16, 2002 at 02:01:33PM -0500, Keith G. Murphy wrote:
> Ged Haywood wrote:
> >Hi there,
> >
> >On Wed, 16 Oct 2002, Keith G. Murphy wrote:
> >
> >
> >>do you mean that the problems with the loadable module overall are
> >>so well-known that no one in his right mind should ever use it?
>
Daniel Jacobowitz wrote:
> On Wed, Oct 16, 2002 at 02:01:33PM -0500, Keith G. Murphy wrote:
>>
>>My own bug report is now 47 days old, without apparent followup.
Hmmm, I probably should not have posted that. Sounds like a major whine.
>
>
> That's because I'm having an attack of real life. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 16 October 2002 22:52, Keith G. Murphy wrote:
> It's not like it was an obvious problem: I only got the DSO to leak
> when loading the Pg driver. That's pretty obscure.
Have you tried to connect() without loading the Pg driver first? E.
[debian-isp readers, to recap, I'm trying to confirm a
memory-leak/segfault problem with Debian stable plus apache(-ssl) plus
libapache-mod-perl. The memory leak happens upon
/etc/init.d/apache(-ssl) reload. You can see my startup script and my
other comments below.]
Juha-Mikko A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> OK, it gets weirder. The following script produces the leak. If I
> comment out the install_driver line, I get a big old segfault! Same
> if I comment out the Apache::DBI line in addition. This works with
> plain apache, or apache-ssl.
>
> #!/usr
Juha-Mikko Ahonen wrote:
I looked into it with the following setup:
apache 1.3.26-0woody1
libapache-mod-perl 1.27-2
postgresql 7.2.1-2woody2
There was a Test.pm module handling all requests for /. It opened a
connection to the database and fetched a couple of rows.
With DBI->install_driver('Pg
> "KGM" == Keith G Murphy <[EMAIL PROTECTED]> writes:
KGM> When using a modular mod_perl, I get a huge leak if I preload the 'Pg'
KGM> driver in my startup perl script thus:
Hmmm. Interesting theory. I shall have to investigate it. I also
see a multi-megabyte memory leak in my app when DB
if you use Apache::Reload with a threaded MPM and multiple interpreters,
the modules will be reloaded by each interpreter as they are used, not
every interpreter all at once. similar to 1.x where each child has
its own interpreter, the modules are reloaded as each kid is hit with a
request
[EMAIL PROTECTED] wrote:
> if you use Apache::Reload with a threaded MPM and multiple interpreters,
> the modules will be reloaded by each interpreter as they are used, not
> every interpreter all at once. similar to 1.x where each child has
> its own interpreter, the modules are
eters in it, there can be a
> thread that monitors changed modules and update the idle interpreters by
> making them reload the code and put them in the head of the list. This
> should save the overhead of reloading during a request. Does this make
> sense?
there already is a plan
[EMAIL PROTECTED] wrote:
> On Fri, 12 Apr 2002, Stas Bekman wrote:
>
>
>>But if talk about futuristic Solar variables (perl globals shared
>>between threads). what if a solar variable is a reference to CODE? Can
>>this be shared? If so, will reloading this variable in one interpreter
>>affec
On Thu, 11 Apr 2002, Perrin Harkins wrote:
> Does it look you'll be able to get the solar variables idea to work for
> those data types?
i had a simple prototype way back that sorta worked for simple scalars,
probably won't take it any further now that there is threads::shared in
5.7.x. hav
101 - 174 of 174 matches
Mail list logo
