From victor@vsespb.ru

This example is broken​:
http​://perldoc.perl.org/perlipc.html#Handling-the-SIGHUP-Signal-in-Daemons

it only works for first SIGHUP.

looks like it's because this issue
http​://www.nntp.perl.org/group/perl.perl5.porters/2000/01/msg5237.html
more investagations and workarounds here​:
http​://www.perlmonks.org/?node_id=1058565

I can fix the example by setting flag in signal handler, and calling exec
outside of handler, but probably there are better fixes with
POSIX​::SigAction etc which I am not familar with.

From @Leont

On Thu, Oct 17, 2013 at 7​:29 PM, Victor Efimov <perlbug-followup@​perl.org>wrote​:

# New Ticket Created by Victor Efimov
# Please include the string​: [perl #120256]
# in the subject line of all future correspondence about this issue.
# <URL​: https://rt-archive.perl.org/perl5/Ticket/Display.html?id=120256 >

This example is broken​:
http​://perldoc.perl.org/perlipc.html#Handling-the-SIGHUP-Signal-in-Daemons

it only works for first SIGHUP.

looks like it's because this issue
http​://www.nntp.perl.org/group/perl.perl5.porters/2000/01/msg5237.html
more investagations and workarounds here​:
http​://www.perlmonks.org/?node_id=1058565

I can fix the example by setting flag in signal handler, and calling exec
outside of handler, but probably there are better fixes with
POSIX​::SigAction etc which I am not familar with.

This example is broken​:
http​://perldoc.perl.org/perlipc.html#Handling-the-SIGHUP-Signal-in-Daemons

it only works for first SIGHUP.

looks like it's because this issue
http​://www.nntp.perl.org/group/perl.perl5.porters/2000/01/msg5237.html
more investagations and workarounds here​:
http​://www.perlmonks.org/?node_id=1058565

I can fix the example by setting flag in signal handler, and calling exec
outside of handler, but probably there are better fixes with
POSIX​::SigAction etc which I am not familar with.

Right, this makes sense.

During the signal handler, the signal is temporarily blocked. On exec, the
new process inherits this block.

Actually the proposed fix sucks too (it uses an unsafe signal handler);
possibly a better approach is to unblock it before the exec call.

Leon

The RT System itself - Status changed from 'new' to 'open'