From: a@9srv.net
To: 9fans@9fans.net
Subject: Re: [9fans] Authentication questions
Date: Tue, 6 May 2008 11:48:42 -0400 [thread overview]
Message-ID: <98788b107c295f7fed9237120bd0f2a0@9srv.net> (raw)
In-Reply-To: <050620081527.28522.482078D2000688D000006F6A22230650029B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net>
I'm not sure about the "usual" way, but I've got the
listens in cpurc commented out and rely only on
entries in /cfg/whatever/cpustart.
Does your cpustart listen specify -d as well as -t?
It looks like giving only -t should make it not try
(or re-try in your case) the non-trusted ones.
Anthony
next prev parent reply other threads:[~2008-05-06 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 18:47 Brian L. Stuart
2008-05-05 19:10 ` Christian Kellermann
2008-05-05 19:17 ` Brian L. Stuart
2008-05-05 20:07 ` Brian L. Stuart
2008-05-05 21:04 ` Steve Simon
2008-05-06 11:28 ` a
2008-05-06 15:19 ` Brian L. Stuart
2008-05-06 15:27 ` Brian L. Stuart
2008-05-06 15:48 ` a [this message]
2008-05-06 19:33 ` Brian L. Stuart
2008-05-06 16:09 ` 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=98788b107c295f7fed9237120bd0f2a0@9srv.net \
--to=a@9srv.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).