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

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

resolution: => fixed
status: assigned => closed

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

2 years ago

Login to comment on this ticket.