Good advice. I would re-iterate that you probably really don't want to do this, but if you're going to anyway, you're looking at either doing what was suggested above, or doing an suid thing (bad plan). So, you're basically left with what was said above, in which case I would add that you may want to just grep out the relevant info from the logfile rather than copy the entire thing. Make sure that you have proper rules to grab _only_ the info you would want Mr. Evil Hacker to see. Even if this is on an intranet, I don't know about you, but I don't trust my users anymore than absolutely necessary, soooo...

In reply to RE: Re: Parsing log files by BastardOperator
in thread Parsing log files by cajun

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.