Re: mtime vs ctime

2015-09-07 Thread Andrej
On 8 September 2015 at 15:21, Kevin Korb wrote: > 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 shou

Re: mtime vs ctime

2015-09-07 Thread Kevin Korb
-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 - --it

Re: mtime vs ctime

2015-09-07 Thread Andrej
On 8 September 2015 at 13:57, Kevin Korb 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 on

Re: mtime vs ctime

2015-09-07 Thread Kevin Korb
-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 (--ti