(quoting reordered for my sanity's sake) Package: coreutils Version: 5.93-5 Followup-For: Bug #340236 I hit this problem as well today. Poking around with strace, I noticed several things: 1. cp exec
Thanks for the report. You might be right that the problem is due to the combination of using /proc/self/fd/N and NFS. I've Cc'd bug-coreutils, in case someone else has time to investigate this.
See <http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=755c1e20cd2ad56e5c567fa05769eb98a3eef72b>. Andreas. -- Andreas Schwab, SuSE Labs, address@hidden SuSE Linux Produc
nfs-utils is just the userspace part, which is only responsible for the setup of the NFS kernel daemon, and definitely does not touch futimes() in any way. It sounds like you'd rather want to reassig
The strace output does not refer to utimes by name. The relevant EPERM is returned by something referred to as SYS_271 - presumably the label simply means "strace could not identify the name of this
It looks like on x86 linux, 271 is in fact utimes(), according to <http://www.lxhp.in-berlin.de/lhpsysc0.html>. The fact that strace shows 5 arguments is probably because it cannot identify it (and t
The Wanderer <address@hidden> writes in <http://lists.gnu.org/archive/html/bug-coreutils/2005-12/msg00199.html>: I copied a directory hierarchy across a network to a shellfs mount, What's a shellfs
I don't observe the problem on my Debian host, when running coreutils 5.93 (which I compiled). This is with Linux kernel 2.4.18-686, libc 2.3.2, as an NFS client with a Solaris 8 NFS server. So possi
What's a shellfs mount? Sorry, I've never heard of shellfs. That sounds very much like an error in the shellfs implementation; it shouldn't matter at all whether the file names contain a single-quote
Thanks for the strace details. That confirms utimes is operating on /proc/fd/... and succeeding, yet not changing time stamps. You might want to try the latest snapshot, just in case it helps, but I
Additional info to my former mail: 1) My former mail contained a small inconsistency (after anonymizing the user name). The following messages show the problem in a consistent way (username, home-dir