SSSD / sssd

#1119 Monitor SIGKILL time should be configurable
Closed: Fixed Opened by sgallagh.

Closed: Fixed
Reopen Issue

If a process is unresponsive, send a SIGTERM to the old one. If it does not shut down in sixty seconds, we send SIGKILL. This wait period should be made a configurable option (to consider times when the backend might actually be in an uninterruptible state for more than 60s)

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.7.91 (1.8.0 beta 1)

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=771975

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=771975 771975]

Fields changed

milestone: SSSD 1.7.91 (1.8.0 beta 1) => SSSD 1.9.0

"Nice to have" for 1.9.

Fields changed

feature_milestone: =>
milestone: SSSD 1.9.0 => SSSD 1.9 beta
priority: minor => trivial
type: defect => enhancement

Fields changed

owner: sgallagh => jhrozek
patch: 0 => 1
status: new => assigned

master: b83e43eb88879c7fb3114aafcc525356ff7d4235

resolution: => fixed
status: assigned => closed

Metadata Update from @sgallagh:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.9.0 beta 1

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2161

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.
Metadata
None
None
None
Highest
enhancement
Service Monitor
master
0
1
https://bugzilla.redhat.com/show_bug.cgi?id=771975
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.