public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redhat at flyn dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nscd/2132] Use nscd to support disconnected LDAP operation
Date: Tue, 10 Jan 2006 01:39:00 -0000 [thread overview]
Message-ID: <20060110013931.11531.qmail@sourceware.org> (raw)
In-Reply-To: <20060109232507.2132.redhat@flyn.org>
------- Additional Comments From redhat at flyn dot org 2006-01-10 01:39 -------
Right. However, imagine I set my cache TTL to 30 days. This will allow me to
operate my laptop away from my LDAP server for 30 days. However, if I do
connect my laptop to the LDAP server it will continue to use cached data. So if
the network administrator changes some NSS data, this change will not propagate
to my laptop until my 30 TTL expires, even if I connect my laptop to the network
before then.
This is why I am wondering if two TTL's would be more appropriate.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WORKSFORME |
http://sourceware.org/bugzilla/show_bug.cgi?id=2132
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2006-01-10 1:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 23:25 [Bug nscd/2132] New: " redhat at flyn dot org
2006-01-09 23:41 ` [Bug nscd/2132] " drepper at redhat dot com
2006-01-10 1:39 ` redhat at flyn dot org [this message]
2006-01-10 3:02 ` drepper at redhat dot com
2006-02-12 15:24 ` redhat at flyn dot org
2007-02-18 4:49 ` drepper at redhat dot com
2007-04-05 14:10 ` costinel at gmail dot com
2007-04-05 14:25 ` costinel at gmail dot com
2009-10-22 3:33 ` brian at interlinx dot bc dot ca
2009-10-24 14:22 ` brian at interlinx dot bc dot ca
2009-10-24 15:07 ` brian at interlinx dot bc dot ca
2009-10-25 22:51 ` drepper at redhat dot com
2009-10-26 20:09 ` dqarras at yahoo dot com
2009-10-27 13:59 ` howard at cohtech dot com
2009-11-01 14:49 ` arthur at arthurdejong dot org
2009-11-01 17:48 ` dqarras at yahoo dot com
[not found] <bug-2132-131@http.sourceware.org/bugzilla/>
2011-09-17 14:12 ` dqarras at yahoo dot com
2012-05-03 19:14 ` dqarras at yahoo dot com
2013-01-21 3:29 ` carlos at systemhalted dot org
2014-02-16 17:43 ` jackie.rosen at hushmail dot com
2014-05-28 19:46 ` schwab at sourceware dot org
2014-05-28 19:46 ` schwab at sourceware dot org
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=20060110013931.11531.qmail@sourceware.org \
--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: link
Be 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).