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

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.
  • 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
    • 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.