Is this what you want?

use strict;
use warnings;
use 5.010;
use threads;
use threads::shared;


my $flag = 0;
share($flag);
say "\$flag in main() is: $flag";


$SIG{'HUP'} = sub { 
    $flag = !$flag;
    say "signal caught, \$flag in main() changed to: $flag";
};


sub thr_func
{
    for (1 .. 5) {
        sleep 1;
        say "\$flag in thread is: $flag";
    }
}



my $thr = threads->create('thr_func')->detach();
sleep 3;  #allow time for thread to be created and start running

kill('HUP', $$);  #send signal to main()

sleep 10;   


--output:--
$flag in main() is: 0
$flag in thread is: 0
signal caught, $flag in main() changed to: 1
$flag in thread is: 0
$flag in thread is: 1
$flag in thread is: 1
$flag in thread is: 1

[download]

In reply to Re: Catching signals under Linux by 7stud
in thread Catching signals under Linux by weismat

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.