Date: Tue, 8 Oct 2013 08:15:26 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: munin related Message-ID: <alpine.BSF.2.00.1310080808140.70367@mail.fig.ol.no> In-Reply-To: <12BA615C8BF048EAA9C5961448988DAF@yahoo.com> References: <1380991485.82917.YahooMailNeo@web160503.mail.bf1.yahoo.com> <20131007155554.GB5343@dan.emsphone.com> <12BA615C8BF048EAA9C5961448988DAF@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --2055831798-292674840-1381212926=:70367 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT On Mon, 7 Oct 2013 19:57+0200, Laszlo Danielisz wrote: > Yep killing nscd help me to get out of this trouble. I have long suspected nscd to reinitialise the timers whenever an entry is requested while still held in the cache, be it a positive or a negative result. As such the only reasonable solution is to never cache negative results (TTL=0) and keep the positive TTL relatively short, say no more than 60 minutes. Can someone more knowledgeable on nscd internals confirm my suspicion? -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ --2055831798-292674840-1381212926=:70367--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1310080808140.70367>