Doug MacEachern wrote:
>
> On Tue, 6 Jun 2000, Tom Lancaster wrote:
>
> > Here's the output of gdb: ( now what does this mean?)
> ...
> > Breakpoint 1, 0x400ddd35 in exit () from /lib/libc.so.6
> > (gdb) bt
> > #0 0x400ddd35 in exit () from /lib/libc.so.6
> > #1 0x80851e1 in ap_start_restart (
On Tue, 6 Jun 2000, Tom Lancaster wrote:
> Here's the output of gdb: ( now what does this mean?)
...
> Breakpoint 1, 0x400ddd35 in exit () from /lib/libc.so.6
> (gdb) bt
> #0 0x400ddd35 in exit () from /lib/libc.so.6
> #1 0x80851e1 in ap_start_restart ()
> #2 0x8085454 in ap_start_restart ()
>
On Tue, 6 Jun 2000, Tom Lancaster wrote:
> Hi,
> I've got this strange behavior in a production site that until a recent
> upgrade never showed this kind of thing:
> I've set maxclients to 50, maxrequestsperchild 1.
> What happens is that the server runs fine, is fast, etc, but the number
> of ap
OK, I followed the directions in SUPPORT, for gdb, and got this :
(gdb) run -X -f /usr/local/apache/conf/httpd.conf.test
Starting program: /usr/local/mod_perl-1.24/../apache_1.3.12/src/httpd -X
-f /usr/local/apache/conf/httpd.conf.test
Subroutine Apache::TIEHANDLE redefined at
/usr/lib/perl5/5.00
On Tue, 6 Jun 2000, Tom Lancaster wrote:
> Here's the output of gdb: ( now what does this mean?)
You should compile mod_perl with PERL_DEBUG=1, see the SUPPORT file.
>
> Starting program: /usr/sbin/apache -X
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging sym
Here's the output of gdb: ( now what does this mean?)
Starting program: /usr/sbin/apache -X
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging sy
On Tue, 6 Jun 2000, Tom Lancaster wrote:
> Hi,
> I've got this strange behavior in a production site that until a recent
> upgrade never showed this kind of thing:
> I've set maxclients to 50, maxrequestsperchild 1.
> What happens is that the server runs fine, is fast, etc, but the number
> of ap
Hi,
I've got this strange behavior in a production site that until a recent
upgrade never showed this kind of thing:
I've set maxclients to 50, maxrequestsperchild 1.
What happens is that the server runs fine, is fast, etc, but the number
of apache processes climbs gradually until it reaches ~maxc
