There probably is some F::F::R extension that looks into files that could eliminate my greps and readfiles completely.
Yep, and it's waiting right there in the File::Find::Rule POD.. :) I know you said it's throwaway, but for the heck of it (untested):
#!/usr/bin/perl -w use strict; use File::Find::Rule; my %uid; my %vm_data; print("Killing $_\n"), kill 15, $_ for map /(\d+)/, File::Find::Rule ->file ->name('status') ->grep(sub { my $fullname = $_[2]; $uid{$fullname}++ if /^Uid:\s*33\b/; $vm_data{$fullname}++ if /^VmData:\s*(\d+)/ and $1 > 16384 +; return $uid{$fullname} and $vm_data{$fullname}; }) ->in('/proc');
What can I say? File::Find::Rule rocks. :)

Makeshifts last the longest.


In reply to Re: Killing Apache by Aristotle
in thread Killing Apache by Juerd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.