Re: Mac Backup App

2014-10-03 Thread Dmitry Yu Okunev
Hello.

On 10/03/2014 09:24 PM, Dave Gradwell wrote:
 Hello,
 
 I am writing a backup application for Apple Macs which uses rsync at its core
 and I'd greatly appreciate any testing/feedback.

And I developed a live sync utility based on rsync and inotify/kqueue.
But I think it's wrong to use this maillist to advertise my project. :)

I think you just should find maintainers for your package for every
important OS and write a good documentation with clear HOWTO-s. Also you
should report about the project on IT-related conferences. And this will
be the best publicity policy, IMHO. ;)

Best regards, Dmitry.



signature.asc
Description: OpenPGP digital signature
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: Rsync 3.1.0 failing [iobuf] on MacOSX 10.8.5 (was Re: Cannot build rsync 3.1.0 on MacOSX 10.8.5 with fileflags patch)

2013-10-12 Thread Dmitry Yu Okunev
Hello, people.

On 10/12/2013 02:56 PM, Robert DuToit wrote:
 
 On Oct 12, 2013, at 12:36 AM, Anthony Morton amor...@fastmail.fm wrote:
 
 I got 3.1 to build all right on OS X but it won't run without stalling and 
 lots of errors. Is it working for you or anyone else yet or have the 
 problems come to light?

 Yes, now I'm using it in anger I'm seeing several fatal errors like the 
 following (I'm syncing with a local mount point, no network access involved):

 need to write 129836 bytes, iobuf.out.buf is only 65532 bytes.
 rsync error: protocol incompatibility (code 2) at io.c(599) [sender=3.1.0]
 rsync: [sender] write error: Broken pipe (32)
 
 Yes this is the error. I assume it has to do with the changes to the output 
 buffer code in io.c
 
 3.0.9 works great so I'm staying there for now and thankful for it. Would be 
 nice if someone with a bit more rsync code experience could take a look too. 

Yeah, I've seen that IO_BUFFER_SIZE was increased from 4092 to
32*1024 in version 3.1.0. However it works well on my Linux
systems.. And I'm using it on my production servers already.

Just a hypothesis, can you show ulimit -a?

 Cheers,  Rob
 
 

 need to write 401925 bytes, iobuf.out.buf is only 65532 bytes.
 rsync error: protocol incompatibility (code 2) at io.c(599) [sender=3.1.0]
 rsync: [sender] write error: Broken pipe (32)

 I've rolled back to version 3.0.5 (the most recent I had installed 
 previously) and it seems to be doing the job.

 Tony M.

 

-- 
С уважением, Дмитрий,
начальник отдела UNIX-технологий,
тел. 8 (495) 788-56-99, доб. 8255



signature.asc
Description: OpenPGP digital signature
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Re: Rsync 3.1.0 failing [iobuf] on MacOSX 10.8.5 (was Re: Cannot build rsync 3.1.0 on MacOSX 10.8.5 with fileflags patch)

2013-10-12 Thread Dmitry Yu Okunev
On 10/12/2013 03:49 PM, Robert DuToit wrote:
 
 On Oct 12, 2013, at 7:11 AM, Dmitry Yu Okunev dyoku...@ut.mephi.ru wrote:
 
 Hello, people.

 On 10/12/2013 02:56 PM, Robert DuToit wrote:

 On Oct 12, 2013, at 12:36 AM, Anthony Morton amor...@fastmail.fm wrote:

 I got 3.1 to build all right on OS X but it won't run without stalling 
 and lots of errors. Is it working for you or anyone else yet or have the 
 problems come to light?

 Yes, now I'm using it in anger I'm seeing several fatal errors like the 
 following (I'm syncing with a local mount point, no network access 
 involved):

 need to write 129836 bytes, iobuf.out.buf is only 65532 bytes.
 rsync error: protocol incompatibility (code 2) at io.c(599) [sender=3.1.0]
 rsync: [sender] write error: Broken pipe (32)

 Yes this is the error. I assume it has to do with the changes to the output 
 buffer code in io.c

 3.0.9 works great so I'm staying there for now and thankful for it. Would 
 be nice if someone with a bit more rsync code experience could take a look 
 too. 

 Yeah, I've seen that IO_BUFFER_SIZE was increased from 4092 to
 32*1024 in version 3.1.0. However it works well on my Linux
 systems.. And I'm using it on my production servers already.

 Just a hypothesis, can you show ulimit -a?
 
 it shows:
 
 core file size  (blocks, -c) 0
 data seg size   (kbytes, -d) unlimited
 file size   (blocks, -f) unlimited
 max locked memory   (kbytes, -l) unlimited
 max memory size (kbytes, -m) unlimited
 open files  (-n) 256
 pipe size(512 bytes, -p) 1
 stack size  (kbytes, -s) 8192
 cpu time   (seconds, -t) unlimited
 max user processes  (-u) 709
 virtual memory  (kbytes, -v) unlimited

OK, the hypothesis was wrong. Sorry, :).

 
 Rob
 

 Cheers,  Rob



 need to write 401925 bytes, iobuf.out.buf is only 65532 bytes.
 rsync error: protocol incompatibility (code 2) at io.c(599) [sender=3.1.0]
 rsync: [sender] write error: Broken pipe (32)

 I've rolled back to version 3.0.5 (the most recent I had installed 
 previously) and it seems to be doing the job.

 Tony M.



 -- 
 С уважением, Дмитрий,
 начальник отдела UNIX-технологий,
 тел. 8 (495) 788-56-99, доб. 8255

 -- 
 Please use reply-all for most replies to avoid omitting the mailing list.
 To unsubscribe or change options: 
 https://lists.samba.org/mailman/listinfo/rsync
 Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
 

-- 
Best regards, Dmitry,



signature.asc
Description: OpenPGP digital signature
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html