The 02.11.23 at 10:45, zentara wrote:

Maybe try stopping nscd (Name Service Cache Daemon) in services, you don't need it if you don't run your own DNS. Mozilla runs fine for me here.

Nscd doesn't have much to do with DNS; it caches passwd, group, hosts, etc. -- Cheers, Carlos Robinson

On Mon, 25 Nov 2002 03:25:58 +0100 (CET) "Carlos E. R." wrote:

The 02.11.23 at 10:45, zentara wrote:

...

Maybe try stopping nscd (Name Service Cache Daemon) in services, you don't need it if you don't run your own DNS. Mozilla runs fine for me here.

Nscd doesn't have much to do with DNS; it caches passwd, group, hosts, etc.

The reason I mentioned it, was the OP said the first error message was "VM killed nscd" as his machine was running out of memory. I always turn that nscd off on my dialup machine. So what does it actually do for you.? A few releases back, the only option to turn it off was to actually remove the startup script. I'm slightly paranoid about services which startup automatically, and don't seem to serve any useful purpose. (or things still run fine without them). So does nscd make things run faster, or does it just take up ram? The NOTES section in man nscd does indicate that the nscd daemon does have an inter-relationship with DNS, which may even have contributed to his problem. -- use Perl; #powerful programmable prestidigitation

The 02.11.25 at 08:41, zentara wrote:

...

Nscd doesn't have much to do with DNS; it caches passwd, group, hosts, etc.

The reason I mentioned it, was the OP said the first error message was "VM killed nscd" as his machine was running out of memory.

I don't know what exact strategy does the kernel use for deciding what to kill first when it is short in memory.

I always turn that nscd off on my dialup machine. So what does it actually do for you.?

There is a configuration file, /etc/nscd.conf. It caches passwd, group, and host queries (meaning dns queries), which probably should be disabled if you run dns locally - in suse 8.1 they are disabled by default, thus what I said initially. But I suppose if you don't use bind, and you have a modem conection, you could get faster network responses enabling nscd dns (hosts) caching. In fact, netscape had its own dns caching helper for that very reason. Right now, I have enabled its log file, I want to know more of what it's reallly doing. I would really like to know what is the impact of caching paswd/group queries :-?

A few releases back, the only option to turn it off was to actually remove the startup script. I'm slightly paranoid about services which startup automatically, and don't seem to serve any useful purpose. (or things still run fine without them).

I know :-) I think I disabled it somehow in 7.1 or 7.3, but I don't remember how.

So does nscd make things run faster, or does it just take up ram?

Maybe both.

The NOTES section in man nscd does indicate that the nscd daemon does have an inter-relationship with DNS, which may even have contributed to his problem.

Yes, but I think Suse default for most versions have been to disable dns queries. -- Cheers, Carlos Robinson