Ahhh ok in this case, forking off as many copies of your script as you can get away with to flood the syslog server with connections is the way to go, probably somewhere around 50-100 forked children is a good place to start, have the parent spawn off the children who each attempt one connection then die, that way the parent can launch another child and keep track of how many connection attempts where made and you can compare that to how many syslog entries exist. Be sure to run top in another terminal the first couple tests and make sure you arn't swaping out..if so reduce the number of children forked, if you have lots of memory free increase the number..


daN.

In reply to Re^4: help me fork by mutated
in thread help me fork by mhearse

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.