* re: in place file splitter
@ Tyler Spivey
` Adam Myrow
` killing process wasRe: " Kenny Hitt
0 siblings, 2 replies; 3+ messages in thread
From: Tyler Spivey @ UTC (permalink / raw)
To: speakup
well, i guess you'd have to have enough memory to hold the whole file.
that doesn't matter though, since the worst that can happen is that the
kernel will kill any old process when the ram and swap fill up.
i've had no swap, and my ram got filled and it killed anything - it picks a
number at random and kills it.
not very useful, just extreamly annoying - it should kill the process that
is eating up all the ram.
but now that we can add huge ammounts of swap space, this isn't a big issue
anymore.
just dd to a file with input from /dev/zero, run swapon, and if the file
gets filled reboot so the swapspace
isn't used, and trash it.
^ permalink raw reply [flat|nested] 3+ messages in thread
* re: in place file splitter
in place file splitter Tyler Spivey
@ ` Adam Myrow
` killing process wasRe: " Kenny Hitt
1 sibling, 0 replies; 3+ messages in thread
From: Adam Myrow @ UTC (permalink / raw)
To: speakup
Killing processes when memory runs out usually isn't a big deal, and it's
better than a hang or crash. However, try running parted with 32MB of RAM
from a boot disk some time and you'll learn real quick how to restore from
backup. I did that and since the boot floppy uses a RAM disk and there
was no swap, I ran out of memory in the middle of resizing a partition.
Well, guess what happens when parted gets killed in the middle of
something like resizing a partition? I had scrambled eggs for a
filesystem and it didn't just effect that partition. It somehow effected
my Slackware partition as well requiring me to restore two partitions from
backups. So, if you have less than 128MB of memory and plan on doing
anything disk intensive, better find a free partition for swap space or
disaster could strike.
^ permalink raw reply [flat|nested] 3+ messages in thread
* killing process wasRe: in place file splitter
in place file splitter Tyler Spivey
` Adam Myrow
@ ` Kenny Hitt
1 sibling, 0 replies; 3+ messages in thread
From: Kenny Hitt @ UTC (permalink / raw)
To: speakup
Hi. When my memory filled up, the Kernel didn't just pick a process at
random. It started killing the processes that were eating up the
memory.
Kenny
On Tue, Nov 12, 2002 at 02:22:03PM -0800, Tyler Spivey wrote:
> well, i guess you'd have to have enough memory to hold the whole file.
> that doesn't matter though, since the worst that can happen is that the
> kernel will kill any old process when the ram and swap fill up.
> i've had no swap, and my ram got filled and it killed anything - it picks a
> number at random and kills it.
> not very useful, just extreamly annoying - it should kill the process that
> is eating up all the ram.
> but now that we can add huge ammounts of swap space, this isn't a big issue
> anymore.
> just dd to a file with input from /dev/zero, run swapon, and if the file
> gets filled reboot so the swapspace
> isn't used, and trash it.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
in place file splitter Tyler Spivey
` Adam Myrow
` killing process wasRe: " Kenny Hitt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).