From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: 9fans@9fans.net
Subject: [9fans] Factotum discrepancy
Date: Thu, 25 Feb 2010 07:22:54 -0800 [thread overview]
Message-ID: <14515.98067.qm@web83904.mail.sp1.yahoo.com> (raw)
There appears to be a disagreement between the
factotum man page and its actual behavior regarding
the -a option. In the man page, the wording:
-a supplies the address of the authentication server to
use. Without this option, it will attempt to find an
authentication server by querying the connection
server, the file <mtpt>/ndb, and finally the network
database in /lib/ndb.
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.
BLS
next reply other threads:[~2010-02-25 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 15:22 Brian L. Stuart [this message]
2010-02-25 15:44 ` 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=14515.98067.qm@web83904.mail.sp1.yahoo.com \
--to=blstuart@bellsouth.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).