"Roger A. Faulkner" wrote:
> > IIRC, then the pcfs timestamps have a 2 second timestamp granularity
> > for the mtime and a one day granularity for the atime.
> >
> > The latter cannot be represented in the pathconf() fcall.
> >
> > J?rg
>
> Yeah, well...
>
> I just made pathconf(_PC_TIMESTAMP_
"Roger A. Faulkner" wrote:
> In response to the e-mail discussion of this case,
> I am submitting this revised specification:
>
> futimens, utimensat
>
> 1. Introduction
>
> This case adds two new functions to the C library,
> futimens() and utimensat(), as follows:
>
>#include
On Thu, Aug 27, 2009 at 05:14:17PM -0700, Roger A. Faulkner wrote:
> > Actually, NFSv3 and NFSv4 already have this. I think our server just
> > sets this to a constant, and our client doesn't use it.
>
> I know that NFSv3 and NFSv4 send nanosecond-resolution
> timestamps over the wire. That's no
> Date: Thu, 27 Aug 2009 16:35:25 -0500
> From: Nicolas Williams
> Subject: Re: PSARC/2009/453 - futimens, utimensat
> To: "Garrett D'Amore"
> Cc: "Roger A. Faulkner" , psarc-ext at sun.com,
Pavel.Filipensky at sun.com, Bart.Smaalders at sun.com, Krist
On Thu, Aug 27, 2009 at 03:27:38PM -0500, Nicolas Williams wrote:
> On Thu, Aug 27, 2009 at 01:02:52PM -0700, Garrett D'Amore wrote:
> > +1 on the revised spec.
> >
> > It seems like (not this project) someone ought to pursue getting support
> > for high resolution timestamps into the next NFS sp
On Thu, Aug 27, 2009 at 01:02:52PM -0700, Garrett D'Amore wrote:
> +1 on the revised spec.
>
> It seems like (not this project) someone ought to pursue getting support
> for high resolution timestamps into the next NFS specification.
Conveniently, the IETF NFSv4 WG is looking for work items for
On Thu, 27 Aug 2009 22:25:19 +0200, Roger A. Faulkner wrote:
>> From: Joerg.Schilling at fokus.fraunhofer.de (Joerg Schilling)
>> "Roger A. Faulkner" wrote:
>>
... ... ...
>>> In addition, in order to query the timestamp resolution for
>>> a given file or directory, fpathconf() and pathc
> Date: Thu, 27 Aug 2009 22:25:19 +0200
> From: Joerg.Schilling at fokus.fraunhofer.de (Joerg Schilling)
> Subject: Re: PSARC/2009/453 - futimens, utimensat
> To: Roger.Faulkner at sun.com, psarc-ext at sun.com
> Cc: roland.mainz at nrubsig.org, Pavel.Filipensky at su
+1 on the revised spec.
It seems like (not this project) someone ought to pursue getting support
for high resolution timestamps into the next NFS specification.
- Garrett
Roger A. Faulkner wrote:
> In response to the e-mail discussion of this case,
> I am submitting this revised specificati
In response to the e-mail discussion of this case,
I am submitting this revised specification:
futimens, utimensat
1. Introduction
This case adds two new functions to the C library,
futimens() and utimensat(), as follows:
#include
int futimens(int fd, const struct times
"Roger A. Faulkner" wrote:
> I'm in agreement with the sentiment expressed here,
> and in fact I made the changes to support the pathconf()
> name _PC_TIMESTAMP_RESOLUTION in all the local file systems.
> ufs returns 1000 and zfs returns 1.
This seems to be correct.
> However, there is a proble
Hugh McIntyre wrote:
> Joerg Schilling wrote:
> >>>int futimens(int fd, const struct timespec times[2]);
> >>>
> >>>int utimensat(int fd, const char *path,
> >>> const struct timespec times[2], int flag);
> >
> > In order to allow programs like star to be able to work
On Fri, 21 Aug 2009 12:01:46 -0700, Roger A. Faulkner wrote:
>> Garrett D'Amore wrote:
>>> Don Cragun wrote:
On Fri, 21 Aug 2009 00:00:53 -0700, Hugh McIntyre wrote:
>> ... ... ...
I believe this project is incomplete without also adding support for
these to the fpathconf()
> Date: Fri, 21 Aug 2009 12:01:46 -0700
> From: Don Cragun
> Subject: Re: PSARC/2009/453 - futimens, utimensat
> To: "Garrett D'Amore"
> Cc: Roger.Faulkner at sun.com, lists at mcintyreweb.com, psarc-ext at
> sun.com,
Pavel.Filipensky at sun.com, Bart.Sm
Garrett D'Amore wrote:
> Don Cragun wrote:
> > On Fri, 21 Aug 2009 00:00:53 -0700, Hugh McIntyre wrote:
> >> Joerg Schilling wrote:
> int futimens(int fd, const struct timespec times[2]);
>
> int utimensat(int fd, const char *path,
> con
Don Cragun wrote:
> On Fri, 21 Aug 2009 00:00:53 -0700, Hugh McIntyre wrote:
> > Joerg Schilling wrote:
> > >>> >>>int futimens(int fd, const struct timespec times[2]);
> > >>> >>>
> > >>> >>>int utimensat(int fd, const char *path,
> > >>> >>> const struct timespec times
Garrett D'Amore wrote:
> Don Cragun wrote:
>> On Fri, 21 Aug 2009 00:00:53 -0700, Hugh McIntyre wrote:
>>
... ... ...
>>
>> I believe this project is incomplete without also adding support for
>> these to the fpathconf() and pathconf() functions and the getconf
>> utility.
>>
>
> Hm it
Don Cragun wrote:
> On Fri, 21 Aug 2009 00:00:53 -0700, Hugh McIntyre wrote:
>
>> Joerg Schilling wrote:
>>
int futimens(int fd, const struct timespec times[2]);
int utimensat(int fd, const char *path,
const struct timespec times
On Fri, 21 Aug 2009 00:00:53 -0700, Hugh McIntyre wrote:
> Joerg Schilling wrote:
> >>> >>>int futimens(int fd, const struct timespec times[2]);
> >>> >>>
> >>> >>>int utimensat(int fd, const char *path,
> >>> >>> const struct timespec times[2], int flag);
> > >
> > > In
To: gdamore at sun.com, Roger.Faulkner at sun.com
Cc: Bart.Smaalders at sun.com, Darrin.Johnson at sun.com,
Krister.Johansen at sun.com, Pavel.Filipensky at sun.com, psarc-ext at sun.com
Subject: Re: PSARC/2009/453 - futimens, utimensat
"Garrett D'Amore" wrote:
> An o
Joerg Schilling wrote:
>>>int futimens(int fd, const struct timespec times[2]);
>>>
>>>int utimensat(int fd, const char *path,
>>> const struct timespec times[2], int flag);
>
> In order to allow programs like star to be able to work correctly, we would
> also need to
An obvious +1. Thanks!
- Garrett
Roger A. Faulkner wrote:
> I am sponsoring this automatic case for myself.
>
> 1. Introduction
>
> This case adds two new functions to the C library,
> futimens() and utimensat(), as follows:
>
>#include
>
>int futimens(int fd, const
I am sponsoring this automatic case for myself.
1. Introduction
This case adds two new functions to the C library,
futimens() and utimensat(), as follows:
#include
int futimens(int fd, const struct timespec times[2]);
int utimensat(int fd, const char *path,
23 matches
Mail list logo
