similar to: DO NOT REPLY [Bug 5867] New: rsync with ACLs resets mtime on targets

I have a problem with the latest Samba (3.0.25a) running under FreeBSD (recent STABLE: FreeBSD 6.2-STABLE #41: Mon Jun 11 19:24:30 CEST 2007). I run multiple Samba/FreeBSD file servers (in a Windows 2003 domain with Windows 2003 DCs), and everything worked quite nicely until this week. After an upgrade (both Samba and OS), I have a serious problem with access. I am using pam_winbind with

https://bugzilla.samba.org/show_bug.cgi?id=5455 Summary: destination files with resource forks now have current mtime Product: rsync Version: 3.0.2 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would need to see both your existing rsync command line and the output of --itemize-changes when such an occurrence happens before I can really understand what is happening. In the end, if you have any output at all the bare minimum should be - --itemize-changes. --verbose is utterly useless without it. On 09/07/2015 11:10 PM, Andrej wrote: >

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

-----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 set a specific mtime (--times) but setting a specific ctime is impossible as it would violate the basic *nix security model.

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"

Hi, this is a question regarding the behavior of the --update option for the recursive replication of directories. rsync 3.0.7-2 shows the following behavior on a Debian squeeze system (ext4): After running the following commands the adjusted ownership of the subdirectory /tmp/dst/sub below the target directory is overwritten and its newer modification time is reset to that of the older

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

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

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

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?

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

I'm really excited about the recent work on extended attributes. I've compiled 2.6.9 with xattr support, and run a few tests. It seems that if I have a file with an extended attribute ( a resource fork in this case), and I run rsync -aX , the mtime is not preserved. Example: stat xattrsrc/a 234881026 2894399 -rw------- 1 admin staff 0 1048576 "Nov 10 10:03:01 2006" "Nov

I'm trying to write a script that runs rsync to pull files and then detect which ones of them have changed. The problem is when I run rsync without the -t flag the mtime gets updated every run, not only when the file changes. It this a bug, by design, or un-avoidable? My plan was to use the -N bash file test operator to check to see if the file had been accessed since it have been

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

samba on Raspberry pi 4b - Linux 6.1.41-v8+ aarch64 GNU/Linux if I do a mtime on the file that gets shared I see this Modify: 2020-10-22 09:02:16.991364753 -0400 when I do a mtime on the same file on the client (Linux) I see this Modify: 2020-10-22 09:02:16.991364700 -0400 Is not a big deal it just caused some rsync confusion that was addressed by using --modify-window=1 Is this by design

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

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

I've added the options --min-age=SECONDS and --max-age=SECONDS to allow rsync to skip files based on how recently they were modified. Setting --min-age=30 (for example) would cause rsync to skip files that had been modified within the last 30 seconds. Setting --max-age=7776000 would cause rsync to skip files that had been modified more than 90 days ago (7776000 == 60*60*24*90). I realize

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