"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
--
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin
js at cs.tu-berlin.de (uni)
joerg.schilling at fokus.fraunhofer.de (work) Blog:
http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
