Re: bin/48379: resolv.conf symlink changes not picked up by resolver

[David Brownlee <abs%absd.org@localhost>]

The following reply was made to PR bin/48379; it has been noted by GNATS.

From: David Brownlee <abs%absd.org@localhost>
To: "gnats-bugs%netbsd.org@localhost" <gnats-bugs%netbsd.org@localhost>
Cc: "gnats-admin%netbsd.org@localhost" <gnats-admin%netbsd.org@localhost>, 
netbsd-bugs%netbsd.org@localhost
Subject: Re: bin/48379: resolv.conf symlink changes not picked up by resolver
Date: Wed, 13 Nov 2013 17:44:21 +0000

 On 13 November 2013 17:35, Joerg Sonnenberger 
<joerg%britannica.bec.de@localhost> wrote:
 > The following reply was made to PR bin/48379; it has been noted by GNATS.
 >
 >  > >Synopsis:       resolv.conf symlink changes not picked up by resolver
 >
 >  I don't think it is reasonable to expect that to work.
 >  The system would have to monitor not only the symlink, but e.g. all
 >  directories involved. Consider
 >
 >  /etc/resolv.conf -> /a/b
 
 I would have thought checking readlink() plus dev+ino would be pretty
 comprehensive.
 
 The PR was a followup to a question from Christos. I'd also be quite
 happy if the current mechanism and limitations was documented in
 resolver(3) or similar - right now from a user perspective its just
 magic. Very cool magic, but undocumented and uncertain in the face of
 symlinks.