[OpenAFS] Can't aklog with Windows v1.3.66

John Koyle jkoyle@rfpdepot.com
Thu, 29 Jul 2004 08:49:17 -0600

I was trying the version that came with KFW 2.6.3 and 2.6.4.  Trying 
1.3.66 also fails :(

Using aklog -d doesn't give any addition debugging information that I 
can tell, and nothing is logged to the \windows\temp\afs* files.  Do I 
need to install the debug version of the client to get more debugging 

Using Leash32 to get tickets/tokens works, but doesn't/can't use the 
keytab file.  In addition, I can't kinit/aklog from the command prompt.

The only previous client on the system was v1.3.65, and I 
un-install/rebooted before installing 1.3.66.


Jeffrey Altman wrote:

> Which aklog are you running?  There is an aklog shipped with OpenAFS 
> and one with KFW.
> You want to use the one from OpenAFS.
> As I maintain both packages you talk to me either way.
> At what point in the aklog does the crash occur?   "aklog -d"
> Jeffrey Altman
> John Koyle wrote:
>> I have a system that uses a script to obtain credentials via a keytab 
>> file and kinit/aklog.  However,
>> the latest release causes aklog to crash when it's run (previous 
>> 1.3.63 and 1.3.65 versions worked).
>> Presumeably this is a problem the MIT folks will need to tackle, or 
>> am I just missing something obvious?
>> Just wanted to give a heads up to anyone who may run into the same 
>> issue.
>> John
>> _______________________________________________
>> OpenAFS-info mailing list
>> OpenAFS-info@openafs.org
>> https://lists.openafs.org/mailman/listinfo/openafs-info