Displaying 3 results from an estimated 3 matches for "find'ed".
Did you mean:
binded
2005 Aug 12
4
Remote archiving with tar over ssh
I am trying to create a one line command that will:
1. Find all files ending in .conf
2. tar these over ssh to a remote server.
I have reached this point in my trials.
a. I can find the files.
b. I can tar them locally.
c. I can get a simple fileset tar'ed to a remote server over ssh
using tar -zvcf - /some/fileset | ssh host.domain.tld "cat &...
2006 Aug 22
1
rsync performance
...ed: 123363867
sent 643209 bytes received 123363867 bytes 62963.73 bytes/sec
total size is 17103825898 speedup is 137.93
lion:/homes/atg/ ========= Tue Aug 22 12:47:48 CEST 2006 ==================
1232323 files / 1960 sec = 629 files/sec
In comparison, on the large filesystem, 'find'ing all files on the
source system and 'stat'ing them takes 1.75 minutes:
source# time find /homes -xdev -print0 | xargs -0 stat -c "%s %Y" | wc -l
1232287
real 1m41.987s
user 0m7.075s
sys 0m33.216s
On the destination 4 minutes:
dest# time find /backup...
2004 Aug 10
2
out of memory in receive_file_entry rsync-2.6.2
...a pull on a linux system fom the HP-UX system that actually
houses the data. Both using rsync-2.6.2. The one solution i've come up
with isn't pretty, but seems to work.
Basically, I wrote a shell function that runs an rsync process for each
subdirectory if necessary. I'm using "find | wc -l" to count the number
of files in the source path and then calling the function again for each
subdirectory if the number is more than 2mil. Perhaps recursion is a bad
idea? It's the only way I could think of to catch the case where all the
files exist in a single directory severa...