From: sl@9front.org
To: 9front@9front.org
Subject: Re: [9front] passwd(1): These commands may be run only on a terminal
Date: Sun, 3 May 2015 13:34:38 -0400 [thread overview]
Message-ID: <87cdb7845f05e7e0af6de7233c4db0e6@u2.inri> (raw)
> 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
next reply other threads:[~2015-05-03 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 17:34 sl [this message]
2015-05-03 19:00 ` cinap_lenrek
-- strict thread matches above, loose matches on Subject: below --
2015-05-03 4:23 sl
2015-05-03 16:31 ` [9front] " cinap_lenrek
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=87cdb7845f05e7e0af6de7233c4db0e6@u2.inri \
--to=sl@9front.org \
--cc=9front@9front.org \
/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).