On Fri, Jul 03, 2009 at 03:32:29PM -0300, Carlos Carvalho wrote:
Both processes were killed with the same command, kill pid1 pid2.
A SIGTERM (the default kill signal) should be caught by rsync, allowing
it to cleanup before it exits.
However I've found that a file was left after interruption,
On Fri, Jul 03, 2009 at 05:25:18PM -0300, Carlos Carvalho wrote:
What happens if [some of] these files no longer exist in the source
when the next run happens? Are they, and .~tmp~, removed or kept?
The file is only removed if a matching filename is transfered in the
parent directory. This is
On Fri, Jul 03, 2009 at 10:46:13PM +0200, Axel Essbaum wrote:
In the second case the backup_dir report in the output is apparently
not on STDOUT.
In all versions of rsync prior to 3.1.0 (which is not yet released), the
backup_dir is ... message is output very early in the transfer, so a
remote
Leen Besselink (l...@consolejunky.net) wrote on 30 June 2009 09:05:
Mike Connell wrote:
Hi,
Hi Mike,
I've got identical servers. One is primary the other is backup
receiving rsyncs from the primary. I'm backing up a file system to
disk and the files are small and there are lots
Hello Samba Team,
We are using rysnc utility for transferring ~90GB data across the machines.
We noticed that for small folders, rsync is working fine but the moment we
switch to 90GB folder, it gets stuck at building file list. We even left
it running overnight e.g. 16 hours but it never came
Wayne Davison (way...@samba.org) wrote on 4 July 2009 08:53:
On Fri, Jul 03, 2009 at 03:32:29PM -0300, Carlos Carvalho wrote:
Both processes were killed with the same command, kill pid1 pid2.
A SIGTERM (the default kill signal) should be caught by rsync, allowing
it to cleanup before it
Water Kingdom (waterking...@gmail.com) wrote on 3 July 2009 15:49:
We are using rysnc utility for transferring ~90GB data across the machines.
We noticed that for small folders, rsync is working fine but the moment we
switch to 90GB folder, it gets stuck at building file list. We even left
it
Hi, I am trying to transfer a file that has spaces in its name. The rsync
gives me below error. Am I doing anything wrong?
#ls -l /tmp/test\ file
-rw-rw-r-- 1 xxx xxx0 Jul 5 02:23 /tmp//test file
# /usr/local/bin/rsync --archive /u/masanip/ACH/test\\\ file /tmp/mydir/
rsync:
Please note that double quates is working but I want to make it work with
\\\.
For example, == /usr/local/bin/rsync --archive /u/masanip/ACH/test file
/tmp/mydir/ == is working but == /usr/local/bin/rsync --archive
/u/masanip/ACH/test\\\ file /tmp/mydir/ == not.
Thanks.
On Sun, Jul 5, 2009 at
On 05.07.2009 02:29, paresh masani wrote:
Hi, I am trying to transfer a file that has spaces in its name. The rsync
gives me below error. Am I doing anything wrong?
What you are looking for is -s a.k.a. --protect-args'
- man rsync -
-s, --protect-args no space-splitting;
Got it work with single slash. :-)
# /usr/local/bin/rsync --archive /u/masanip/ACH/test\ file /tmp/mydir/
On Sun, Jul 5, 2009 at 2:34 AM, paresh masani masanipar...@gmail.comwrote:
Please note that double quates is working but I want to make it work with
\\\.
For example, ==
Hi,
On Sun, 5 Jul 2009, paresh masani wrote:
Hi, I am trying to transfer a file that has spaces in its name. The rsync
gives me below error. Am I doing anything wrong?
#ls -l /tmp/test\ file
-rw-rw-r-- 1 xxx xxx0 Jul 5 02:23 /tmp//test file
# /usr/local/bin/rsync --archive
12 matches
Mail list logo
