To follow up on marto's reply, it is generally a bad idea to reference transient material as you have done because your question stays around so others with a similar problem can refer to it. If an important part of the question is no longer available the question and replies are much less useful to people in the future.

You should put the contents of the file that you link to in code tags inside a readmore block. As marto suggests, see Writeup Formatting Tips for the details of how to do this. Note too that it is conventional (to make your text easier to read) to put a space after full stops and commas.

DWIM is Perl's answer to Gödel

In reply to Re: Why I got so many CLOSE_WAIT by GrandFather
in thread Why I got so many CLOSE_WAIT by pangj

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.