#895 SSSD should fall back to polling resolv.conf if inotify breaks
Closed: Fixed None Opened 10 years ago by sgallagh.

Right now, if inotify is in use when SSSD starts up, if at any time it stops being available (such as if the maximum number of inotify watches is reached), SSSD will self-terminate.

Instead, we should detect the failure and fall back to the five-second polling approach that we would follow if inotify had been initially unsupported.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.5.9

Fields changed

owner: somebody => jhrozek

Jakub is on vacation. Reassigning to Jan as this is high priority.

owner: jhrozek => jzeleny

Fixed by:
- 203b6bc (master)
- dedabcb (sssd-1-5)

patch: 0 => 1
resolution: => fixed
status: new => closed

Fields changed

rhbz: => 0

Metadata Update from @sgallagh:
- Issue assigned to jzeleny
- Issue set to the milestone: SSSD 1.5.9

4 years ago

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

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.

Login to comment on this ticket.

Metadata