Allo monks, I have a strange, strange puzzle for you. I have a class library built that uses a symbolic reference for SIGTERM. Basically, its
$SIG{TERM} = "sigterm_handler";
I do this basically so each app that uses this class can have its own set sigterm handler.

Now, this is where the wierdness starts. First, I start up multiple instances of the same perl script which is using this class. They have different PIDS and PGIDs but the same PPIDs and SIDs.

Now I send a SIGTERM (basically "kill <pid>") to ANY of these processes.. and the rest also receives the SIGTERM! I'm fairly sure its a clean SIGTERM exit because I log in the handler. But now if I remove the sym ref in the class, this DOESN'T happen.

This is just so odd to me. How would sending a SIGTERM to one process propagate to another? I need help.. and an Advil.

TIA
Mike


In reply to wierd wierd behavior with SIGTERM and classes by shrubbery

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.