On Thursday, January 04, 2007 06:11:01 PM -0500 Jeffrey Altman
<[EMAIL PROTECTED]> wrote:
Marcus Watts wrote:
Secondly, I don't believe this *particular* structure is exported on
the wire. This could probably be made 64 bits and still work.
There are almost certainly going to be local 64-bit rounding
issues, especially wherever this thing gets used with openafs &
kerberos times (as Jeff points out these have to remain 32-bit for
now). Since this is a kerberos 4 specific structure and kerberos 4
itself is "going away" it's unlikely to have its 32-bit time issues
fixed - so there will probably never be anything that can make a
ktc_token that needs 64 bit timestamps.
ktc_token is communicated via pioctl. There is no requirement
that the pioctl client and the AFS cache manager be from the same
release or even the same distribution. This data structure really can't
be changed.
In fact, pioctl arguments _do_ appear on the wire, as part of the rmtsys
protocol. This is an ABI and must not change gratuitously.
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
