[ python-Bugs-884533 ] SIGTERM blocked in processes forked by threads

[SourceForge.net]

Bugs item #884533, was opened at 2004-01-26 04:42
Message generated for change (Settings changed) made by jackjansen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=884533&group_id=5470

Category: Macintosh
Group: Python 2.3
>Status: Closed
Resolution: Duplicate
Priority: 5
Submitted By: Steve Muir (hairy_flange)
Assigned to: Jack Jansen (jackjansen)
Summary: SIGTERM blocked in processes forked by threads

Initial Comment:
python version 2.3 (#1, Sep 13 2003) apple build 1495

When a child process is created using os.fork, from a
thread spawned by threading.Thread, that child will
have SIGTERM blocked (problem #1) but python thinks
that it is still being handled in the default way (problem #2).

Fink python version 2.2 behaves as expected i.e., SIGTERM
is not blocked in the child process.  This can be observed
by running the attached test program in both environments:
Apple python 2.3 outputs

SIGTERM status: 0 [corresponds to signal.SIG_DFL]
child exited normally

whereas Fink python 2.2 outputs

SIGTERM status: 0
child killed by signal

Note that explicitly setting the SIGTERM handler to
SIG_IGN in the child process under Fink python produces
the same behaviour as Apple python, and the blocked
SIGTERM can be seen by execing a C program that
checks the real signal mask.

----------------------------------------------------------------------

Comment By: Steve Muir (hairy_flange)
Date: 2004-01-26 05:08

Message:
Logged In: YES 
user_id=960132

sorry, looks like i submitted a duplicate of bug #853411

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=884533&group_id=5470