On Fri, 17 Oct 2003, Post, Mark K wrote:
> Date: Fri, 17 Oct 2003 16:53:57 -0400
> From: "Post, Mark K" <[EMAIL PROTECTED]>
> Reply-To: Linux on 390 Port <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: Error Building glibc 2.3.2
>
> I figured it out. The process was using 115MB+ of virtual storage, and I
> ran out of swap space. (The top command does have its uses.) Adding
> another swap file allowed the command to finish. I have to say that "Error
> 143" is _very_ uninformative in a case like this. :(
The way Linux handles "out of memory" errors sucks bunnies through
garden hoses (as jdow would say).
Remember to take a look at /var/log/{messages,syslog}, or run this:
dmesg | tail
from time to time when these things happen.
Most recently I found rsync consuming too much memory when backing up
20 Gbytes of data.
It ran out on both machines (target, source).
--
Cheers
John.
Join the "Linux Support by Small Businesses" list at
http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
Copyright John Summerfield. Reproduction prohibited.
