> 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 sun.com, lists at > mcintyreweb.com, krister.johansen at sun.com, gdamore at sun.com, dcragun at sonic.net, darrin.johnson at sun.com, bart.smaalders at sun.com > > "Roger A. Faulkner" <Roger.Faulkner at sun.com> 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 <sys/stat.h> > > > > int futimens(int fd, const struct timespec times[2]); > > > > int utimensat(int fd, const char *path, > > const struct timespec times[2], int flag); > > > > In addition, in order to query the timestamp resolution for > > a given file or directory, fpathconf() and pathconf() will > > be extended to accept a new name, _PC_TIMESTAMP_RESOLUTION, > > defined in <unistd.h>. The return value of fpathconf() > > and pathconf() in this case will be a number in the range > > 1 to 1000 million, indicating the number of nanoseconds > > of the file's timestamp resolution. Each local file system > > will be made to understand this new VOP_PATHCONF operation > > and return the appropriate value. > > 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_RESOLUTION) return 1000 000 000 for pcfs. Is that good enough? Does anyone really care? Should I make it fail (-1 w/ EINVAL)? Roger
