9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Factotum discrepancy
Date: Thu, 25 Feb 2010 10:44:13 -0500	[thread overview]
Message-ID: <756e179ca9a5019048abd2683adc8e0d@brasstown.quanstro.net> (raw)
In-Reply-To: <14515.98067.qm@web83904.mail.sp1.yahoo.com>

> makes it sound like the -a option takes precedence
> over cs and ndb.  But the code for _autdial() in
> util.c looks for cs first and if it's there, the
> -a option is ignored.  (In p9p, -a seems to be ignored
> altogether.)
>
> Which way should it be?  I'd prefer if -a took precedence,
> but if the existing behavior is really what's wanted,
> then I suggest we change the man page so it's more clear
> that's what's happening.

it seems like this code is being very sly.
i think the problem the code is working around
is that if you first connect to the local machine
and later want to mount sources, you will fail
since the auth server you've specified in -a won't
auth sources.  (at least that's how i read the comment,
if i squint a bit.)

also, if you were to smarten up -a to take an
authdom / authserver pair, e.g. -a coraid.com!tyty.coraid.com
it could still cause trouble if ndb were updated
while you were running  one would expect cs to
fix things up, but it wouldn't.

is this a problem with a 9vx setup?  perhaps
getting cs looking at the right data is the real
problem?

- erik



      reply	other threads:[~2010-02-25 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 15:22 Brian L. Stuart
2010-02-25 15:44 ` erik quanstrom [this message]

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=756e179ca9a5019048abd2683adc8e0d@brasstown.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).