summaryrefslogtreecommitdiff
path: root/client
diff options
context:
space:
mode:
authorRuss Allbery <rra@stanford.edu>2010-02-09 23:58:36 -0800
committerRuss Allbery <rra@stanford.edu>2010-02-09 23:58:36 -0800
commit690493358caeba1c61e2a1edb4db9bd27faae0f6 (patch)
tree68f20d05aa3103c41ec0aaa3e4e17182dfb0ee2e /client
parent5d7f614e88bac459a693f1dcc91aad36ed3d00dd (diff)
Document that -u works if you don't have a ticket
The wallet client documentation said that you always needed an existing ticket. Mention that -u will work as well.
Diffstat (limited to 'client')
-rw-r--r--client/wallet.pod8
1 files changed, 4 insertions, 4 deletions
diff --git a/client/wallet.pod b/client/wallet.pod
index 09fb571..885b77e 100644
--- a/client/wallet.pod
+++ b/client/wallet.pod
@@ -51,10 +51,10 @@ data specific to the scheme that specifies which users are authorized.
For example, for the C<krb5> scheme, the identifier is a principal name
and only that principal is authorized by that ACL entry.
-To run the wallet command-line client, you must already have a Kerberos
-ticket. You can obtain a Kerberos ticket with B<kinit> and see your
-current Kerberos tickets with B<klist>. The wallet client uses the remctl
-protocol to talk to the wallet server.
+To run the wallet command-line client, you must either already have a
+Kerberos ticket or use the B<-u> option. You can obtain a Kerberos ticket
+with B<kinit> and see your current Kerberos tickets with B<klist>. The
+wallet client uses the remctl protocol to talk to the wallet server.
=head1 OPTIONS