Skip to content

fix(cmdeploy): stop and disable unbound-resolvconf - #953

Merged
missytake merged 1 commit into
chatmail:mainfrom
punkero-org:unbound-resolvconf
May 7, 2026
Merged

fix(cmdeploy): stop and disable unbound-resolvconf#953
missytake merged 1 commit into
chatmail:mainfrom
punkero-org:unbound-resolvconf

Conversation

@punkero-org

Copy link
Copy Markdown

Commit 825831e purges resolvconf, however the unbound service activates a 'wants' unit for async resolvconf updates. This results in errors in systemd startup as the unit will now always fail.

Stop and disable the unbound-resolvconf unit activation

Commit 825831e purges resolvconf, however the unbound service
activates a 'wants' unit for async resolvconf updates. This
results in errors in systemd startup as the unit will now always fail.

Stop and disable the unbound-resolvconf unit activation
@punkero-org

Copy link
Copy Markdown
Author

Side note: this is a trivial issue, it was only discovered as I was rebooting the relay to the newly released Debian kernel upgrade and reviewing my logs. The failure itself does not result in any changes to the system, /etc/resolv.conf stays as intended

@missytake missytake left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@missytake
missytake merged commit 129b8a2 into chatmail:main May 7, 2026
6 checks passed
@punkero-org
punkero-org deleted the unbound-resolvconf branch May 7, 2026 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants