--On Thursday, June 05, 2003 10:23 AM -0700 Donald MacDougall <[EMAIL PROTECTED]> wrote:
From my limited understanding I figure it would have to be a Perlproblem of some sort, but I really can't figure out what. I have other perl applications running that never cause anything like this.
I disagree. Problems with perl should *at worst* cause perl to segfault.
Any time any application can cause an entire system to freeze I feel the cause is one of two things. Either an old buggy kernel, or a hardware problem that the particular application just happens to trigger. And in my 7 years of experience as a programmer and sysadmin, 99% of the time its hardware.
My first guess would be you may have a disk problem. For example, it might be in your swap partition, and it only causes problems when you're exercising the machine enough to be swapping pretty hard. But any number of other problems could be the cause.
Use some standard system debugging procedures, and a little of the Scientific Method:
Contemplate other ways in which the machine is using its hardware more agressively when a failure occurs. Try running other programs that exercise that hardware. Run 'dmesg' and look for kernel errors that may be early warning signs. Listen for strange noises (disk problems). Open up the machine and disconnect and reconnect everything, including reseating memory, PCI cards, etc. Install and use utilities for monitoring the system temperature. Try replacing hardware components with hot-spares. (You do have spare hardware, right?)
You get the idea...
-David Nolan Network Software Developer Computing Services Carnegie Mellon University
_______________________________________________ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
