🚀 go-pugleaf

In article <6jSr4.4317$uT1.91132@nnrp4.clara.net> Mike Mann <mike@kempston.net> writes:
>In article <88olvn$l87$2@axalotl.demon.co.uk>, huge@nospam.huge.org.uk
>(Huge) wrote:
>>Ah. Hang on. nscd.conf contains a line;
>>
>>        enable-cache            hosts           no
>>
>On the whole, I find it's desirable to switch off host caching in
>nscd.  There's one exception: recent versions of Netscape seem to have
>a bug whereby on some systems, it fails to do any name lookups
>successfully unless nscd is configured to cache hostnames.  On other
>systems, it works perfectly without nscd and I've never been able to
>track down why it Netscape requires nscd on some systems but not on
>others.

Just my luck - I think I've been bitten by this one too. I cried success
before I'd tested the system enough. I too seem to find that with nscd killed
off or running without host caching, Netscape won't play ball.
What I have done as a trial is re-enabled host caching, but upped the
timeouts massively and 'allowed old data' this seems to allow nscd to run
without re-checking. It might be that I can set the timeouts to normal levels
in practice - after one day's testing the number of dialups is vastly reduced,
so much that it hasn't connected often enough!

jsm