From: john@csplan9.rit.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] terminals and /lib/ndb/local
Date: Tue, 15 Jan 2008 19:11:07 -0500 [thread overview]
Message-ID: <ab0fd3e2c33fbf86271123ba6cabeb74@csplan9.rit.edu> (raw)
In-Reply-To: <780a18048fb5bb76555d3c6eea25cf7f@csplan9.rit.edu>
>>> Sorry, I didn't specify. plan9 is the auth server; csplan9 is my machine
>>> at RIT.
>>> Ron just discovered that somewhere in my recent changes I make drawterm
>>> stop working; I'm sure that's got something to do with the cpu problems. I've
>>> since done "yesterday" and pulled in a working version, so now here's what
>>> we're using:
>>>
>>> auth=sources.cs.bell-labs.com authdom=outside.plan9.bell-labs.com
>>> auth=out9auth.cs.bell-labs.com authdom=cs.bell-labs.com
>>> auth=csplan9.rit.edu authdom=rit.edu
>>> auth=plan9 authdom=ca.sandia.gov
>>>
>>> sys=go dom=go.cs.bell-labs.com
>>> sys=csplan9 dom=csplan9.rit.edu
>>>
>>
>> since you say
>> sys=csplan9 dom=csplan9.rit.edu
>> then you say
>> auth=csplan9.rit.edu authdom=rit.edu
>> i'm pretty sure you've declared that csplan9 is its own
>> authentication server.
>>
>> - erik
>
> Yeah, it is. It's a cpu/auth/file server sitting at RIT. I shouldn't even have
> included that in my mail, since it's not very important to the problem.
> Basically, csplan9 is in there because I want to use it. Nobody else here
> has an account on it or ever connects.
>
> John
Ok, I think I've solved the problem. I hadn't given an IP for plan9, which
was a relic from before the server had a static IP. Giving it a static IP
makes everything seem to work; my current local file is appended,
although it still probably has some unneeded things in it.
John
#
# files comprising the database, use as many as you like, see ndb(6)
#
database=
file=/lib/ndb/local
file=/lib/ndb/common
auth=sources.cs.bell-labs.com authdom=outside.plan9.bell-labs.com
auth=csplan9.rit.edu authdom=rit.edu
auth=out9auth.cs.bell-labs.com authdom=cs.bell-labs.com
sys=go dom=go.cs.bell-labs.com
sys=csplan9 dom=csplan9.rit.edu
authdom=ca.sandia.gov auth=plan9
ipnet=9net ip=192.168.18.0 ipmask=255.255.255.0
fs=plan9.ca.sandia.gov
cpu=plan9.ca.sandia.gov
auth=plan9.ca.sandia.gov
ipgw=192.168.18.10
dnsdomain=ca.sandia.gov
# authdom=ca.sandia.gov
dns=192.168.18.10
dns=140.246.250.1
sys=plan9 dom=plan9.ca.sandia.gov ip=192.168.18.13
dom=plan9.ca.sandia.gov
auth=plan9.ca.sandia.gov
sys=ramac ip=192.168.18.179 ether=001641e0fcfd
sys=gnot ether=001b210f7faa
ip=192.168.18.90
# ipgw=192.168.18.10
dom=gnot.ca.sandia.gov
bootf=/386/9pxeload
authdom=ca.sandia.gov
sys=jerq ether=001b210eaab5 ip=192.168.18.93
dom=jerq.ca.sandia.gov
auth=plan9.ca.sandia.gov
#Note this is wrong but ron is too lazy to fix it just yet.
sys=blit ether=ff1b210f7faa
ip=192.168.18.92
ipgw=192.168.18.10
dom=gnot.ca.sandia.gov
bootf=/386/9pxeload
authdom=ca.sandia.gov
sys=ppc ether=0002b5019094
ip=192.168.18.91
dom=ppc.ca.sandia.gov
bootf=/power/9eval.elf
authdom=ca.sandia.gov
#
# because the public demands the name localsource
#
ip=127.0.0.1 sys=localhost dom=localhost
smtp=plan9
prev parent reply other threads:[~2008-01-16 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 20:05 john
2008-01-15 20:44 ` erik quanstrom
2008-01-15 20:59 ` john
2008-01-15 21:10 ` erik quanstrom
2008-01-15 21:28 ` john
2008-01-16 0:11 ` john [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=ab0fd3e2c33fbf86271123ba6cabeb74@csplan9.rit.edu \
--to=john@csplan9.rit.edu \
--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).