Once upon a time, Neal D. Becker <nbecker@xxxxxxx> said: > On Friday 06 June 2003 10:13 am, John Haxby wrote: > > The second part is slightly harder -- the resolver library needs to > > check to see if /etc/resolv.conf has changed and if it has, it needs to > > re-load it. > > Not sure what you mean here. If you change /etc/resolv.conf the result is > immediately seen when a new program is run. Do you mean that you also want > an already running program to see the change? (I'm not sure what the current > behaviour is in this case). The behaviour is that running programs continue to use to previous contents of /etc/resolv.conf. This can be a real problem, as that includes things like syslogd (some versions basically hang when they can't resolve IPs, and that can cause all kinds of other programs to hang when they try to log something). It would be nice if the resolver library would stat() /etc/resolv.conf periodically (no more than once per minute) to see if there has been a change. -- Chris Adams <cmadams@xxxxxxxxxx> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble.
