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

[Alan Barrett <apb%cequrux.com@localhost>]

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

From: Alan Barrett <apb%cequrux.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: bin/48379: resolv.conf symlink changes not picked up by resolver
Date: Wed, 13 Nov 2013 21:42:05 +0200

 On Wed, 13 Nov 2013, Joerg Sonnenberger wrote:
 > 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
 >
 > and someone renames a. This is a classic case of "Don't do this" for
 > me...
 
 I agree that noticing such changes immediately is unreasonable, 
 but the resolver code could stat("/etc/resolv.conf") every now and 
 again and notice changes in st_dev or st_ino.  It might as well 
 look at st_mtime and st_size at the same time, as a safety net in 
 case kqueue is broken or not available.
 
 --apb (Alan Barrett)