Red Hat Bugzilla – Bug 428029
killproc waiting granularity
Last modified: 2014-03-16 23:11:57 EDT
Attached patch implements more granular waiting
for process termination (which sometimes may
speed up `init.d/script stop` execution)
Created attachment 291081 [details]
killproc waiting granularity patch
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Some feedback about this bug?
Fedora Bugzappers volunteer triage team
Created attachment 335539 [details]
Another patch solving this problem.
I was just about to file the same request, this would be really nice to merge. I'm also attaching another patch, you can review both.
The motivation is as follows: I'm maintaining boinc-client which sometimes takes a lot of time (even more than 10 seconds) to properly quit as it has to store its computation status. Moreover, killing by SIGKILL can lose the computed results which we definitely need to avoid => I've to use "-d 10" for killproc. This is much more than needed in most cases, while in some small percent it might not even be enough. Trying to kill by SIGTERM periodically until $delay amount of time makes really sense.
Thanks for consideration in advance.
Bill, could you express yourself about the proposed change? I know you're probably short on time, but even letting us know in a way "yes, this should be done, I'll review the patches later" or "no, this is plain nonsense" would be nice. Thanks.
Yeah, I suck. The idea's reasonable.
Merged, way too late, in http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=9369bf1568b73061fe29670b4faae80c6507d56f.
initscripts-9.26-1.fc15 has been submitted as an update for Fedora 15.
initscripts-9.26-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
As far as I understand this bug is still actual in RHEL 6.3.
Will it be resolved ....?
(In reply to George Rafaelov from comment #11)
> Hi guys,
> As far as I understand this bug is still actual in RHEL 6.3.
> Will it be resolved ....?
Yes, this issue is fixed in RHEL in 9.03.39-1, sometime after RHEL 6.3.