On Wed, 22 Jan 2025 at 00:38, Roland Mainz via Cygwin <cygwin@cygwin.com> wrote: > > Hi! > > ---- > > If a Windows filesystem does not support a type of timestamp it sets > the matching timestamp field in |FILE_BASIC_INFO| to |0LL| (e.g. see > Windows-driver-samples/filesys/cdfs/fileinfo.c: > |Buffer->LastAccessTime.QuadPart = 0| ; typically this can affect > |FILE_BASIC_INFO.CreationTime| and/or > |FILE_BASIC_INFO.LastAccessTime|, but formally any combination of > timestamp fields can be unsupported(==|0LL|)), and the Microsoft NFSv3 > driver sets the matching > |nfs_timestruc_t.tv_sec|+|nfs_timestruc_t.tv_nsec| to a negative value > (traditional UNIX uses -1, see > https://github.com/gagern/gnulib/blob/master/lib/stat-time.h#L173 - > and this value is then propagated via NFS), but I can't find a place > in Cygwin where this is explicitly handled - is this missing, or is > this code handling this somehow implicitly ? >
What should Cygwin stat() return if a timestamp field is not supported by the file system? Return tv_sec=-1? Ced -- Cedric Blancher <cedric.blanc...@gmail.com> [https://plus.google.com/u/0/+CedricBlancher/] Institute Pasteur -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
