From: Boris Z. (boris@conley.com)
Date: 07/28/98-10:57:03 AM Z
Message-ID: <01BDBA05.B0D34300.boris@conley.com>
From: "Boris Z." <boris@conley.com>
Subject: RE: nfstime4 data type
Date: Tue, 28 Jul 1998 08:57:03 -0700
Sorry, I did not follow closely the time discussion and may be I missed the answer for another
question.
nseconds is unsigned. If my seconds value is negative, do I have to add or subtract nseconds?
Even if missed this answer, we have to add it to the draft.
Boris.
On Monday, July 27, 1998 3:15 PM, spencer.shepler [SMTP:Spencer.Shepler@Eng.Sun.COM] wrote:
>
> The following is what I have placed in the draft.
>
>
> struct nfstime4 {
> int64_t seconds;
> uint32_t nseconds;
> }
>
> The nfstime4 structure gives the number of seconds and
> nanoseconds since midnight or 0 hour January 1, 1970 Coordinated
> Universal Time (UTC). Values greater than zero for the seconds
> field denote dates after the 0 hour January 1, 1970. Values
> less than zero for the seconds field denote dates before the 0
> hour January 1, 1970.
>
> This data type is used to pass time and date information. A
> server converts to and from local time when processing time
> values, preserving as much accuracy as possible. If the
> precision of timestamps stored for a file system object is less
> than defined, loss of precision can occur. An adjunct time
> maintenance protocol is recommended to reduce client and server
> time skew.
This archive was generated by hypermail 2.1.2 : 03/04/05-01:46:06 AM Z CST