From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: unmatched replies
Date: Thu, 17 Oct 1996 00:49:59 +0100 [thread overview]
Message-ID: <19961016234959.kmyOZqrxbG6Ce2wx9e6bJnwyStdtbiK8p70rYxmjCIs@z> (raw)
the `unmatched reply' diagnostic is easy to generate by
interrupting a (user level) file server that queues requests and replies
to them out of issuing order but doesn't (quite) cope with Tflush/Rflush.
p9auth% mail 9fans
subject: unmatched replies
the `unmatched reply' diagnostic is easy to generate by
interrupting a (user level) file server that queues requests and replies
to them out of issuing order but doesn't (quite) cope with Tflush/Rflush.
rflush(void) /* synchronous so easy */
is sometimes a clue.
dnsiplookup in ndb/cs might be a good place to start looking in your case,
but i'm just guessing.
it depends what you were trying to do when you noticed that the routing
tables had changed ...
next reply other threads:[~1996-10-16 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-16 23:49 forsyth [this message]
1996-10-17 2:47 Scott
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=19961016234959.kmyOZqrxbG6Ce2wx9e6bJnwyStdtbiK8p70rYxmjCIs@z \
--to=forsyth@plan9.cs.york.ac.uk \
/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).