If the process which is forking them is avaliable to do stuff then you could fork them with an open(FH, "-|") in which case the forked stdout would go to that file handle for the main process to collate the all togeather.

Another method is to have each one logging to seperate files and then the main process when it closes sticks them all togeather, but thats a bit dodgy I would say.

But otherwise if your main process does need to do stuff then you probabley should go for the open+lock+write+close

I'm not sure but you might not have to open it everytime, just lock it, but hold me to that.

Toby

In reply to Re: Multiprocess logging mechanism by Anonymous Monk
in thread Multiprocess logging mechanism by Anonymous Monk

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.