[Pkg-utopia-maintainers] Bug#826366: Bug#826366: network-manager: does not remove resolv.conf symlink on package removal

Julian Gilbey jdg at debian.org
Wed Jun 8 09:47:05 UTC 2016


On Sun, Jun 05, 2016 at 11:44:35PM +0200, Michael Biebl wrote:
> Hi Julian

Hi Michael,

> Am 05.06.2016 um 01:56 schrieb Julian Gilbey:
> > [...]
> > 
> > So when network-manager shuts down, it should revert /etc/resolv.conf
> > to a regular file.  This should also be checked when the package is
> > removed (and unarguably when the package is purged).
> 
> I'm not convinced replacing /etc/resolv.conf on stop is a good idea, so
> I won't do that.
> [...]

Interesting point.  As /var/run/NetworkManager/resolv.conf still
exists after stop, it would be OK.  But if the machine is then
rebooted with network-manager still disabled, the problem resurfaces.

Question: If the symlink is reverted to an empty file on stop, but the
/var/run version is kept intact, would NM pick it up again on restart,
just by recreating the symlink?  Or does NM recreate the /var/run
version on startup anyway?  If either of these are the case, then it
seems that it would be fine to revert /etc/resolv.conf on stop, as it
should have no bad effects (and possibly some good ones).

Incidentally, it seems as though NM obliterates any previously
existing resolv.conf when it is first run, so there is no hope of
reinstating the previous version.  This does not seem ideal, either.

Best wishes, and thanks for your quick response.

   Julian



More information about the Pkg-utopia-maintainers mailing list