Bug 73615

Summary: Service manager blocked signals cause user service scripts to fail
Product: Red Hat Enterprise Linux 2.1 Reporter: Lon Hohberger <lhh>
Component: clumanagerAssignee: Lon Hohberger <lhh>
Status: CLOSED ERRATA QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 2.1CC: mwaite, sabdelg
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-09-06 19:16:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Example of how to break 1.0.11 during 'service start'. none

Description Lon Hohberger 2002-09-06 19:15:56 UTC 
Description of Problem:
When clustering certain applications which use signals to synchronize or
communicate with eachother, the tasks fail to run properly because the service
manager spawns them with most or all signals blocked.


Version-Release number of selected component (if applicable):
1.0.11, CVS/Development


How Reproducible: Every Time


Steps to Reproduce:
1. Create a process which goes to sleep and uses SIGALARM to wake itself up. 
Have it wait forever until SIGALARM is called.
2. Create a service script which spawns this process in the "start" path.
3. Create a service which uses this script.
4. Attempt to enable the service.  Watch the service script hang.

Actual Results:
Hung service start/Application broken.


Expected Results:
Clean service start.
Comment 1 Lon Hohberger 2002-09-06 19:16:36 UTC 
I will fix this ASAP.
Comment 2 Lon Hohberger 2002-09-06 20:01:55 UTC 
Fix in pool.
Comment 3 Lon Hohberger 2002-09-06 20:04:02 UTC 
Created attachment 75324 [details]
Example of how to break 1.0.11 during 'service start'.