On 16 Aug 2006, at 22:40, Jonathan Vanasco wrote:
if there's an issue, big or small, i want to know where it is. if
i can fix it-- great. if i can't fix it, i can document what the
issue is, so maybe i can fix it when able to or when something
goes wrong, i know where to look.
Sounds
> Thats possibly because STDERR isn't tied to anything yet. There's
> some black magic that seems to go on.
That's correct
http://perl.apache.org/docs/2.0/user/config/config.html#C_PerlConfigRequire_
I knew that was the case, it just interferes with the behaviour that I
would like.
I think I
On Aug 16, 2006, at 5:08 PM, Michael Peters wrote:
A memory leak is when memory is used and then lost and can't be
recovered. If
the process can still access or use that memory, it's not a leak,
it's just
memory growth. Leaks should be completely eliminated. Growth should
be managed.
I
On Wed, 2006-08-16 at 14:01 -0700, David Scott wrote:
> "...uses more memory over time..." Hmm, sounds like an actual leak to
> me, unless there's some justification for it.
Usually it's just normal perl behavior. You use variables, they need
memory, they don't give the memory back, and the who
David Scott wrote:
> "...uses more memory over time..." Hmm, sounds like an actual leak to
> me, unless there's some justification for it.
>
> I agree that the problem is probably in someone's XS somewhere. But a
> leak is a leak and is bad.
A memory leak is when memory is used and then lost
"...uses more memory over time..." Hmm, sounds like an actual leak to
me, unless there's some justification for it.
I agree that the problem is probably in someone's XS somewhere. But a
leak is a leak and is bad.
d
Perrin Harkins wrote:
On Wed, 2006-08-16 at 13:35 -0700, David Scott wrote
On Wed, 2006-08-16 at 13:35 -0700, David Scott wrote:
> Memory leak != memory hog. The leak could indicate instability and is a
> much higher priority than "a measly couple of KB". Even little leaks
> need to be plugged.
When people talk about "memory leaks" on this list, they almost never
mea
Jonathan Vanasco wrote:
On Aug 16, 2006, at 3:46 PM, Perrin Harkins wrote:
On Wed, 2006-08-16 at 21:03 +0200, Jiří Pavlovský wrote:
I think I see a place in my
program where it crashes. It is a initialization routine I call on
startup to get data from db and populate some caches. I can't see
On Aug 16, 2006, at 4:21 PM, Leo Lapworth wrote:
Memory is cheap / CPU is cheap (for when you reach
Apache::SizeLimit and need to spawn a new process) - your (and
other developers) time is not.
practical response:
Because I'm using some modules with known large memory leaks ( open
ssl wr
Memory leak != memory hog. The leak could indicate instability and is a
much higher priority than "a measly couple of KB". Even little leaks
need to be plugged.
d
Joel Bernstein wrote:
On Wed, Aug 16, 2006 at 03:24:32PM -0500, Matthew wrote:
Memory is cheap / CPU is cheap
My bos
On Wed, Aug 16, 2006 at 03:24:32PM -0500, Matthew wrote:
> > Memory is cheap / CPU is cheap
>
> My boss makes this same argument and I hate it. Wasting is still wasting.
Wasting developer time over a measly couple of KB, you mean?
/joel
> Memory is cheap / CPU is cheap
My boss makes this same argument and I hate it. Wasting is still wasting.
-Matthew
Playing devils advocate...
On 16 Aug 2006, at 19:54, Jonathan Vanasco wrote:
but anything thats 1k or more per request i think i need to try
and fix.
Why :) ?
Memory is cheap / CPU is cheap (for when you reach Apache::SizeLimit
and need to spawn a new process) - your (and other developer
Smolder 0.3 has arrived. This is the first release candidate towards 1.0.
Smolder is web-based smoke test aggregator used by developers and testers to
upload (automated or manually) and view smoke/regression tests using the Test
Anything Protocol. Details and trends can be viewed in various format
On Aug 16, 2006, at 3:46 PM, Perrin Harkins wrote:
On Wed, 2006-08-16 at 21:03 +0200, Jiří Pavlovský wrote:
I think I see a place in my
program where it crashes. It is a initialization routine I call on
startup to get data from db and populate some caches. I can't see
anything wrong in my perl
On Wed, 2006-08-16 at 21:03 +0200, Jiří Pavlovský wrote:
> Yes, that is the case. With mod_perl 2.0.2 it did not matter what pg
> libs I used.
But the segfault happens when you try to use DBD::Pg, not mod_perl,
right? If you just take out the Pg stuff, does it start ok?
> I think I see a place
Perrin Harkins wrote:
On Wed, 2006-08-16 at 16:19 +0200, Jiří Pavlovský wrote:
Httpd segfaults if I compile DBD::Pg against newer libreries and/or
use newer mod_perl.
So you're saying that it segfaults if you compile DBD::Pg against the Pg
8.1.4 libs or if you compile mod_perl 2.0.2 with
still profiling stuff like crazy, and using ab to bench single pages
while watching top / ps
i've been isolating stuff i know to leak so i can continue looking
for issues
i'm finding a ton of stuff in random libraries, and have been
prioritizing on what to fix
obviously , 4k/request is
in the extreme development model, the task of removing the debug statements
rarely gets prioritized to the point of happening. Popularizing constant-based
debug statements as a best practice is certainly an approach; maybe if
we get some power to impose standards by refusal we can insist that all
WHEN restart_count!=1
- setup happens only when it should, but you don't see any of the
startup info.
- if I print the startup info to STDERR instead of STDOUT, then you
don't see anything on 'apachectl start', but you do on
'apachectl restart'
Thats possibly because STDERR isn't ti
On Wed, 2006-08-16 at 16:19 +0200, Jiří Pavlovský wrote:
> Httpd segfaults if I compile DBD::Pg against newer libreries and/or use
> newer mod_perl.
So you're saying that it segfaults if you compile DBD::Pg against the Pg
8.1.4 libs or if you compile mod_perl 2.0.2 with apache 2.0.59? Does
this
On 8/14/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
entering captain obvious mode, i realized
use constant DEBUG_CONNECT= $ENV{'P2XLP_DEBUG_CONNECT'}
Brilliant! (applause)
--
David L Nicol
Luddite! (mob of angry villagers with ray guns)
On Wed, 2006-08-16 at 19:24 +0200, Clinton Gormley wrote:
> The framework does quite a lot of work setting up the applications that
> depend on it, and one of the things it does is autoconfigures the
> virtual hosts that the application requires.
When I need to do things like that, I just template
Hi,
Could someone recommend a web-based file manager (or better yet, just
library) that works well under mod_perl and hopefully allows for
customization?
Thanks.
Arshavir
I have a homegrown framework which I use for my webapps (Perrin, it's
like the others, but faster!! and lighter!! and will be on CPAN any day
now... or something like that)
The framework does quite a lot of work setting up the applications that
depend on it, and one of the things it does is autoco
One way that I've done this kind of thing in the past is to really use
SSI and call a mod_perl handler or Registry script with it. In other
words, you write a "list users logged in" thing in CGI::Application as
usual and then call it like this from a page:
That just makes an Apache subrequest
-8<-- Start Bug Report 8<--
1. Problem Description:
$r->prev->notes->{'error-notes'} exists but is blank on an error document
redirect.
This patch appears to fix it:
--- modperl_callback.c.orig 2006-08-16 13:06:25.0 -0400
+++ modperl_callback.c
On 16 Aug 2006, at 15:23, Jesse Erlbaum wrote
(Imagine a list of the users currently logged into the site
One could quite easily have this written out into a JSON file and read
in/displayed with JavaScript/AJAX (though the JS can be a pain to
start).
or a
database query on the 5 products
On Aug 16, 2006, at 7:48 AM, Frank Maas wrote:
Which one? The first, the latter or both?
any tie.
my $options= $self->ApacheSessionOptions->{ $store };
tie %session , 'Apache::Session::Postgres', $sessionID, $options ;
my %options= $self->ApacheSessionOpti
On Wed, 2006-08-16 at 10:23 -0400, Jesse Erlbaum wrote:
> This is for primarily static web sites which are managed by a CMS. The
> CMS publishes out pages which would contain HTML + various bits of code
> to generate possibly navigation and semi-interactive bits of the page.
> (Imagine a list of t
On Wednesday 16 August 2006 02:44, Jesse Erlbaum wrote:
> think "better
> server-side includes"
Are you aware of Apache::IncludeHook?
Torsten
pgpQwNFblgmUS.pgp
Description: PGP signature
> I think understanding what you are actually going to do in the SSI
> would help
> somewhat - is this dynamic content based on per user - or just
> navigation on
> the website depending on the section you are in?
This is for primarily static web sites which are managed by a CMS. The
CMS pub
Hi,
I'm runnig RHEL3 on server and wanted to use Apache::AuthCookie module
for my application. As it needs mod_perl 2.0.0rc5 and RHEL3 comes with
1.99_09 I decided to upgrade.
I installed apache 2.0.59, postgresql 8.1.4. Here my problems started.
The only workable combination is to downgrad
When I asked about early bird rates at the beginning of the month, this
is what I found out. Clearly the dates of the price changes have
shifted, but I expect that the price increments will likely stay the
same.
---
After August 10 the price will go to $650. then it goes to $850 and
finally to $1
On 16 Aug 2006, at 15:04, Jesse Erlbaum wrote:
My proverbial "better SSI".
I think understanding what you are actually going to do in the SSI
would help
somewhat - is this dynamic content based on per user - or just
navigation on
the website depending on the section you are in?
Personal
Hi Perrin --
> Depending on what you want to use it for, you might also consider just
> using Template Toolkit with the in-line perl option enabled.
That's an interesting idea. I was not familiar with that option. It is
possible that a full framework is not needed.
> Or... you could write
hi all :)
registration for ApacheCon US 2006 (October 9-13 in Austin, Texas) is
now open.
for those not familiar with ApacheCon, it's the annual US conference for
all things Apache - from httpd and mod_perl to spamassassin and other
popular Apache Software Foundation projects. you can find the d
On Wed, 2006-08-16 at 03:51 -0400, Jonathan Vanasco wrote:
> Can someone confirm if there is a memory leak in Apache Session ?
Your best bet is to just keep going using the same technique until you
find it. You have all the source, so there's no reason to stop when you
hit someone else's code.
>
> the loss happens directly after the tie.
Which one? The first, the latter or both?
Regards,
Frank
On Aug 15, 2006, at 4:28 PM, Perrin Harkins wrote:
If that happens even when you just send the same request every time to
the same process, there's something extra going on, like a variable
not
going out of scope or being added to each time.
It took me 4 hours to track this down, I finally
40 matches
Mail list logo
