I've found the Apache::Resource module is
a lifesaver in these situations - you can limit 
the CPU time and memory used by a process,
so these things *don't* kill the server...

Michael

> -----Original Message-----
> From: Wim Kerkhoff [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 27, 2001 5:09 PM
> To: Gerald Richter
> Cc: Peter Mayr; Angus Lees; Embeded PERL ML
> Subject: Re: stopping EMB:PERL
> 
> 
> Gerald Richter wrote:
> > 
> > >
> > > that a sql statement couldn't be executed (I had an error 
> in my sql
> > > syntax a ';'),
> > 
> > Maybe this has triggered an endless loop in your Perl code. 
> An endless loop
> > will not be stopped by Embperl (because it can't detected 
> it), Apache has a
> > timeout, which is 10 minutes per default, after that it 
> should stop the
> > request (but I never have tried if it really does).
> 
> I've had this several times... I learned that doing
> 
> [$ while (@stuff = $sth->fetchrow-array) $]
> 
> Will kill a server (100% CPU, 100% memory, 100% swap) in seconds. (The
> '-' should be a '_'.)
> 
> > The easiest way to stop such a request is to kill the 
> corresponding Apache
> > child process (if you running Unix, on Windows you can only 
> restart the
> > server). Simply run top, see which child consumes your cpu 
> time and kill it.
> 
> Which works when you have superuser access :P
> 
> 
> Wim
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

http://www.iii.co.uk 
Interactive Investor International is a leading UK Internet personal 
finance service that provides individuals with the capability to identify, 
compare, monitor and buy online a number of financial products and services.

Interactive Investor Trading Limited, a subsidiary of Interactive Investor 
International plc, is regulated by the SFA.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to