From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Tue, 3 May 2005 14:00:41 -0400 From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] Auth woes. In-Reply-To: <4277BB46.6020001@asgaard.homelinux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4277BB46.6020001@asgaard.homelinux.org> Topicbox-Message-UUID: 44b3212c-ead0-11e9-9d60-3106f5b1d025 pull a new factotum from sources. i bet your problem goes away. On 5/3/05, "Nils O. Sel=E5sdal" wrote: > Hi, > I'm having some auth woes - on a cpu/file/auth server running pccpuf(minu= s some > network and video drivers). >=20 > These lines appear in my cpurc; >=20 > auth/cron >>/sys/log/cron >[2=3D1] & > auth/secstored -s tcp!192.168.1.100!5356 > auth/keyfs -wp -m /mnt/keys /adm/keys >/dev/null >[2=3D1] >=20 > 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 >=20 > 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 >=20 > Commenting out the line that starts cron in cpurc, auth never(so far) > stops after a reboot... > Any suggestions ? >=20 > (btw. 2 other people have the same symptoms on their auth/cpu/file server= s, I've > not verified with them wether running cron or not affects anything.) >=20 > -- > Nils O. Sel=E5sdal >