>The short answer is no. GLIBC is usually the code which reads
>/etc/resolv.conf and it re-reads the file each time, so any changes made
>to it take effect immediately.
>
>You can test this by running nslookup and see what your default nameserver
>is.
>Steve Borho Voice: 31
On Fri, 17 Dec 1999, Vidiot wrote:
> RedHat 6.0
>
> If I change /etc/resolv.conf, is there anything I need to "kill -1" in order
> for it to reread the file?
no
>
> I'd do a "man resolve", but I'm told the page doesn't exist and "man resolver"
> brings up the configuration layout for resolv.c
On Fri, Dec 17, 1999 at 10:55:04PM -0600, Vidiot wrote:
> RedHat 6.0
>
> If I change /etc/resolv.conf, is there anything I need to "kill -1" in order
> for it to reread the file?
The short answer is no. GLIBC is usually the code which reads
/etc/resolv.conf and it re-reads the file each time, s
RedHat 6.0
If I change /etc/resolv.conf, is there anything I need to "kill -1" in order
for it to reread the file?
I'd do a "man resolve", but I'm told the page doesn't exist and "man resolver"
brings up the configuration layout for resolv.conf and also references
resolve(3), which for some reas
