Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Purdy (2383)

Purdy
  jasonNO@SPAMpurdy.info
http://purdy.info/
AOL IM: EmeraldWarp (Add Buddy, Send Message)
Yahoo! ID: jpurdy2 (Add User, Send Message)

Bleh - not feeling creative right now. You can check me out on PerlMonks [perlmonks.org].

Journal of Purdy (2383)

Thursday December 06, 2001
09:20 AM

More mod_perl & Yet Another Server Crash

[ #1519 ]
Well, I completed my first mod_perl program, just in time for another server crash. It could be correlated to that, or on the fact that I have an old-ish kernel (2.2.16), which has been proven to have a memory leak in its VM and the server has been up for over 10 days.

I posted something to the Cobalt support forum and haven't a response yet. Go figure. I was lucky this time, though in that my web hosting company had a faster response time (30 min) and physically rebooted the machine for me. Fortunately, no (or not much) corruption on the HD.

So now I've survived that and I'm starting up my 2nd mod_perl program... as darobin says, once you go mod_perl, you don't go back (to vanilla CGI). I do feel like developing with mod_perl is more of an art, or rather better utilizing my Comp Sci background. Maybe that's b/c it's new and challenging.

Oh, did I mention that our server has about 160Mb (odd # - but that's what 'top' outputs) of memory. Gonna need to ask management to upgrade that as I go more & more into mod_perl.

Jason

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.