Some thoughts.

You should know that signal handlers are not fully safe to do much in especially printing.

You probably want to set a flag in your handler and return. Then check the flag in your main code and write out relevant info and clear the flag.

As for reconnecting output with your terminal, I think you should look along the lines of an output file then in your session tail -f the file or look into syslog which can recieve messages from programs and then send them to users (you) when they are logged in. Messages collected while you are not logged in are tossed though unless you also have syslog send those messages to some file, which brings us back to the first method.

In reply to Re: Diagnositc output on background processes by dga
in thread Diagnositc output on background processes by gomez18

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.