Writes "John W. Sopko Jr." <so...@cs.unc.edu>: > Does anyone have a clue why the "tokens" command sometimes shows the > (AFS ID xxxx) and sometimes it does not as shown below? The > problem is intermittent. ...
The tokens command outputs 'AFS ID' if the difference between the token EndTimestamp and BeginTimestamp is odd, 'Unix UID' if the difference is even. There's logic in openafs [in src/auth/ktc.c] that increments BeginTimestamp if the difference is even (or makes it odd if the client name doesn't start with "AFS ID "...) Evidently whatever mechanism you're using to acquire tokens in redhat doesn't adjust BeginTimestamp. Probably you get the "wrong" behavior 50% of the time. -Marcus Watts _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info