search for: utimensat

...nisys MCP Mainframe mounted with mount.cifs from RHEL 6.1 (samba-common-3.5.6-86.el6.x86_64). when I try to touch a file, it creates the file, but reports an error - "setting times of `testfile.txt': Permission denied" strace on the touch command shows that it is erroring out on the utimensat() call utimensat(0, NULL, NULL, 0) = -1 EACCES (Permission denied) Documentation from the Unisys Mainframe can be found here.... http://public.support.unisys.com/aseries/docs/clearpath-mcp-12.0/pdf/70118328-103.pdf Pages: C-2 and C3 show what POSIX functions are/not supported utime() and utimens...

...dif #if defined _MSC_VER # if _MSC_VER >= 1800 @@ -160,11 +164,15 @@ #define flac_fopen fopen #define flac_chmod chmod -#define flac_utime utime #define flac_unlink unlink #define flac_rename rename #define flac_stat stat +#if _POSIX_C_SOURCE >= 200809L +#define flac_utime(a, b) utimensat (AT_FDCWD, a, *b, 0) +#else +#define flac_utime utime +#endif #endif #ifdef _WIN32 diff --git a/src/libFLAC/metadata_iterators.c b/src/libFLAC/metadata_iterators.c index 352a6c7a..d5255eb9 100644 --- a/src/libFLAC/metadata_iterators.c +++ b/src/libFLAC/metadata_iterators.c @@ -3422,13 +3422,18...

...#39;s mtime specially by itemizing "T" instead of raising exit code 23. However, since commit accc091fe9ebbb602bcf692c577486e62011d5c1, rsync will try lutimes on non-symlinks as well and raise exit code 23, which defeats the intent of tolerating older kernels. The same issue occurs with utimensat, support for which was added right after the aforementioned commit. To fix this, rsync should fall back to utimes at runtime when lutimes or utimensat fails on a non-symlink. Alternatively, the special handling of lutimes/utimensat ENOSYS failures could be removed: the need is probably less now t...

