From: James Chapman <james@cs.ioc.ee>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] drawterm to cpu/auth server with ordinary user
Date: Mon, 4 Jun 2012 22:59:33 +0300 [thread overview]
Message-ID: <ECDF9D78-2C01-4EE4-B3A2-2D8CFB311CEC@cs.ioc.ee> (raw)
In-Reply-To: <20120604213423.6003ee4f@gmail.com>
I just discovered that I can drawterm in from a machine on the same network with my user but it doesn't work from outside (over the internet).
I am using dhcp with just the following in /lib/ndb/local:
cpu% cat /lib/ndb/local
#
# 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
#
# because the public demands the name localsource
#
ip=127.0.0.1 sys=localhost dom=localhost
authdom=mydom.home auth=myserver
and
sysname=myserver
in plan9.ini
Do I need to put the authdom and auth somewhere else too?
James
On Jun 4, 2012, at 10:34 PM, David du Colombier wrote:
>> I'm trying to set up a combined cpu/auth server. I can drawterm into
>> it using bootes but if I try the other user then I created the
>> following happens after I type in my password:
>>
>> cpu: cannont get auth tickets in p9sk1: Connection refused
>>
>> goodbye
>
> When you are running plan9port factotum, this problem appears
> when you forgot to add auth= authdom= in $PLAN9/lib/ndb.
>
> --
> David du Colombier
>
next prev parent reply other threads:[~2012-06-04 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 18:52 James Chapman
2012-06-04 19:01 ` erik quanstrom
2012-06-04 19:14 ` James Chapman
2012-06-04 19:21 ` James Chapman
2012-06-04 19:26 ` erik quanstrom
2012-06-04 19:34 ` David du Colombier
2012-06-04 19:59 ` James Chapman [this message]
2012-06-04 20:32 ` James Chapman
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=ECDF9D78-2C01-4EE4-B3A2-2D8CFB311CEC@cs.ioc.ee \
--to=james@cs.ioc.ee \
--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).