similar to: rsync: always modify atime of all destination files

In the past there have been discussions about adding a switch to rsync to preserve the atime on files being copied by rsync. I needed this function for a project I'm working on and decided to invent it. I've attached the diffs. Note that this has the limitations describe in previous emails, namely that preserving atime causes ctime to not be preserved. *** Patch follows *** ***

I posted a patch a few days ago that adds copying of atime. At that time, it was just enabled with -t/--times. After some time, we have figured out that that choice might not have been the best. Here's a new version of the patch (relative to CVS) that adds -A/--copy-atime instead. It also includes a test case. Any feedback on this patch and/or the previous one that I posted?

Hi. Here's a patch for copying the atimes of files when -t/--times is given. I bumped the protocol to 29 since it sends more data over the wire. It obviously does not send the atime if it's sending data to an older rsync version. It passes all the tests (including the added atime.test) for me on a: Linux Debian/3.0 gcc 2.95.4 (debian), glibc 2.2.5 system. Any questions/feedback? I

-------- --Multipart_Thu_Apr__8_13:33:51_1999-1 Content-Type: text/plain; charset=US-ASCII Hello guys, I always wondered why smbclient keeps timestamp in `put'ting a file but does not keep it in `get'ting a file. Alternative to keep the time stamp in `get'ting file is to use -Tc option or smbtar script, but they are a bit hairy for interactive use, and it can only dump files with an

Dear Martin Pool. We regularly use rsync for making backups of our file systems but we have noticed that the atimes are not transferred with the files and are also always updated on the sender's side. Therefore, we have created a modified version of rsync based on rsync-2.6.6 protocol version 29 which transfers the access times with the transferred files and also allows to preserve the access

On Wed, 11 Jan 2006, joe wrote: >> Environment: > RELENG_4 20051028 >> Description: > [cp fails to update atime] > > this occurs regardless of whether or not the user has > rwx permissions on the source file. does not apply of > course if the source filesystem is mounted read-only. > they are read-write here. > > since the source file is indeed being read,

Hi all, and particularly Andrew and Stephen, I recently "upgraded' one of my NFS fileservers from (patched)2.4.18 to 2.4.23-pre7 (in order to resolve a HIMEM related memory pressure problem). Unfortunately I have experienced what appears to be a deadlock. The one I will describe was experienced while running 2.4.23-pre7, though I had a very similar problem in 2.4.22 (but

Hello Gluster Community, I did some experiments with setting the atime in different scenarios. In scenario 2,3 and 4 I have a simple replica 2 volume with worm-file-level on 1. Setting atime on XFS: *[davids at gluster-test1 src]$ touch test[davids at gluster-test1 src]$ sudo touch -a -t 197001010001 test[davids at gluster-test1 src]$ stat test File: ?test? Size: 0

Often we need to preserve the information atime conveys, but I have found no way to get rsync to preserve this, nor any hint it is being worked on. It would be great if 'rsync -t' also set atime not just mtime -- or maybe a new option is desired for atime. I don't know if the -X mentioned in "NEWS file from CVS" covers this: > Added the --xattrs (-X) option to preserver

It looks like I need to elaborate further to get a feedback. I checked the rsync source code and it is using utime() to restore atime file attribute. It is fine to change ctime for that transferred file in this case. What we are having problem is that when rsync gets kicked off and transfers one file to the destination, this action changes ctime of "all" files in the same

I find rsync an excellent tool when I need to move multi-gigabyte filesystems, because I can do most of the copying during the week - then a quick cleanup sweep in our 4 hour outage window. I do need to somehow get the atime's to copy over, because as it stands now I loose the age information (which we will soon be using for auto-archiving) on things I copy with rsync. Would it be that hard

https://bugzilla.samba.org/show_bug.cgi?id=5506 Summary: support utime differences at runtime, not configure/build time Product: rsync Version: 3.0.3 Platform: All URL: http://thread.gmane.org/gmane.network.rsync.general/1794 8 OS/Version: Linux Status: NEW Severity:

Hi, I looked though documentation and also checked last 9 months of archives, but could not find the corresponding information. We are having an issue with incremental backup with arkeia. Arkeia checks if ctime/mtime of the file are changed, if so, it backs up. I realized that when I ran rsync from a cammnd line, it changed ctime, and preserved atime of the file in a destination as

Hi Folks, I am a newbie in Qos... I could not find references to my question, then I am asking. This is the network: 192.168.1.2 --+ 192.168.1.3 --+ Router 192.168.1.4 --+ Linux/2.4 192.168.1.5 --+---- eth0 eth1 ---- internetprovider1 200.x.x.2 ----+ 200.x.x.3 ----+ 200.x.x.4 ----+ Other network: internetprovider2 ----- 200.y.y.6 (static IP) The link to internetprovider1 is

Hello I am making backup of a Plesk Debian server to /backup using Rsync. My questioin is how can I preserve the ctime, mtime, and atime of original files? Thanks

The way gnutar "preserves" atime is by noting it before the read, and setting it back after the read, thus wiping out a legitimate setting of atime occuring during that interval. Yeah, the netapps mess with unix times. Did you notice that mtime and ctime always match? Now that I know you're on a netapp, though, your problems are solved. Snapshot and sync from the snapshot, then

We should call ocfs2_inode_lock_atime instead of ocfs2_inode_lock in ocfs2_file_splice_read like we do in ocfs2_file_aio_read so that we can update atime in splice read if necessary. Signed-off-by: Tao Ma <tao.ma at oracle.com> --- fs/ocfs2/file.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/fs/ocfs2/file.c b/fs/ocfs2/file.c index 775ac34..95cba48 100644

Synopsis: cp(1) does not update atime of the source file State-Changed-From-To: open->closed State-Changed-By: dds State-Changed-When: Fri Dec 14 08:33:46 UTC 2007 State-Changed-Why: This problem has been fixed in RELENG_6. Pending MFC is no longer pertinent. http://www.freebsd.org/cgi/query-pr.cgi?pr=91622

I'm using 3.0.24 with patches from http://us4.samba.org/samba/patches/. On my XP client the print services for Unix are installed, I shared the local printer named 'jet' on the XP client to all users and the connecting user is an existing user on linux (system and samba user) and XP. I cannot execute the dir command in smbclient for this printer: deveis # smbclient -Utb%password

Hi! I have a setup with several Linux machines running samba-3.0.22-10.1.17 (from SuSE 10 OSS), authenticating against an AD. Since one of the machines is exporting an NFS share mounted by the rest of the machines, I need SID <-> uid/gid mapping to be shared between all Linux machines, which led me into using an OpenLDAP server as idmap backend. My smb.conf is found at the end of this mail.