All the Perl that's Practical to Extract and Report
use Perl Log In
Matts (1087)
(email not shown publicly)
I work for MessageLabs [messagelabs.com] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.
HTTPD problems
I've taken httpd on axkit.org down permanently for now, until I can figure out what the heck is up with it. I've now had to reboot twice. Last time I could see it, there were about 50 httpd's spawned (which is a lot when each uses mod_perl and about 15M of ram!), and all were using 100% of RAM. I swear all I did was restart the httpd after deleting a bunch of log files.
However, I can see how a restart might potentially affect things - if I did a apt-get upgrade (which I did) a few weeks ago, but hadn't restarted my httpd since, it might change something that could cause this.
So I'm a bit lost now. How do I fix it? I have absolutely no idea what to do right now. I tried the old USR2 signal trick, where you install a signal handler to do a Carp::confess, but that failed to work (nothing appeared in my logs).
Yours bogglingly, Matt.
--Larry Wall in stab.c from the perl source code
MaxClients (Score:2)
If you don't have a proxy you want to install one, then you'll be able to do a
-- ask bjoern hansen [askbjoernhansen.com], !try; do();
Re:MaxClients (Score:2)
It's so easy to forget this stuff when you're no longer doing mod_perl development.
Looks like the lock up is somewhere in XML::LibXML parsing. Probably based on an upgraded libxml2 without recompiling XML::LibXML.
Set child process life span (Score:1)
@JAPH = qw(Hacker Perl Another Just);
print reverse @JAPH;