From: ori@eigenstate.org
To: fde101@fjrhome.net, 9fans@9fans.net
Subject: Re: [9fans] pi cpu server
Date: Fri, 04 Sep 2020 20:38:39 -0700 [thread overview]
Message-ID: <A433B6B6794C7540E6DE1E1F622495F1@eigenstate.org> (raw)
In-Reply-To: <2cb9d239-0071-619a-a176-32267ec7e017@fjrhome.net>
> Thanks, that is what I was missing - I had them on separate lines.
>
> Now I need to puzzle through this "tlsclient: auth_proxy: auth_proxy rpc
> write: interrupted" error whenever I try to use rcpu to connect back to
> the server as a different user (from a drawterm connection). If I just
> "rcpu" by itself it works, but "rcpu -u glenda" for example gives me
> that error.
First, make sure that your auth server is actually set up and found
correctly -- auth/debug can help here. Note that you'll probably be
able to auth as hostowner even if your auth server is misconfigured.
next prev parent reply other threads:[~2020-09-05 3:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 21:53 Frank D. Engel, Jr.
2020-09-04 22:38 ` [9fans] " ori
2020-09-05 2:35 ` Frank D. Engel, Jr.
2020-09-05 3:38 ` ori [this message]
2020-09-05 11:45 ` Frank D. Engel, Jr.
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=A433B6B6794C7540E6DE1E1F622495F1@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9fans@9fans.net \
--cc=fde101@fjrhome.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).