-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/11/2012 02:08 PM, Kevin Korb wrote:
> "Skipping directory ." because you didn't tell it to run
> recursively. I was suggesting options to add to a normal rsync not
> the only options to use. You would still need either --recursive
> or --archiv
On 11.04.2012 11:14, James Moe wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
> I restored a filesystem by using rsync to copy directories and files
> from a backup volume to the newly recreated volume. All of the
> re-created files were given the current date and time rathe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
"Skipping directory ." because you didn't tell it to run recursively.
I was suggesting options to add to a normal rsync not the only options
to use. You would still need either --recursive or --archive if you
are trying to rsync a directory.
On 04/1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/11/2012 01:53 PM, Kevin Korb wrote:
> It shouldn't care which way the time stamps are off. --times
> (which is part of --archive) will tell rsync to correct the time
> stamps and --size-only tells rsync to assume that files of the same
> size ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --times --size-only --itemize-changes
check it out first with --dry-run
On 04/11/12 14:14, James Moe wrote:
> Hello, I restored a filesystem by using rsync to copy directories
> and files from a backup volume to the newly recreated volume. All
> of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I restored a filesystem by using rsync to copy directories and files
from a backup volume to the newly recreated volume. All of the
re-created files were given the current date and time rather than the
original file's timestamp. I am sure ther
