Bug 187078 - allow configurable killproc timeout
allow configurable killproc timeout
Status: CLOSED DUPLICATE of bug 198429
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
: FutureFeature, Reopened
Depends On:
Blocks: 184403
  Show dependency treegraph
 
Reported: 2006-03-28 05:43 EST by Joe Orton
Modified: 2014-03-16 22:59 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-07-30 13:02:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Joe Orton 2006-03-28 05:43:17 EST
Description of problem:
When shutdown by the init script, httpd has a race between the parent killing
the children, and the parent being killed by the SIGKILL from killproc.  If
there is a lazy/stuck child which refuses to die, killproc may win the race,
SIGKILL the parent, and leave orphaned children.  This is Undesirable Behaviour
(TM). 

This can be eliminated by allowing the httpd init script to specify the time
before the SIGKILL is sent.

(this is an RFE which I will hopefully get round to attaching a patch to RSN)
Comment 1 Miloslav Trmač 2006-07-28 20:04:39 EDT

*** This bug has been marked as a duplicate of 198429 ***
Comment 2 Joe Orton 2006-07-29 02:47:47 EDT
This is requested in RHEL4 to fix a bug in httpd, it's not just a feature. 
Otherwise I will have to duplicate all of killproc() in the httpd init script or
something.
Comment 3 Miloslav Trmač 2006-07-29 06:44:13 EDT
I'm sorry, it was filed against rawhide, so I had no way to know that.
Comment 4 Joe Orton 2006-07-30 13:02:53 EDT
Oh, sorry, my mistake - I forgot this was filed against Raw Hide, there is
already a separate RHEL4 bug (bug 198468).  Closing this again.

*** This bug has been marked as a duplicate of 198429 ***

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