SSSD / sssd

#53 Reread resolv.conf periodically or with inotify
Closed: Fixed Opened by sgallagh.

Closed: Fixed
Reopen Issue

SSSD will not currently reread /etc/resolv.conf if it is modified by NetworkManager, a VPN or other processes after it is started.

We need to monitor for changes to /etc/resolv.conf using either inotify (on supported platforms) or periodic polling and then run res_init() in all sssd_be processes.

Fields changed

status: new => assigned

Fixed in 7ac82a61aff588daaa1c217889b3055538380e47 and 9bec63f4b9cb97c1ff1cf2ff448446ab1e59734d

Fields changed

fixedin: => 0.5.0
resolution: => fixed
status: assigned => closed

Fields changed

rhbz: => 0

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

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

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
0.4.0
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.