Some file systems support 64-bit time stamps and have the utimes system call. This includes at least FreeBSD 4.6 and above and Linux. However, Samba does not pass the actual Windows timestamp values down to the VFS layer. I imagine that we will need configure tests to detect if 64-bit timestamps are supported on the platform that Samba is being built for, as well as changes to pass 64-bit time stamps all the way down. In addition, it might be useful to pass all four time stamps that Windows gives us down to the VFS layer on the grounds that some implementations might be able to store all four timestamps, or will choose to store some in extended attributes.
OpenVMS uses 64 bit timestamps, but on VAX would prefer them to be passed by pointer, not by value, as VAX does not support any 64 bit integer types. It would be better on OpenVMS if there were a set of macros that could be overridden by CONFIG.H that would allow the conversion from the SAMBA host times directly to the Microsoft Windows times, as there would be no loss in precision from the conversion. For the VFS layer, OpenVMS can store/report several of the timestamps with the same precision as Microsoft Windows. Otherwise for OpenVMS, the conversion to a what the OpenVMS C support library stores as a UNIX timestamp involves a loss of precision the last time I checked the options available.
anyone going to work on this ?
this is done