Rodney uses a modified version of the integrated login which performs the kinit and aklogsteps in an external process instead of relying on the k4 support built into OpenAFS. More than likely he is bypassing the cause of the blue screen.
You are correct. We do use a minimally altered version of the AFS logon authenticator "afslogon.dll" that we compile ourselves. See...http://www.coe.uncc.edu/~rmdyer/afslogonshell.htm
The "altered" part is simply a single line of code addition for exec'ing a shell. But, we've only been using this method since we moved to OpenAFS...since of course, I didn't have the source for Transarc's version and other reasons.
But laughing, I would be surprised if anything I do "prevents" a blue screen for us! The normal "unmodified" AFS logon authenticator has never failed on me. I may be wrong, my memory is poor these days. The code in the OpenAFS authenticator DLL is pretty generic, I doubt there's anything there that would cause a blue screen as none of it runs in the kernel.
Rodney
_______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
