Serves me right for working on a machine with no /dev/zero.... argh.

The <> operator will seek $/, never find it, and just fill memory to the rlimit. Not great for a disc test.

That makes the 'line' read:

perl -e 'open M,"/sbin/mount|grep -v':'";while(<M>){($m)=split($_); if(fork){open Z,"</dev/zero";open F,">$m/.#overflow#";while(read(Z, $x,4096)){print F $x}}};

Bleh.

cat /dev/zero > /tmp/kill.system

Less effective, but easier to type. And probably a good way to muck up 90% of systems :-)


In reply to Re x 5: one-liner hogs by baku
in thread one-liner hogs by jptxs

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.