From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Auth woes.
Date: Tue, 3 May 2005 14:00:41 -0400 [thread overview]
Message-ID: <ee9e417a05050311007a7101fd@mail.gmail.com> (raw)
In-Reply-To: <4277BB46.6020001@asgaard.homelinux.org>
pull a new factotum from sources.
i bet your problem goes away.
On 5/3/05, "Nils O. Selåsdal" <noselasd@asgaard.homelinux.org> wrote:
> Hi,
> I'm having some auth woes - on a cpu/file/auth server running pccpuf(minus some
> network and video drivers).
>
> These lines appear in my cpurc;
>
> auth/cron >>/sys/log/cron >[2=1] &
> auth/secstored -s tcp!192.168.1.100!5356
> auth/keyfs -wp -m /mnt/keys /adm/keys >/dev/null >[2=1]
>
> Now, the only crontab is /cron/upas/cron , after cron has run that once, I can
> no longer authenticate to the box.
> Drawterm says; drawterm: cannot authenticate with p9
> abort 11426
>
> And 'cpu -h localhost -u bootes' from an already logged in drawterm
> session says
> cpu% cpu -h localhost -u bootes
> cpu: can't authenticate: localhost: auth_proxy short read: cpu: srvauth:
> auth_proxy rpc: negotiation failed, no common protocols or keys
>
> Commenting out the line that starts cron in cpurc, auth never(so far)
> stops after a reboot...
> Any suggestions ?
>
> (btw. 2 other people have the same symptoms on their auth/cpu/file servers, I've
> not verified with them wether running cron or not affects anything.)
>
> --
> Nils O. Selåsdal
>
next prev parent reply other threads:[~2005-05-03 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 17:56 "Nils O. Selåsdal"
2005-05-03 18:00 ` Russ Cox [this message]
2005-05-03 18:41 ` "Nils O. Selåsdal"
[not found] ` <ee9e417a05050311465174d433@mail.gmail.com>
2005-05-03 20:19 ` "Nils O. Selåsdal"
2005-05-03 20:59 ` Russ Cox
[not found] ` <4277EEE4.5060504@asgaard.homelinux.org>
[not found] ` <ee9e417a05050314435cd0ebd9@mail.gmail.com>
2005-05-03 22:08 ` "Nils O. Selåsdal"
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=ee9e417a05050311007a7101fd@mail.gmail.com \
--to=russcox@gmail.com \
--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).