SSSD / sssd

#1602 provider is forcibly killed with SIGKILL instead of SIGTERM if it's not responding
Closed: Fixed Opened by jhrozek.

Closed: Fixed
Reopen Issue

We only read the configured SIGKILL time for services and actually used the value of 0, which actually translated into tevent_schedule_immediate. That meant that after we sent the SIGTERM we also sent a SIGKILL right away, which is bad...

Fields changed

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

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.3

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=771975 (Red Hat Enterprise Linux 6)

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=771975 771975]
  • sssd-1-9: 851d0158241fcc0a0796682c43f9e5ca8f2fb673
  • master: 31d97bce8f113276bf73c7d4349f720cd5edbcb8

resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.9.3

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/2644

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
Normal
defect
SSSD
1.9.2
0
1
https://bugzilla.redhat.com/show_bug.cgi?id=771975
0
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.