From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Description of problem: The SIGPIPE signal is set to be ignored in rhnsd.c via syscall: signal (SIGPIPE, SIG_IGN); Due to this, actions (commands) scheduled to be executed via RHN, when executed using rhn_check, also inheret an ignored SIGPIPE This causes problems with certain utilities like cron, which when restarted, pass this Ignored SIGPIPE further down causing problems like: zcat: stdout: Broken pipe (while running makewhatis.cron) Refer Bugzilla #64836 Possibly also impacts up2date-4.2.57-2 from RHEL 3 Update 4. Version-Release number of selected component (if applicable): up2date-4.2.38-1 How reproducible: Always Steps to Reproduce: Run the following via Remote Command -> Script Window #!/bin/sh exec 1>/tmp/test echo "Sending SIGPIPE to Self (Pid $$)" kill -s SIGPIPE $$ echo "SIGPIPE Ignored" Actual Results: (Executed via rhnsd) # cat /tmp/test Sending SIGPIPE to Self (Pid 7069) SIGPIPE Ignored Expected Results: (Running Directly via Shell) #./test.sh Sending SIGPIPE to Self (Pid 7115) Broken pipe Additional info:
Off hand, I'm not sure why it's ignoring SIGPIPE. I inherited that code, so I'm bug the original author what the intent was.
Adrian, I origionally reported this bug via Red Hat Support ticket 487796. I was just wondering if there was a time schedule for a fix with this? Shawn
We really should look into the use cases for this bug.
Moving to the triage list
Disassociating from top-level tracking bug
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.