...-- a/usr/klibc/SYSCALLS.def +++ b/usr/klibc/SYSCALLS.def @@ -140,7 +140,8 @@ int fchown32,fchown::fchown(int, uid_t, gid_t); <?> int fchownat(int, const char *, uid_t, gid_t, int); <?> int lchown32,lchown::lchown(const char *, uid_t, gid_t); int getcwd::__getcwd(char *, size_t); -int utimensat(int, const char *, const struct timespec *, int); +<32> int utimensat_time64::utimensat(int, const char *, const struct timespec *, int); +<64> int utimensat(int, const char *, const struct timespec *, int); <?> int inotify_init(); <?> int inotify_add_watch(int, const char...

Not all the fields of struct stat are actually filled by us. This caused rubbish to appear in the microseconds fields, which were then used as base when changing atime/ctime (with e.g. touch), triggering EINVAL by futimens/utimensat when those rubbish values were out of the range allowed for microseconds. --- src/fuse.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/fuse.c b/src/fuse.c index 288c02a..dd4f139 100644 --- a/src/fuse.c +++ b/src/fuse.c @@ -175,6 +175,7 @@ mount_local_readdir (const char *path, void *bu...

...POSIX.1-2001 declares this function obsolete; use nanosleep(2) instead. POSIX.1-2008 removes the specification of usleep(). recent rsync 3.1.3 is still using usleep: # grep -r usleep * config.h.in:/* Define to 1 if you have the `usleep' function. */ configure.ac: initgroups utimensat posix_fallocate attropen setvbuf usleep) configure.sh: initgroups utimensat posix_fallocate attropen setvbuf usleep OLDNEWS: - Use usleep() for our msleep() function if it is available. util2.c: usleep(t*1000); for my curiosity, that went into rsync @2014, which is not too long ago: ht...

...at syscall declarations mknodat and mkdirat contain a spurious repeated parameter, linkat is missing the final int flags parameter, symlinkat has the first two parameters transposed, and fchmodat is missing the flags parameter and is declared in the wrong header. Also declarations are missing for utimensat and fchownat. This patch fixes up these syscall declarations. Originally-by: Neil Williams <codehelp at debian.org> Originally-by: Anil Singhar <anil.singhar at linaro.org> Signed-off-by: Steve Capper <steve.capper at linaro.org> Signed-off-by: H. Peter Anvin <hpa at zytor.co...

...failures using Xcode 9, but all those same tests pass when using Xcode 8.3.3. I'm attaching a log, but here's an example: created directory /Users/chdiza/.tmp/tmpdir/rsync-20170920-66113-1rmtqxr/rsync-3.1.2/testtmp/exclude/chk ./ .filt dyld: lazy symbol binding failed: Symbol not found: _utimensat Referenced from: /Users/chdiza/.tmp/tmpdir/rsync-20170920-66113-1rmtqxr/rsync-3.1.2/rsync Expected in: /usr/lib/libSystem.B.dylib dyld: Symbol not found: _utimensat Referenced from: /Users/chdiza/.tmp/tmpdir/rsync-20170920-66113-1rmtqxr/rsync-3.1.2/rsync Expected in: /usr/lib/libSystem.B.d...

...a at samba.org Created attachment 13152 --> https://bugzilla.samba.org/attachment.cgi?id=13152&action=edit a proposed patch to ignore bogus .st_mtim.tv_nsec values by resetting them to 0 This suggestion is actually in a grey area between a proposed enhancement and a minor fix. Basically utimensat() sometimes fails to transfer mtimes for some bogus mtime values, so then rsync tries to transfer the same files over and over again. However, a simple utime() call works just fine, what leads to the whole suggestion. I'm attaching a proposed patch for rsync 3.1.1, but I think v. 3.1.2 can be...

That's what i did. After updating the kernel the phenomen has gone. The utimensat function is quite new and needed for timestamps in nano seconds. ----------------------------------------------- Karsten Hoffmann Adventos GmbH Alstertor 18 20095 Hamburg Tel +49 40 2093106-0 Fax +49 40 2093106-66 Email Info at Adventos.de ------------------------------------------------ ----- R...

...rt_sigaction 0.02 0.001588 16 102 brk 0.02 0.001494 18 85 getdents 0.02 0.001441 5 265 181 flock 0.00 0.000362 11 33 getxattr 0.00 0.000279 25 11 utimensat 0.00 0.000212 9 23 chdir 0.00 0.000122 122 1 unlink 0.00 0.000110 14 8 connect 0.00 0.000095 16 6 setxattr 0.00 0.000074 9 8 socket 0.00...

I was struggling tracking down a strange behaviour and could reproduce it with the testsuite. After patching it with: --- a/testsuite/compare-dest.test 2007-09-03 22:43:58.000000000 +0200 +++ b/testsuite/compare-dest.test 2014-12-30 19:28:32.060267390 +0100 @@ -18,6 +18,7 @@ # Setup the alt and chk dirs $RSYNC -av --include=text --include='*/' --exclude='*'

...pread 0.01 0.008339 18 451 pwrite 0.01 0.007232 14 505 getdents 0.00 0.003154 18 178 brk 0.00 0.000389 97 4 fdatasync 0.00 0.000322 17 19 9 utimensat 0.00 0.000250 5 47 getpeername 0.00 0.000230 5 46 1 flock 0.00 0.000152 152 1 unlink 0.00 0.000130 14 9 connect 0.00 0.000122 31 4 msync 0.0...

...sendmsg 0.00 0.000270 14 20 socket 0.00 0.000270 11 24 getcwd 0.00 0.000246 12 20 10 connect 0.00 0.000149 14 11 flock 0.00 0.000142 24 6 utimensat 0.00 0.000137 11 12 pread64 0.00 0.000129 11 12 kill 0.00 0.000117 15 8 open 0.00 0.000019 19 1 brk ------ ----------- ----------- --------- --------- ---------------- 100.0...

https://bugzilla.samba.org/show_bug.cgi?id=6672 Summary: mtim.tv_nsec not used when reading time of a file Product: rsync Version: 3.0.6 Platform: Other OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: antonio at

On Thu, 2016-10-13 at 20:08 -0400, Kevin Korb wrote: > I don't remember whether or not you said you were running rsync over > ssh but if you are you can also debug the ssh layer.  You can even do > it at both ends.... > > On the server run a debugging sshd on an alternate port with: > /usr/sbin/sshd -dDp222 > (note that this will only accept 1 connection, debug to the

...nt lchown32,lchown::lchown(const char *, uid_t, gid_t); int getcwd::__getcwd(char *, size_t); <?> int utime(const char *, const struct utimbuf *); <?> int utimes(const char *, const struct timeval *); <?> int futimesat(int, const char *, const struct timeval *); +<?> int utimensat(int, const char *, const struct timespec *, int); <?> int inotify_init(); <?> int inotify_add_watch(int, const char *, __u32); <?> int inotify_rm_watch(int, __u32); @@ -158,7 +159,7 @@ int getcwd::__getcwd(char *, size_t); */ <!i386,m68k,64> int open::__open(const char...

Hi Jones, many thanks again four your help and your time. Thanks for the patch too - I'll check it up. On my Ubuntu, there is a Samba 4.1.6. I'll install the samba source package, and will try to apply the patch, then - I hope - the package will be compiled as well. I'll notify to you about the result. (First, I need to upgrade that server.) Thanks again, Ervin On Thu, Apr

...nt lchown32,lchown::lchown(const char *, uid_t, gid_t); int getcwd::__getcwd(char *, size_t); <?> int utime(const char *, const struct utimbuf *); <?> int utimes(const char *, const struct timeval *); <?> int futimesat(int, const char *, const struct timeval *); +<?> int utimensat(int, const char *, const struct timespec *, int); <?> int inotify_init(); <?> int inotify_add_watch(int, const char *, __u32); <?> int inotify_rm_watch(int, __u32); @@ -158,7 +159,7 @@ int getcwd::__getcwd(char *, size_t); */ <!i386,m68k,64> int open::__open(const char...

Hello, Here is V2 of the arm64 support for klibc patch set. Notable changes since the original series: * fp regs dropped from setjmp/longjmp * chmod, lstat and stat re-implemented with *at functions. * open64 merged into open. As with the original, this series is to be applied against the latest klibc, just after 25a66fa README.klibc: update build information V2 has been tested on x86_64