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:21:41 +0300 [thread overview]
Message-ID: <2700E2A4-BCFB-42F1-B6DF-C5D38B1A75AC@cs.ioc.ee> (raw)
In-Reply-To: <88B3A90A-889C-40F1-BA12-54EF472E555E@cs.ioc.ee>
P.S.
mv /rc/bin/service/tcp567 /rc/bin/service/!tcp567
This line didn't work when I was following the instructions on the wiki for configuring a standalone cpu server as the file tcp567 wasn't there.
James
On Jun 4, 2012, at 10:14 PM, James Chapman wrote:
> cpu%cat /cfg/$sysname/cpustart
> aux/listen -q -t /rc/bin/service.auth -d /rc/bin/service tcp
>
> cpu%ls /rc/bin/service.auth
> /rc/bin/service.auth/authsrv.il566
> /rc/bin/service.auth/tcp567
>
> I guess I am already flailing... and I can't run anything on the server's console until tomorrow.
>
> Thanks,
>
> James
>
> On Jun 4, 2012, at 10:01 PM, erik quanstrom wrote:
>
>> On Mon Jun 4 14:53:57 EDT 2012, james@cs.ioc.ee wrote:
>>> Hi,
>>>
>>> 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
>>
>> check to see that you have the proper entries in your /rc/bin/service.auth
>> (or whatever directory you're using) *and* that you are starting a listen
>> on this directory.
>>
>> also, it's worth running auth/debug on the auth server's console
>> before making too many changes. i've found that it's easy to flail
>> and make conuter-productive changes.
>>
>> - erik
>>
>
next prev parent reply other threads:[~2012-06-04 19:21 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 [this message]
2012-06-04 19:26 ` erik quanstrom
2012-06-04 19:34 ` David du Colombier
2012-06-04 19:59 ` James Chapman
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=2700E2A4-BCFB-42F1-B6DF-C5D38B1A75AC@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).