From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] time to accept swap
Date: Fri, 19 Jul 2002 06:34:03 +0100 [thread overview]
Message-ID: <2a9d01e11925ce299e50451d7275090c@caldo.demon.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 291 bytes --]
yes, it was doing a DNS query to try to resolve the invented domain.
you could make /lib/ndb/local authoritative for that domain, and then
you could use the domain as you like. it has been years since i
last had to do ndb from scratch, but i think
dom=<fake domain> soa
will do it.
[-- Attachment #2: Type: message/rfc822, Size: 1909 bytes --]
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] time to accept swap
Date: Thu, 19 Jul 2001 00:52:20 +0900
Message-ID: <a4ec8763ddeab53d0da319bf1d074ebc@granite.cias.osakafu-u.ac.jp>
>% ndb/csquery
>> net!$auth!ticket
term% net!$auth!ticket
> net!$auth!ticket
/net/tcp/clone 192,.168.1.11!567
I see no problem from this answer???
By the way, from the hints by Charles and Dave, I re-examined my
/lib/ndb/local file, and found a line
auth=diabase.<fake domain> authdom=<fake domain>
where <fake domain> should be read replaced by something.
Then, I changed the line to
auth=diabase authdom=<fake domain>
Now, the slow authentication problem is gone.
Thanks all!
Kenji
next reply other threads:[~2002-07-19 5:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 5:34 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-18 13:22 presotto
2002-07-29 15:58 ` Don
2002-07-18 10:42 forsyth
2002-07-18 9:12 forsyth
2002-07-18 0:14 okamoto
2002-07-17 22:40 okamoto
2001-07-18 22:20 okamoto
2001-07-18 15:52 okamoto
2001-07-15 17:56 okamoto
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=2a9d01e11925ce299e50451d7275090c@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).