9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil and auth
Date: Sun, 20 Jul 2003 09:28:35 -0400	[thread overview]
Message-ID: <cc301e7ff18eed4074ccfa9f006deb88@plan9.bell-labs.com> (raw)
In-Reply-To: <20030720050244.GG63873@cassie.foobarbaz.net>

[-- Attachment #1: Type: text/plain, Size: 305 bytes --]

what authentication errors are you getting on the calling system?  In
a window, 'echo -n debug > /mnt/factotum/ctl' then 'cat /dev/kprint'.
In another window, try the attach.

Most likely, the caller doesn't know which auth server to use for
the auth domain of the file server and is just hanging up.

[-- Attachment #2: Type: message/rfc822, Size: 2334 bytes --]

From: Christopher Nielsen <cnielsen@pobox.com>
To: 9fans@cse.psu.edu
Subject: [9fans] fossil and auth
Date: Sat, 19 Jul 2003 22:02:44 -0700
Message-ID: <20030720050244.GG63873@cassie.foobarbaz.net>

I have setup a standalone fossil/venti fileserver. I also
have a standalone auth server.

When I try to attach to main on the fileserver, I am getting
authentication failures. There are no errors in the logs on
the auth server. The output on fscons is:

attach main as madhatter: phase error protocol phase error: read in state SNeedTicket

Any clues as to what I might have done wrong?

--
Christopher Nielsen
"They who can give up essential liberty for temporary
safety, deserve neither liberty nor safety." --Benjamin Franklin

  reply	other threads:[~2003-07-20 13:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20  5:02 Christopher Nielsen
2003-07-20 13:28 ` David Presotto [this message]
2003-07-21 14:13   ` Christopher Nielsen
2003-07-21 19:46     ` Christopher Nielsen
2003-07-21 21:40       ` Christopher Nielsen

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=cc301e7ff18eed4074ccfa9f006deb88@plan9.bell-labs.com \
    --to=presotto@closedmind.org \
    --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).