-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I agree completely about getting rsync onto the NFS server. Rsync
(especially over ssh) is far more secure than NFS. Even if the NFS
server is actually a NAS appliance many of them can do rsync as well.
On 01/13/2014 11:14 PM, Linda A. Walsh wrote:
Perry Smith wrote:
This is my first time to really use rsync. I did small tests to get the
arguments like I wanted and then kicked off the big rsync about 2 and a half
hours ago. So far, it has not copied over any files.
-
Is it really making progress? Or will it take this long to real
On 1/13/2014 6:19 PM, Perry Smith wrote:
Yea. Shouldn't be hard to split up. The hard part is some type
of dependable rotation.
You mention "pause"... I have to disconnect so I assume that would
"abort" the transfer. But that triggered another question: would
daemon mode help in this situatio
On 1/13/2014 5:34 PM, Perry Smith wrote:
Ok. I can get the Mac up to version 3 but I'm wondering if
I need to rethink my whole strategy. Since the source is on NFS,
doing a stat on all the files each run may cost me too much
time.
I might need to split it into smaller pieces and then rotate
th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
By pause I essentially meant ^Z. If you have to actually disconnect
then you wouldn't be able to simply resume.
The only way rsyncd would help here would be that you could define
your globs in the rsyncd.conf file instead of on the command line.
Unle
Yea. Shouldn't be hard to split up. The hard part is some type
of dependable rotation.
You mention "pause"... I have to disconnect so I assume that would
"abort" the transfer. But that triggered another question: would
daemon mode help in this situation? (I assume not. The daemon
probably fol
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you have to abort it then I suppose that makes sense. Otherwise
you could throttle or pause it.
If you do have to split it up then it shouldn't be difficult. Your
original command was specifying multiple sources using a glob of some
kind so you w
The NFS server is off somewhere else, locked down. secure, blah blah.
Doing it via a script that rotates is the same number of stat calls but it
would start at a different place each day.
If I start it day 1 and it gets 25% through the stat calls, on day 2, will rsync
start where it left off or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It is still the same number of stat calls. Doesn't really matter if
you split them up.
Can you rsync to the NFS server directly?
On 01/13/2014 05:34 PM, Perry Smith wrote:
> Ok. I can get the Mac up to version 3 but I'm wondering if I need
> to ret
Ok. I can get the Mac up to version 3 but I'm wondering if
I need to rethink my whole strategy. Since the source is on NFS,
doing a stat on all the files each run may cost me too much
time.
I might need to split it into smaller pieces and then rotate
through the pieces via a script. Do you have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/13/2014 05:05 PM, Perry Smith wrote:
> A friend and I noticed the --times or --archive flag. I have not
> stopped it yet but I'll add that flag (probably --times).
>
> This is the first time so it must be #2.
>
> The side issuing the command
A friend and I noticed the --times or --archive flag. I have not
stopped it yet but I'll add that flag (probably --times).
This is the first time so it must be #2.
The side issuing the command is a Mac using rsync version 2.6.9
protocol version 29. The other side is AIX using rsync version 3.1.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
First, don't run rsync without either --times or --archive. Without
that rsync won't copy timestamps and it won't be able to tell what is
changed when you run it again.
Second, if rsync isn't copying anything then there are 2 reasons...
1. You alread
This is my first time to really use rsync. I did small tests to get the
arguments like I wanted and then kicked off the big rsync about 2 and a half
hours ago. So far, it has not copied over any files.
The command I used is:
rsync \
--relative \
--recursive \
--copy-links \
host:/glob
14 matches
Mail list logo