Subject: Re: re-reading /etc/resolv.conf on change
To: None <>
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
List: tech-userlevel
Date: 01/01/2004 16:49:02
>> I don't know if it's considered to be too expensive to do it for
>> each resolver call (but I gess we could as well reread the
>> resolv.conf file then :)
> It would be too expensive for each call I think - but also
> unnecessary.  Once every N seconds would be plenty.

Except that that means determining when N seconds have passed.

That means either a syscall to get the time or some kind of input-based
time notification like AF_TIMER sockets - though even then it takes
some care to avoid an extra syscall overhead in the common case.
(Incidentally, as a coder, I purely love AF_TIMER and can barely
understand how I lived without it.)

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B