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 ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) -- 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
