> -----Original Message----- > From: Nix [mailto:[EMAIL PROTECTED] > Sent: Sunday, August 31, 2008 5:12 PM > To: Marc Perkel > Cc: users@spamassassin.apache.org > Subject: Re: Handy script for generating /etc/resolv.conf > > On 28 Aug 2008, Marc Perkel told this: > > > Here's something I threw together to make sure the /etc/resolv.conf > > points to a working nameserver. I run this once a minute. > > How do you arrange that all the existing programs that have already > sucked in resolv.conf note the change? They're generally not going to > unless you restart them: nothing polls resolv.conf looking for changes > to it as far as I know, that would be far too inefficient.
Depending on the specific implementation of the resolver library, the application may check for changes in the resolv.conf file. Maybe they don't check at every and each resolv request, however: they may instead check for changes every, say, 10 secs or maybe every 1.000 requests. This way, looking for changes in the /etc/resolv.conf file is not that much inefficient... Giampaolo > > It checks to > > see what name servers are up and creates /etc/resolv.conf. As you all > > know SA and mail servers need the first nameserver to always be > > working. > > But these are both root-owned daemons and you're not restarting any > of them.
