From: David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Grazvydas Ignotas <notasas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
Pavel Shilovsky
<piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Jeff Layton <jlayton-vpEMnDpepFuMZCB2o+C8xQ@public.gmane.org>
Subject: Re: DNS resolver cache does not expire
Date: Tue, 28 Jun 2011 11:10:47 +0100 [thread overview]
Message-ID: <20945.1309255847@redhat.com> (raw)
In-Reply-To: <BANLkTinN0pXZsPADfzvO8p+Jf0i3tWtKpw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Grazvydas Ignotas <notasas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> So in my case it's cifs.upcall that doesn't set the timeout I guess,
> as contents of my /etc/request-key.conf are:
Indeed. In any case, the kernel doesn't know about the TTL userspace received
received from the DNS server, so userspace has to tell the kernel somehow.
David
prev parent reply other threads:[~2011-06-28 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 14:19 DNS resolver cache does not expire Grazvydas Ignotas
[not found] ` <BANLkTim+Phg+cY6_KAhxhfSeDj1td_GALw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-23 19:15 ` Pavel Shilovsky
[not found] ` <BANLkTikbk1yvwWCvhmqdH1DHZN1PPEz+hw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-23 19:48 ` Steve French
2011-06-23 20:14 ` Jeff Layton
2011-06-27 12:34 ` David Howells
[not found] ` <21187.1309178053-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-06-27 17:27 ` Pavel Shilovsky
[not found] ` <BANLkTikOq_dT1SF9aZ=0DNdoVOngvygfZw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-27 19:42 ` David Howells
[not found] ` <28505.1309203730-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-06-28 9:47 ` Grazvydas Ignotas
[not found] ` <BANLkTinN0pXZsPADfzvO8p+Jf0i3tWtKpw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-28 10:10 ` David Howells [this message]
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=20945.1309255847@redhat.com \
--to=dhowells-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=jlayton-vpEMnDpepFuMZCB2o+C8xQ@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=notasas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.