> > why stat it?  you wanna reload it?  i've been known to exploit the
> > fact that it won't get reloaded so that applications get different
> > sets of name servers.
> > 
> > yes, there's chroot, but no, that's not really an answer for, say,
> > netscape.
>
>I suppose you could always add support for passing an envronment variable
>which pointed to the other name servers...

actually, being about to pass an environment variable to tweak that,
and the timeouts, and some other options (like...usevc perhaps?) would
be really neat.  there's LOCALDOMAIN and RES_OPTIONS now, but
HOSTALIASES is gone.  :(

>In any case, your use is almost certainly an unintended use, and there
>are a great many situations where a nameserver might change, but the
>mission-critical server which uses it CANNOT be rebooted.

yup.  i'm a loony.  i'm just pointing out that someone's "bug" can
sometimes be someone else's "feature".

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
werdna@squooshy.com       * "information is power -- share the wealth."