9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] cpu from one CPU server to another CPU server
Date: Wed,  4 Nov 2015 18:47:34 -0800	[thread overview]
Message-ID: <f8af960acc7c3a365b2020a6166b63de@lilly.quanstro.net> (raw)
In-Reply-To: <4FD2ACD4F05.00000012burtons@inbox.com>

On Wed Nov  4 11:15:04 PST 2015, burtons@inbox.com wrote:
> Hi,
> 
> When I log into my first CPU server using drawterm, I try to cpu to my second CPU server and the first one in drawterm just hangs after entering the username/password.  After I run the cpu command, all subsequent windows in drawterm that I create with rio are blank like the whole system is hung.  I then have to kill my drawterm and reconnect after which everything is ok.
> 
> If I boot up a terminal with a local fossil I can successfully cpu into the other CPU server.
> 
> Any ideas on what is going on?

this is likely an authentication issue.  changing to the local fossil 
is likely skipping authentication.  you might try auth/debug to see what's going on.

also, i have this little wiggle in my lib/profile if the problem is not looking up
the auth server, but talking to factotum:

	if(! test -e /mnt/term/mnt/wsys){
		# cpu call from drawterm
		prompt=('; ' '')
		x=`{wc -l /mnt/term/mnt/factotum/ctl>[2=] || echo 0}
->		if(test $x(1) -gt 1 && ! ~ $sysname mikro µ)
->			bind /mnt/term/mnt/factotum /mnt/factotum
		if not
			auth/factotum
		termish terminal drawterm
	}


- erik



  reply	other threads:[~2015-11-05  2:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 17:49 Burton Samograd
2015-11-05  2:47 ` erik quanstrom [this message]
2015-11-06 16:24   ` Burton Samograd

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=f8af960acc7c3a365b2020a6166b63de@lilly.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).