public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dqarras at yahoo dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nscd/10181] New: nscd discards entries even with unlimited reload count Date: Thu, 21 May 2009 09:12:00 -0000 [thread overview] Message-ID: <20090521091220.10181.dqarras@yahoo.com> (raw) (Upstreamed from https://bugzilla.redhat.com/show_bug.cgi?id=488597) Description of problem: With the configuration below nscd seems to remove user info after a period of time (noticed both after 5 minutes and after 15 hours). I did something like this to test (using LDAP as info source): service ldap start [succeeds] service nscd start [succeeds] id testuser [succeeds] ls -l ~testuser [succeeds] service ldap stop [succeeds] id testuser [succeeds] ls -l ~testuser [succeeds] <wait, retry, wait, ...> id testuser [fails] ls -l ~testuser [fails] It seems that the time after which entries get removed is more or less random making it hard to identify any clear occurances causing this. This is important to allow laptops to work when not connected to the home network. server-user nscd debug-level 0 reload-count unlimited paranoia no enable-cache passwd yes positive-time-to-live passwd 600 negative-time-to-live passwd 20 suggested-size passwd 211 check-files passwd yes persistent passwd yes shared passwd yes max-db-size passwd 33554432 auto-propagate passwd yes enable-cache group yes positive-time-to-live group 600 negative-time-to-live group 60 suggested-size group 211 check-files group yes persistent group yes shared group yes max-db-size group 33554432 auto-propagate group yes I was able to reproduce this easily on Fedora 10 with all updates as of 2009-03-10 installed, including: root@localhost:~# rpm -q nscd nscd-2.9-3.i386 I will attach from Fedora 10 test /etc/nscd.conf, /var/log/nscd.log, and steps done in a terminal. -- Summary: nscd discards entries even with unlimited reload count Product: glibc Version: 2.10 Status: NEW Severity: normal Priority: P2 Component: nscd AssignedTo: drepper at redhat dot com ReportedBy: dqarras at yahoo dot com CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=10181 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2009-05-21 9:12 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-05-21 9:12 dqarras at yahoo dot com [this message] 2009-05-21 9:13 ` [Bug nscd/10181] " dqarras at yahoo dot com 2009-05-21 9:13 ` dqarras at yahoo dot com 2009-05-21 9:14 ` dqarras at yahoo dot com 2009-10-26 20:08 ` dqarras at yahoo 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=20090521091220.10181.dqarras@yahoo.com \ --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).