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.

use Perl

All the Perl that's Practical to Extract and Report

How not to make empty promises More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Running unlimited, eh? (Score:1)

by parv (6865)

For things like Firefox which have tendency (from your account) to use too much memory & molest the hard disk, why don't run them with (something like) limits(1) [freebsd.org]?

--
- parv
- Re: (Score:1)
  
  by Aristotle (5147)
  
  They don’t have a tendency to eat too much memory! Firefox just tries to use up what the kernel promised.
  
  Ever since I changed the overcommit ratio, unsurprisingly, there hasn’t been a single problem.
  Of course, I could use limits(1) or similar to individually reverse the kernel’s promises on a per-process basis, but why would I do such a backwards thing? I’d rather fix the problem once, at the source: the kernel’s unrealistic promise.
  - Re:Running unlimited, eh? (Score:1)
    
    by parv (6865) on 2007.07.06 19:03 (#56030) Homepage Journal
    
    Oh, you see "per process basis" is the "fine-grained option". (I do get your point about setting the limit in global scope.)
    
    --
    - parv
    
    Reply to This
    
    Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.