On Tue, Jul 28, 2020 at 11:22:58AM -0500, Michael Catanzaro wrote:
> I agree we should not replace /etc/resolv.conf if it's not already a
> symlink (although this will not be a common case, since by default
> it is a symlink managed by NetworkManager).
>
> On Tue, Jul 28, 2020 at 11:07 am, Neal Gompa <ngompa13@xxxxxxxxx> wrote:
> >We can be smart here and replace the file when we detect that it's
> >managed by NetworkManager. Otherwise we won't replace it.
>
> Currently we actually don't touch it at all, which is not good
> because it means systemd-resolved will not be managing resolv.conf
> on upgraded systems. We should replace it with a symlink to systemd
> if (and only if) it's managed by NetworkManager.
Right now there's the following scriptlet:
grep -q 'Generated by NetworkManager' /etc/resolv.conf 2>/dev/null && \
echo -e '/etc/resolv.conf was generated by NetworkManager.\nConsider removing it to let systemd-resolved manage this file.' \
|| :
I.e. only a hint is emitted. I'm open to suggestions how to improve it.
Zbyszek
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
