Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Don't mask resolved systemd unit #455

Merged
merged 2 commits into from
Apr 26, 2024
Merged

fix: Don't mask resolved systemd unit #455

merged 2 commits into from
Apr 26, 2024

Conversation

SuperSandro2000
Copy link
Member

No description provided.

servcesi.resolved.enable is false by default and masking the systemd
unit just makes it hard to activate if desired.
@nzbr
Copy link
Member

nzbr commented Apr 19, 2024

Why would we want resolved to be enabled? I just checked and saw that Ubuntu has it enabled as well, but what do we gain from it?

@SuperSandro2000
Copy link
Member Author

For example when using tailscale. It regularly breaks when opening new tabs and complains about changed resolve.conf. I think WSL might try to change the file under it's foot and then things don't work anymore.

@nzbr nzbr merged commit 0b90c1d into main Apr 26, 2024
25 checks passed
@nzbr nzbr deleted the resolved branch April 26, 2024 04:16
@nzbr nzbr added the bug Something isn't working label Jul 7, 2024
@nzbr nzbr changed the title Don't mask resolved systemd unit fix: Don't mask resolved systemd unit Jul 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants