From: geoff@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: [9fans] dns changes
Date: Mon, 5 Mar 2007 13:33:46 -0500 [thread overview]
Message-ID: <0381bfcb7eaa86a4876663db6c2960be@plan9.bell-labs.com> (raw)
I've pushed to sources changes to ndb/dns intended to improve the
effectiveness of its caching. Thanks to Dave Presotto for locating
the specific problems.
I've also attempted to make dns's diagnostics in /sys/log/dns more
specific, to pinpoint the client sending bad requests and to detail
the errors in the requests. Some of the diagnostics are still
somewhat cryptic; I plan to improve them as we get more experience
with them. Some errors characteristic of MS Windows are detected and
not logged to avoid filling the logs with complaints about systems
that cannot be fixed (except by an OS upgrade). Seriously
misformatted DNS requests now draw replies with error flags set, so
clients at least get feedback that they are in error.
dns processes now have their names (visible with ps -a) set to
indicate what they are doing. The internal %R formatting code is now
more robust against incomplete Req structures being printed.
ndb(8) has been updated to reflect all this and had its formatting
slightly altered to improve legibility.
next reply other threads:[~2007-03-05 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 18:33 geoff [this message]
2007-03-05 19:18 ` erik quanstrom
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=0381bfcb7eaa86a4876663db6c2960be@plan9.bell-labs.com \
--to=geoff@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).