On Fri, 6 Mar 2009, Ken Raeburn wrote:
On Mar 6, 2009, at 13:43, pete...@bigfoot.com wrote:
Is there any way to determine the version of kinit or klist?
I'm afraid not, aside from the krb5-config option you noted.
It's still in our bug database, but hasn't gotten any attention yet. :-(
On Mar 7, 2009, at 21:49, Rainer Laatsch wrote:
The OpenAFS people force a string into their programs at compile
time, no extra flags. Doing e.g. 'strings /usr/vice/etc/afsd | grep
OpenAFS' shows the version. A similar setup for krb5 would suffice;
just propagate the
corresponding item
The OpenAFS people force a string into their programs at compile time, no
extra flags. Doing e.g. 'strings /usr/vice/etc/afsd | grep OpenAFS' shows
the version. A similar setup for krb5 would suffice; just propagate the
corresponding item of krb5-config into kinit/klist/kdestroy.
In an AFS
Is there any way to determine the version of kinit or klist?
For whatever reason, none of the kerberos commands support a --version
option other than the krb5-config command. Unfortunately, krb5-config
isn't always available. At least on Redhat systems it's part of the
development package
On Mar 6, 2009, at 13:43, pete...@bigfoot.com wrote:
Is there any way to determine the version of kinit or klist?
I'm afraid not, aside from the krb5-config option you noted.
It's still in our bug database, but hasn't gotten any attention yet. :-(
(I knew it had been reported, but took me a
Ken Raeburn raeb...@mit.edu wrote:
On Mar 6, 2009, at 13:43, pete...@bigfoot.com wrote:
Is there any way to determine the version of kinit or klist?
I'm afraid not, aside from the krb5-config option you noted.
It's still in our bug database, but hasn't gotten any attention yet.
:-( (I
On Mar 6, 2009, at 18:55, Christopher D. Clausen wrote:
Can the usage message display the current version?
That'd be an idea too... actually, standardizing *all* the usage
messages to do this would be smart.
I just checked in (a little while ago) a patch to add klist -V to
print the version
