its a client server app
we have an application (sqr) that can only run (licensing issues) on one machine. Currently we rsh commands over to that box. This has been ok for many years but now we have run up against resource issues with that box. Our unix sa says that there is a limit on the number or rsh sessions that it can handle. So , we decided to rewrite the process using a socket client forking-server set of programs. What I found out while doing this is that many programmers have left alot of debug 'show' commands in their sqr code. For debuging and testing of this new process it was necessary for me to be able to not have all the clutter of these 'debug' statments spewing into the stdout of the server (the parent process).

In reply to Re: Redirecting STDOUT by mifflin
in thread Redirecting STDOUT by mifflin

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.