similar to: fixing user, group, and mtime with rsync?

https://bugzilla.samba.org/show_bug.cgi?id=7618 Summary: symlinks and --link-dest Product: rsync Version: 3.0.7 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: the_majkl at seznam.cz QAContact:

Hello again, as stated earlier there is a problem with mtime setting on directories during healing in replication setup. Today I tested 2.0.5 and found out that the handling is more or less generally buggy for directory mtimes. Simply try this: untar some kernel archive on your local disk and look at the mtime of the created top directory. now untar the same archive on an exported gluster fs and

Hi rsync'ers. What can you recommend to create the initial backup of a partition before calling rsync (under Linux, 100 GB, 10M files, only normal files and some soft links)? (Using rsync takes too long for this initial copy.) Here are some candidates: 1. star -copy -no-fsync -p -xdot -C $1 . $2 2. tar -C $1 -cf - . | tar -C $2 -xf - 3. cp -a $1 $2 4. cpio ... ... Any experiences?

https://bugzilla.samba.org/show_bug.cgi?id=4977 Summary: rsync: failed to set times on Product: rsync Version: 2.6.9 Platform: x86 URL: http://www.mikerubel.org/computers/rsync_snapshots/ OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

Hello List, How would i rsync all files which are older than X-Days? I am missing some kind of -mtime option. Since this is quite common for backups i am wondering how you are doing this kind of stuff. Thanks, Mario

On the wiki: http://wiki.dovecot.org/Plugins/Zlib I think there should be a step 5.0. along the lines of "get and remember the original message file's mtime" And a step 5.4 like "Using the touch command or some other method, set the now compressed message's mtime back to the mtime of the original message file." To preserve the message's internal time in case

I have noticed an anomaly with symbolic links. umask 027 mkdir folder1 echo 'hello world' > folder1/file1 cd folder1 ln -s file1 softfile1 rsync -a ../folder1/ ../folder2/ ls -lF ../folder* ../folder1: total 16 -rw-r----- 1 alan alan 12 Apr 26 00:00 file1 lrwxr-x--- 1 alan alan 5 Apr 26 00:02 softfile1@ -> file1 ../folder2: total 16 -rw-r----- 1 alan alan 12 Apr 26

Hi all. I once tried to rsync around 100 GB (10 million files), but version 2.6.6 needed too much RAM and was too slow. Is one of the snapshots stable enough to try this again? Greetings Sven -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url :

I noticed that rsync is happy to hard-link a device node from a --link-dest dir even if its mtime differs from that of the source device node and --times is given. Is this behavior expected? It seems to break the rule that a difference in preserved attributes disqualifies a hard link. To see the behavior, run the following as root: mkdir src dest basis mknod src/null c 1 3 sleep 1 mknod

What is the maximum transfer rate allowed for rsync? I mean the limitations? I can't get more than 50Mbit speed in my gigabit lan, with rsync server or with ssh. ftp transfers reach >400Mbit , so it is not a lan or nic problem. Maybe it has something to do with my cpu limitations? or the limitations for rsync is the 50Mb/s? Here is my rsyncd.conf if it helps > # by gourgi > max

https://bugzilla.samba.org/show_bug.cgi?id=5867 Summary: rsync with ACLs resets mtime on targets Product: rsync Version: 3.0.4 Platform: x86 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: samba@byshenk.net

Hi, We use an rsync (rrsync, to be precise) based back-up solution. Every so often an iSCSI based file-system gets brought up and left connected for the night. After a mount event rsync will back that volume up, including server TB of data that haven't been modified, but the ctime is newer than the mtime. Is there a way to stop this behaviour? Cheers, Andrej

On 8 September 2015 at 13:57, Kevin Korb <kmk at sanitarium.net> wrote: Hi Kevin. > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > The ctime will always be newer or the same as the mtime. This is > because changing the mtime also changes the ctime as does other things > like changing the permissions. > > Rsync only pays attention to the mtime because rsync can

If Maildir storage is used, the mtime of a given Maildir file is set to the message's INTERNALDATE. Now, when a client APPENDs a message to an IMAP mailbox, the client may optionally specify the INTERNALDATE: | If a date-time is specified, the internal date SHOULD be set in the | resulting message; otherwise, the internal date of the resulting | message is set to the current date and time by

Hello, I'm using rsync as part of a centralised config management for several servers. I'm trying to monitor the mtime of a particular directory and confirm that the remote copies are approximately as new as the the local master. However, mtime on that directory is not being synced. Here's my rsync command: cd $confdir && rsync -avpzR --checksum -I -e "ssh"

If I run this: find /path/to/files/ -type f -mtime -2 -name *.xml.gz I get the expected results, files with modify time less than two days old. But, if I run it like this, with the print0 flag: find /path/to/files/ -print0 -type f -mtime -2 -name *.xml.gz I get older files included as well. Anyone know why?

Is there anyway I can get Dovecot to update mtime on dovecot.index everytime a user successfully checks there email? Or perhaps there is a better way to do what I want here. I am working on a script that I want to check when the last time a user checked there email account. If a user has not checked it in say 6 months I want to automatically suspend the account through the MTA. If they start

Hi, everyone! This is a follow-up to "Looks like a bug to me: Dovecot ignores Maildir/new timestamp" from Fredrik Roubert on 01.12.2015: https://www.dovecot.org/list/dovecot/2015-December/102585.html I've run into the same problem as Fredrik: When manipulating my Maildir locally with mutt, deleting a message from new/ doesn't cause a full update of the index. Therefore, IMAP

Matt McCutchen wrote: > On 8/4/07, Rekrutacja <rekrutacja119@gmail.com> wrote: >> i'm trying to use latest CVS rsync, but i'm getting these errors: >> >> *** glibc detected *** rsync: munmap_chunk(): invalid pointer: >> 0x0d757d58 *** > > This looks like the same problem Sven Hartrumpf recently encountered > and described in this thread: >

Hi, I''m writing my requirements in rspec, however, I can not figure out a way to execute all specs according to alphabetical order, not by last modified time. According to the documentation, it seems like the default is by alphabetical order, I just can not get that to work. In the unit tests with the rspec package, seems like only mtime was tested. Can anyone tell me how to run specs