Jonathan Black wrote:
> Coping a file to a local filesystem using the -p option preserves the
> timestamp as expected, but doing the same to an nfs filesystem replaces
> it with the current time, as if -p had not been given:
Mostly likely this is a limitation of the NFS server. Most likely a
feature restriction.
> $ cp -p /etc/debian_version /tmp
> $ cp -p /etc/debian_version /net/beacon/tmp
> $ ls -l {/etc,/tmp,/net/beacon/tmp}/debian_version
> -rw-r--r-- 1 root root 17 2005-06-06 19:50 /etc/debian_version
> -rw-r--r-- 1 jonathan jonathan 17 2005-11-21 23:40
> /net/beacon/tmp/debian_version
> -rw-r--r-- 1 jonathan jonathan 17 2005-06-06 19:50 /tmp/debian_version
Thank you for the small test case. Would you please run the case
again using strace and send in the result?
strace -e file cp -p /etc/debian_version /tmp
strace -e file cp -p /etc/debian_version /net/beacon/tmp
On my system I see this:
utimes("/net/marbles/tmp/debian_version", {1132636652, 0}) = 0
My suspicion is that the NFS call is given but ignored by the NFS
server. Can you try a different NFS server?
Bob
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
