On Wednesday 06 April 2016, Patrick Shanahan wrote: > * Ruediger Meier <sweet_...@gmx.de> [04-06-16 16:03]: > > On Wednesday 06 April 2016, Patrick Shanahan wrote: > > > * Ruediger Meier <sweet_...@gmx.de> [04-06-16 13:07]: > > > > On Wednesday 06 April 2016, Patrick Shanahan wrote: > > > > > * Ruediger Meier <sweet_...@gmx.de> [04-06-16 10:45]: > > > > > > Hi, > > > > > > > > > > > > Since a few weeks I see nscd running crazy on 13.1, like > > > > > > this > > > > > > > > > > > > USER PR NI VIRT RES SHR S %CPU %MEM > > > > > > TIME+ COMMAND nscd 20 0 5265008 1.626g 652 S > > > > > > 0.000 5.185 0:30.32 nscd > > > > > > > > > > > > I guess 1.6G would be enough to cache all existing zones > > > > > > worldwide. What could be the problem? > > > > > > > > > > odd, mine has been up 261 days and: > > > > > > > > Could you show me your stats? I wonder if you have some > > > > reasonable cache hit rates. > > > > $ nscd -g > > > > > > nscd configuration: > > > > > > 0 server debug level > > > 42d 3h 27m 41s server runtime > > > > So it was restarted during uptime. Because of libc update, or > > crash? > > must have been libc update, I don't recall now,
> but not crash or > uptime would be less/reset ... Ah, I've ment nscd crash/restart, not whole system crash. Could be that OOM killer killed it. This happened on my other machine where nscd consumed more than 8GB! memory. cu, Rudi _______________________________________________ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
