From: Steve Kotsopoulos steve@ecf.toronto.edu
Subject: setting up a cpu server
Date: Tue, 31 May 1994 16:34:45 -0400 [thread overview]
Message-ID: <19940531203445.XiaqpJ1yTzzTXL4FLO3YOLTw0zzJvsvqxtJ_tIFkTxg@z> (raw)
I have 2 Magnums, one is a terminal, the other is a cpu server.
Both use u9fs as their file server.
When I try to telnet into the cpu server, the connection closes right away.
I get the following message in /sys/log/listen:
plan9: May 31 12:28:20: bootes: aux/listen: tcp call for tcp23 on chan /net/tcp/3
Other tcp services don't work either (similar messages in logfile).
When I try to use the 'cpu' command on the terminal, it prints:
cpu: can't read server challenge: plan9: file does not exist
And I see the following message in /sys/log/listen:
plan9: May 31 12:28:47: bootes: aux/listen: il call for il17005 on chan /net/il/2
UDP services such as bootp and tftp seem to work fine, as I can boot the
terminal from the cpu server.
How can I get cpu & TCP services to work?
Steve
reply other threads:[~1994-05-31 20:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19940531203445.XiaqpJ1yTzzTXL4FLO3YOLTw0zzJvsvqxtJ_tIFkTxg@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).