From: Eric Van Hensbergen <airwick@mail.csh.rit.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Almost there....
Date: Tue, 7 May 2002 19:01:33 -0500 [thread overview]
Message-ID: <1020816094.17514.6.camel@arlx125> (raw)
In-Reply-To: <1020814036.17514.4.camel@arlx125>
On Tue, 2002-05-07 at 18:27, Eric Van Hensbergen wrote:
> Ok, auth server is happy, file server is happy - Terminal booting off of
> auth server and file server is happy. Now, diskless CPU server.
> Everything looks good, except when I go for a cpu (or a cpu -h 9.3.61.43
> just to be sure), I get:
> cpu: negotiating authentication method: 9.3.61.43: i/o on hungup channel
>
> No real clues from looking at the logs, or turning on debug in
> factotum. Suggestions?
>
Ok, fixed it -- forgot to make the tcp17010 and 17007
executable....ooops. All better now...thanks again for your help
everyone...
-eric
next prev parent reply other threads:[~2002-05-08 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 23:27 Eric Van Hensbergen
2002-05-08 0:01 ` Eric Van Hensbergen [this message]
2002-12-20 17:54 Ish Rattan
2002-12-26 2:53 ` Russ Cox
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=1020816094.17514.6.camel@arlx125 \
--to=airwick@mail.csh.rit.edu \
--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).