From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] CPU Server Wiki, auth/keyfs,
Date: Sun, 27 Jul 2008 10:42:04 -0400 [thread overview]
Message-ID: <617142f08b85f205809714bff7c3b897@quanstro.net> (raw)
In-Reply-To: <3E858CEB-88B4-40CD-A81A-8B993FBA869E@gmail.com>
> brain# aux/9pcon -n il!192.168.0.108!9fs
> aux/9pcon: dial: connection rejected
does /net/il exist? you may want to check with snoopy
to make sure packets are making it out, too.
cs and a few other programs have had il-ectomies.
> The reason I'm boring you with that information, and the part I found
> interesting, is this. Just for the heck of it I selected my "CPU,
> File Server Root" option, i.e. I booted from 9pccpu instead of
> 9pccpuf. Of course, the CPU server reboots because there are no files
> on the file server yet, but I do seem to get past the il connection
> in this case. The file server says:
>
> il: allocating il!192.168.0.109!43095
> authentication failed: NeedTicket: unknown user
> hangup connection timed out-3 43095/192.168.0.109.17008
you need to enter "users default" at the fs console for initial connection.
if you have a non-standard hostowner, you will need to add that user
as well. (fs(8).)
once the user is place "flag authdisable" will disable authentication
if necessary. you must connect as a known user.
- erik
next prev parent reply other threads:[~2008-07-27 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 13:40 [9fans] CPU Server Wiki, auth/keyfs, and password for the machine g.pavelcak
2008-07-26 16:15 ` Russ Cox
2008-07-26 18:28 ` Gregory Pavelcak
2008-07-26 18:50 ` [9fans] CPU Server Wiki, auth/keyfs, erik quanstrom
2008-07-26 19:10 ` [9fans] CPU Server Wiki, auth/keyfs, and password for the machine Russ Cox
2008-07-27 13:33 ` Gregory Pavelcak
2008-07-27 14:42 ` erik quanstrom [this message]
2008-07-27 14:55 ` [9fans] CPU Server Wiki, auth/keyfs, Skip Tavakkolian
2008-07-27 15:40 ` Gregory Pavelcak
2008-07-27 16:48 ` erik quanstrom
2008-07-28 10:17 ` Gregory Pavelcak
2008-07-28 10:49 ` 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=617142f08b85f205809714bff7c3b897@quanstro.net \
--to=quanstro@quanstro.net \
--cc=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).