From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] File Server Authentication Woes
Date: Mon, 6 May 2002 21:03:56 -0400 [thread overview]
Message-ID: <b7f6dc8bbd8dc3a3ebddb1b88b94b1a3@plan9.bell-labs.com> (raw)
> I'm having a bit of trouble getting my newly installed file server to
> work with my Auth server. I've installed everything from scratch and
> have a stand-alone auth server, a stand-alone terminal, and a file
> server. Everything seems to be happy-happy except when I go to mount
> the file server from the auth-server I get an authentication error.
try
echo -n debug > /mnt/factotum/ctl
on the client and repeat the mount.
you'll get a trace of the factotum activity,
which may contain more useful error messages.
next reply other threads:[~2002-05-07 1:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 1:03 Russ Cox [this message]
2002-05-07 15:10 ` Eric Van Hensbergen
2002-05-07 9:30 ` plan9
-- strict thread matches above, loose matches on Subject: below --
2002-05-07 16:20 rsc
2002-05-07 17:26 ` Eric Van Hensbergen
2002-05-07 15:18 Russ Cox
2002-05-07 15:49 ` Eric Van Hensbergen
2002-05-07 1:17 presotto
2002-05-07 0:57 Eric Van Hensbergen
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=b7f6dc8bbd8dc3a3ebddb1b88b94b1a3@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).