| commit | fedf1a052e3e59197c7e18ae0094b5920c6bfc9c | |
| author | Björn Jacke <bj@sernet.de> | |
| Wed, 4 Nov 2009 10:15:31 +0000 (4 11:15 +0100) | ||
| committer | Björn Jacke <bj@sernet.de> | |
| Wed, 4 Nov 2009 14:56:41 +0000 (4 15:56 +0100) | ||
| tree | 4c0bea728ec928c0fb0d07e63b347538e4740d92 | treesnapshot (tar.gz zip) |
| parent | ba15be46cabaf0875e265dd8c445aac57c3715a2 | commitdiff |
s3: add support for full windows timestamps resolution on files
setting nanosecond timestamps using utimensat() was first supported by Linux
kernel 2.6.22 and glibc 2.6. It's specified in POSIX.1-2008.
This effectively makes us use Windows' full 100ns timestamp resolution -
actually just an improvement from 10^-6 to 10^-7.
For now Linux CIFS vfs will also just be able to make use of 100ns resolution,
not 1ns.
setting nanosecond timestamps using utimensat() was first supported by Linux
kernel 2.6.22 and glibc 2.6. It's specified in POSIX.1-2008.
This effectively makes us use Windows' full 100ns timestamp resolution -
actually just an improvement from 10^-6 to 10^-7.
For now Linux CIFS vfs will also just be able to make use of 100ns resolution,
not 1ns.
| source3/configure.in | diffblobblamehistory | |
| source3/modules/vfs_default.c | diffblobblamehistory |