DO NOT REPLY [Bug 6965] Avoid code 23 when source file is concurrently truncated

2009-12-13 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=6965 m...@mattmccutchen.net changed: What|Removed |Added Summary|truncated files and exit|Avoid code 23 when source

Re: rsync speed on slow wireless links

2009-12-13 Thread Matt McCutchen
On Thu, 2009-12-10 at 13:08 +0700, Max Arnold wrote: > I've noticed that rsync performs significantly worse than wget on slow > congested wireless > links (GPRS in my case). I don't have large statistics, but in my tests > rsync often stalls > for 3-5 minutes, while wget stalls only for several

Re: retransfer fail of large files with inplace and broken pipe

2009-12-13 Thread Tom
Thx to all, it was the -u option which prevents rsync to resume the file. Tom "Tony Abernethy" schrieb im Newsbeitrag news:af5ef1769d564645a9acc947375f0d021567087...@winxbeus13.exchange.xchg... > Tom wrote: >> to make things more clear >> >> 1.) >> first transfer is done either a initial setup

Compression error (Re: rsync hangs during transfer)

2009-12-13 Thread Matt McCutchen
On Fri, 2009-12-11 at 08:58 +0100, Dimitar Dimitrov wrote: > I am running the following rsync command to synchronize directories > between two servers: > rsync -axvz --delete-after -e ssh /SRCDIR/ bla...@dest:/DESTDIR > > The transfer starts and after a short while it appears to hang after > some

Re: v3.0.4 and OSXS - Exit code: 1

2009-12-13 Thread henri
> When launchd executed this command, it did not work. The system.log file > reads "Exited with exit code: 1". > > Can you redirect the output to a file so it can tell you why it failed? e.g. > >file.out 2>&1 > > One common thing that prevents non-interactive sudo is this tty setting: > >

Re: v3.0.4 and OSXS - Exit code: 1

2009-12-13 Thread Jonathan S. Abrams
Wayne Davison wrote: On Sun, Dec 13, 2009 at 8:49 AM, Jonathan S. Abrams mailto:hoci...@comcast.net>> wrote: When launchd executed this command, it did not work. The system.log file reads "Exited with exit code: 1". Can you redirect the output to a file so it can tell you why it fai

Re: retransfer fail of large files with inplace and broken pipe

2009-12-13 Thread Wayne Davison
On Sat, Dec 12, 2009 at 11:21 PM, tom raschel wrote: > so i had a look at --inplace which I thougt could do the trick, but inplace > is updating the timestamp and if the script start a retransfer after a > broken pipe it fails because the --inplace file is newer than the original > file of the se

Re: v3.0.4 and OSXS - Exit code: 1

2009-12-13 Thread Wayne Davison
On Sun, Dec 13, 2009 at 8:49 AM, Jonathan S. Abrams wrote: > When launchd executed this command, it did not work. The system.log file > reads "Exited with exit code: 1". > Can you redirect the output to a file so it can tell you why it failed? e.g. >file.out 2>&1 One common thing that prevent

Re: v3.0.4 and OSXS - Exit code: 1

2009-12-13 Thread Stefan Nowak
My first guess -- superficial because I am in a hurry right now but nevertheless want to help a little -- is that it is a permission problem: Your command line starts with a "sudo", and I am not sure how "launchd" gets sudo permissions without user interaction. Regards, Stefan Nowak Am 1

v3.0.4 and OSXS - Exit code: 1

2009-12-13 Thread Jonathan S. Abrams
Hello, I used Lingon for Leopard Server to create a launchd job that would execute the following rsync (v3.0.4) command when logged in as admin at 12:01 AM each day. sudo rsync -aAHvWX /Volumes/File_Storage/docs/ /Volumes/File_Storage_Mirror/docs When launchd executed this command, it did

RE: retransfer fail of large files with inplace and broken pipe

2009-12-13 Thread Tony Abernethy
Tom wrote: > to make things more clear > > 1.) > first transfer is done either a initial setup or with a usb hdd to get > sender and receiver in sync. > > 2.) > transfer does not stop because rsync had a timeout, it stops because > the dsl > line is broken (which i could see at dyndns) > > 3) >