From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] upgrading a 3rd edition network -- fairly long message
Date: Thu, 2 May 2002 23:26:32 +0200 [thread overview]
Message-ID: <200205022126.g42LQXa27590@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Thu, 02 May 2002 15:18:27 -0600." <210fa94f74190eed2bbd582956d4b6d3@acl.lanl.gov>
Demo effect :-) I tried again, and it now works, several reboots of
the cpu/auth server since I tried before. I dont' recall exactely
what I changed; I think at one point I added in /lib/ndb/local
an authdom=my-auth-dom attribute to the record that also has
the auth=... attribute; wonder whether that made the difference?
Axel.
> I'm using the 3e drawterm on freebsd to connect to a 4e cpu/auth server
> no problems.
next prev parent reply other threads:[~2002-05-02 21:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 21:18 dpx
2002-05-02 21:26 ` Axel Belinfante [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-02 22:28 Russ Cox
2002-05-02 21:31 Russ Cox
2002-05-02 21:47 ` Axel Belinfante
2002-05-02 22:25 ` John Packer
2002-05-02 21:16 Russ Cox
2002-05-02 2:38 dpx
2002-05-02 20:56 ` Axel Belinfante
2002-04-30 10:10 forsyth
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=200205022126.g42LQXa27590@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--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).