From: Scott Schwartz schwartz@galapagos.cse.psu.edu
Subject: unmatched replies
Date: Wed, 16 Oct 1996 22:47:44 -0400 [thread overview]
Message-ID: <19961017024744.kr-fhnZEVOi8XSK7jWBZxLH0LRQ3ECdv67pyE3rZ2IU@z> (raw)
forsyth@plan9.cs.york.ac.uk writes:
| 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.
That sounds familiar: I was interrupting things, like new instances of
telnet which had hung waiting for packets to come back. (This is over
ppp, so I could see from the LEDs that there weren't any.)
| dnsiplookup in ndb/cs might be a good place to start looking in your case,
| but i'm just guessing.
That's plausible, I agree. Once things got confused, starting a new
telnet would induce the error message, and a name lookup is pretty much
the first thing it does.
| it depends what you were trying to do when you noticed that the routing
| tables had changed ...
Pretty much just trying to log in again.
next reply other threads:[~1996-10-17 2:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-17 2:47 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-10-16 23:49 forsyth
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=19961017024744.kr-fhnZEVOi8XSK7jWBZxLH0LRQ3ECdv67pyE3rZ2IU@z \
--to=9fans@9fans.net \
/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).