From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from u2.inri ([107.191.125.208]) by pp; Sun May  3 13:34:45 EDT 2015
Date: Sun, 3 May 2015 13:34:38 -0400
From: sl@9front.org
To: 9front@9front.org
Subject: Re: [9front] passwd(1): These commands may be run only on a terminal
Message-ID: <87cdb7845f05e7e0af6de7233c4db0e6@u2.inri>
List-ID: <9front.9front.org>
X-Glyph: ➈
X-Bullshit: abstract managed full-stack-based hosting CSS-aware component optimizer
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

> i only see auth/login to warn when run on a cpu and netkey to
> refuse to work on a cpu. which commands need to be changed?

Specifically, passwd.

I may be guilty of believing the man page and misunderstanding the
problem. Looking at passwd.c, I don't see any place where any such
check is occurring, either.

I verified that passwd works on my local cpu server, whose ipnet
entry in ndb contains a definition for an auth server.

On the remote cpu server where the problem was first noticed,
running passwd produces the following error:

	passwd: protocol botch: cs: can't translate address: dns: resource does not exist; negrcode

This machine has the auth server defined in its plan9.ini, but has no
auth server specifically identified in its ndb. When I explicitly specify
an auth server, passwd works.

Note: Both machines use the same auth server.

I never had any problem with the original configuration using any
other form of auth or cpu services that I've tried.

So:

It appears passwd was already updated at some time in the past to
remove the restriction that it only runs on terminals. Maybe just
the man page needs to be changed?

sl