Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#41668 - [openresolv] unbound systemd patch results in deadlocks on shutdown
Attached to Project:
Arch Linux
Opened by Mantas Mikulėnas (grawity) - Saturday, 23 August 2014, 18:03 GMT
Last edited by Jan Alexander Steffens (heftig) - Sunday, 24 August 2014, 22:36 GMT
Opened by Mantas Mikulėnas (grawity) - Saturday, 23 August 2014, 18:03 GMT
Last edited by Jan Alexander Steffens (heftig) - Sunday, 24 August 2014, 22:36 GMT
|
DetailsWith openresolv 3.5.7-1, when NetworkManager is running + Unbound support is enabled in resolvconf.conf, a deadlock occurs during shutdown:
* systemd stops NetworkManager.service * NetworkManager runs `resolvconf -d NetworkManager` to clean up after itself * openresolv calls /usr/lib/resolvconf/unbound * resolvconf/unbound runs `systemctl reload-or-try-restart unbound` * `systemctl` blocks while waiting for the "unbound.service/reload" job * systemd continues waiting for "NetworkManager.service/stop" to finish Maybe fs33801.patch should be updated to use `systemctl --no-block` instead? |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Sunday, 24 August 2014, 22:36 GMT
Reason for closing: Fixed
Additional comments about closing: 3.5.7-2
Sunday, 24 August 2014, 22:36 GMT
Reason for closing: Fixed
Additional comments about closing: 3.5.7-2