public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "siddhesh at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nscd/13931] New: Reload nscd cache entry even if its timeout is equal to the current time Date: Fri, 30 Mar 2012 11:10:00 -0000 [thread overview] Message-ID: <bug-13931-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13931 Bug #: 13931 Summary: Reload nscd cache entry even if its timeout is equal to the current time Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: nscd AssignedTo: unassigned@sourceware.org ReportedBy: siddhesh@redhat.com CC: drepper.fsp@gmail.com Classification: Unclassified With the current implementation of cache expiry, the timer for expiry is set exactly at the timeout value of an entry. As a result, there is often a case where the cache prune is called at exactly the timeout time, causing the prune_cache code to think that the timeout has not occurred yet. As a result, the entry is not invalidated or reloaded until the next prune cycle, which is at least 15 seconds away. Fix is to mark an entry as timed out even when the time that prune_cache is called is exactly equal to the timeout time of the entry. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-03-30 10:53 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-30 11:10 siddhesh at redhat dot com [this message] 2012-03-30 12:31 ` [Bug nscd/13931] " siddhesh at redhat dot com 2014-06-25 11:25 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-13931-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).