On Mon, Dec 07, 2009 at 05:33:59AM -0800, John Thomas wrote: > Possibly fixed. There is possibly a bad entry in the nscd cache. > Restarting nscd did not solve the problem until I changed /etc/nscd.conf > from: enable-cache hosts yes > to: enable-cache hosts no > > I am not sure why restarting (machine and/or nscd daemon) did not clear > the cache. /var/db/nscd is the persistent cache location - you need to clear that out after stopping nscd if you want to clear the cache. -- rgds Stephen _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: Name Resolution Broken for One Address
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: CentOS mailing list <centos@xxxxxxxxxx>
- Subject: Re: Name Resolution Broken for One Address
- From: Stephen Harris <lists@xxxxxxxxxx>
- Date: Mon, 7 Dec 2009 08:43:10 -0500
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <4B1D0447.3080703@xxxxxxxxxxxx>
- References: <4B1CFC14.8080202@xxxxxxxxxxxx> <4B1D0447.3080703@xxxxxxxxxxxx>
- User-agent: Mutt/1.4.2.2i
- References:
- Name Resolution Broken for One Address
- From: John Thomas
- Re: Name Resolution Broken for One Address
- From: John Thomas
- Name Resolution Broken for One Address
- Prev by Date: Re: CentOS 5.4 x86_64 only detects 32GB RAM while Fedora x86_64 correctly lists 128GB
- Next by Date: Re: Inquiry:How to compare two files but not in line-by-line basis?
- Previous by thread: Re: Name Resolution Broken for One Address
- Next by thread: Re: Name Resolution Broken for One Address
- Index(es):
 |