Bug 84232 - application bug: screen(4014) has SIGCHLD set to SIG_IGN but calls wait4.
application bug: screen(4014) has SIGCHLD set to SIG_IGN but calls wait4.
Product: Red Hat Raw Hide
Classification: Retired
Component: screen (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Lon Hohberger
Brock Organ
Depends On: 84571
Blocks: 79578 84225
  Show dependency treegraph
Reported: 2003-02-13 13:06 EST by Tim Waugh
Modified: 2007-04-18 12:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-18 14:16:51 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Waugh 2003-02-13 13:06:16 EST
Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install kernel that warns.
2. Run screen.
Comment 1 Lon Hohberger 2003-02-14 13:24:44 EST
The place screen sets SIGCHLD to SIG_IGN is only in the exit path; I can't get
the above warning to actually occur.

Could someone else then test 3.9.13-4?   Dist-8.0.1-HEAD

Comment 2 Ingo Molnar 2003-02-14 14:35:31 EST
The message triggers with 3.9.13-4 as well. It does not trigger for every
startup of screen - i got 1 message out of 3 tries. I'm running screen as
non-root, over ssh. (perhaps this is a factor as well.)
Comment 3 Lon Hohberger 2003-02-18 09:00:42 EST
Indeed, it is.  Thanks for the additional information. Fix coming ASAP.
Comment 4 Lon Hohberger 2003-02-18 11:43:27 EST
The bug seen was in actually in utempter.  However, I have closed all obvious
windows where screen could exhibit the buggy behavior.  (Exit path, and during
the re-attach process).

3.9.13-5... will be in as soon as it finishes building.
Comment 5 Lon Hohberger 2003-02-18 14:16:51 EST
I tested this package a few (50 or so) more times with the latest build of
utempter - everything seems fine. Closing.

Note You need to log in before you can comment on or make changes to this bug.