Bug 764519 (GLUSTER-2787) - if gsyncd is spawned by glusterd, it ignores signals
Summary: if gsyncd is spawned by glusterd, it ignores signals
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2787
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 3.2.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Venky Shankar
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-17 06:43 UTC by Csaba Henk
Modified: 2011-12-16 10:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTNR
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Csaba Henk 2011-04-17 06:43:51 UTC 
... except for SIGINT, and of course, unmaskable ones. This does not happen when gsyncd runs standalone (ie. invoked from shell).
Comment 1 Csaba Henk 2011-08-25 10:08:14 UTC 
"Run" process spawning liblet makes this issue go away as it resets signal masks properly. Hence marking it dupe of run's bz entry.

*** This bug has been marked as a duplicate of bug 2562 ***
Comment 2 Venky Shankar 2011-11-02 07:15:14 UTC 
Need patch to start fork'ed processes with empty signal mask. This is needed for gyncd log-rotate command (which uses SIGUSR1).
Comment 3 Csaba Henk 2011-11-03 15:42:34 UTC 
This issue is now 3.2.x-only, on mainline commits for bug 764294 take care of it, too.
Comment 4 Anand Avati 2011-11-04 06:06:32 UTC 
CHANGE: http://review.gluster.com/657 (Fork'ing causes child to inherit the signal mask of the parent. Hence) merged in release-3.2 by Vijay Bellur (vijay)
Note You need to log in before you can comment on or make changes to this bug.