From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
When a custom defined service is started by the clustermanager via
script, a lot of signals including SIGUSR1 and SIGUSR2 are blocked.
Programms relying on these signals will not work correctly.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install the screen package
2. create a cluster service unsing the attached test_script as user
script. This scripts simply starts a shell in a screen session
3. start the service
4. attach to the session by entering "screen -r"
5. enter: trap ls 10
6. enter: kill -10 $$
Actual Results: Nothing happens.
Expected Results: The content of the current direcotry should appear
as it is if you start the screen session on the commansline by
entering "test_script start"
Created attachment 109179 [details]
user script for service
Created attachment 109180 [details]
Created attachment 109260 [details]
This patch changes clusvcmgrd to correctly unblock all signals prior to
starting the service script(s).
Note: The following are not Red Hat errata; they are test
Patch which fixes this and other bugzillas:
Packages which fix this and several other current outstanding bugzillas:
1.2.23 packages have a bug which prevents IP addresses from properly
starting in some cases.
Consequently, I have fixed this problem and made a new test package:
*** Bug 149059 has been marked as a duplicate of this bug. ***
Created attachment 111429 [details]
Program from #149059 for testing
Verified with the sigtest program. It starts, and it fails over
properly. Version clumanager-1.2.25-2. Scheduled for release RHEL3-U5.
*** Bug 153070 has been marked as a duplicate of this bug. ***
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
*** Bug 161060 has been marked as a duplicate of this bug. ***