similar to: Possible memory leak?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm (very slowly) working on a kioslave for rsync. At this stage I'm just exec()ing the rsync binary. If you want to know how far I have to go, see: http://www.cuneata.net/rsync-kio.html for the bad news. One question that I'm still grappling with is how to handle motd. I have a very rough heurestic for finding it (everything up to the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have it very roughly working, in that I can browse some directories and download at least some files to view in konqueror. Obligatory screen shot at http://www.cuneata.net/rsync-kio.html It is a basic wrapper around the rsync binary. So I'm not yet getting any real benefit from rsync - I'm effectively always in --whole-file mode. This

Kevin Korb via rsync <rsync at lists.samba.org> (So 30 Dez 2018 23:56:44 CET): > I think --partial might be a red herring here. It only applies to what > happens when rsync is aborted in the middle of a file. What happens > without -P? Same happens w/o --partial. I append 2 logs: - a from localhost to remote server, exposing the missing "rename" - b from localhost to

Wayne, Please consider the attached patch. This applies to the current CVS, and is independant of patches/local-batch.diff. As a matter of fact, I'm sure it would conflict heavily with local-batch.diff. This version of batch mode has a couple distinguishing features: Write-batch records (almost) the entire sender side of the conversation into one file. ("Almost" because it has

https://bugzilla.samba.org/show_bug.cgi?id=8475 Summary: memory leak around free_xattr() and rsync_xal_free(), with -aX, 200 bytes per file and per directory Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core

> myotis at cix.compulink.co.uk (Graham Smith) writes: > >> I apologise for this question, as I'm sure the answer has got to be >> obvious, but I am trying to follow the John Maindonald tutorial and have >> stumbled at the first page. > >Link? (I suppose that I could find it, but it is you problem...) http://wwwmaths.anu.edu.au/~johnm/r/dsets/ >> I have

Hey guys, I've been working with rsync for the last couple weeks and I really need some help here. Linux to Linux transfers are working beautifully, but for the life of me I can't get transfers from win2k to work. I have the exact problem that was reported by Mark de Jong on Tue, 16 Jul 2002. I'm using the lastest version of cygwin, with rsync 2.5.5 and ssh 3.5p1 for my tests. The

rsync 2.5.0 still has a bug where it hangs under some circumstances. The hang is beyond my abilities to track down. I'll keep trying, though, but here are details in case they're of use to anyone else: - Code configured & built on Solaris 2.5.1. - Same binary run on Solaris 2.5.1 (client) and 2.8 (server). - Using rsh transport, but also fails with ssh - Does not fail with

Hi All I run rsync in an automated environment and it sometime will crash and leave a core dump file. from core dump, gdb shows that gdb) bt #0 add_dirs_to_tree (parent_ndx=-1, from_flist=0x56c590, dir_cnt=1) at flist.c:1422 #1 0x0000000000409eab in send_file_list (f=16, argc=-1, argv=0x56c238) at flist.c:2068 #2 0x0000000000419052 in client_run (f_in=16, f_out=16, pid=-1, argc=1,

I tried rsync 2.6.1cvs on my FreeBSD 4.X boxes. It dumps core when preserve_hard_links and backup. And SUPPORT_HARD_LINKS is true. rsync -avH --delete --backup --backup-dir=/some/backup/dir \ srchost::dir/ dir/ The core says... ------------------------------------------------------------------------ Program terminated with signal 11, Segmentation fault. #0 0x80536c0 in keep_backup

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 G'day The attached patch adds "first draft" support for service location protocol, using OpenSLP (http://www.openslp.org). This allows you to automagically discover all the rsync servers on your network (which is defined in terms of your SLP configuration - typically equal to multicast scope, but you can change it around with

Hi there, I tried to connect OS2 Warp 4 to Samba server. The network used to be NT 4.0 Domain, then migrated to Samba to become Domain Controller. I've followed below instruction, and still can't login to the domain. I can get an IP address and ping the Samba server, but can't login to domain and map any network share.

Hello, I wrote this patch that allows you to run rsync over an existing I/O connection, instead of creating a new rsh or socket connection. For example, I have a client and server that talk over ssh via a simple custom protocol. I want to use the existing ssh connection to transfer files, but I want the flexibility of rsync to do it. With this patch, I can do the following in my client

Hi All, I am trying to see the rsync source code. I could see that there are main three processes: I realize that Server or Client becomes Sender or Receiver based on arguments provided. 1. Daemon start_daemon : clientserver.c 2. Server if(sender) { call recv_filter_list : exclude.c call send_file_list : flist.c call send_files :

I'm using rsync to sync DB files from a FreeBSD box to a Windows XP box under interix. Until today everything was fine but now as soon as the windows box hits one file which is now greater than 2Gb it goes into an infinite loop in generator.c:sum_sizes_sqroot The code at fault seems to be: for (l = len; l >>= 1; b += 2) {} Here's the stack: #0 0x00402ae3 in sum_sizes_sqroot

https://bugzilla.samba.org/show_bug.cgi?id=4664 Summary: Infinite loop on files > 2Gb Product: rsync Version: 2.6.9 Platform: Other OS/Version: Windows XP Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: steven.hartland@multiplay.co.uk

I can't say I have any idea why rsync would just skip that step and I can't duplicate it myself. Your only recourse might be to use --inplace on that system. On 12/31/18 12:33 PM, Heiko Schlittermann via rsync wrote: > Kevin Korb via rsync <rsync at lists.samba.org> (So 30 Dez 2018 23:56:44 CET): >> I think --partial might be a red herring here. It only applies to what

Hi, I used --partial to transfer files from my local computer (rsync 3.1.2, Debian) to a remote computer (rsync 3.1.1 WD MyPassport Storage device) The files get transferred, but after successful transfer, the files are not renamed from .<tmpfile> to <file>. Where to go next? Here is the verbose output after transferring an empty file heiko at blade:~/Pictures$ rsync

--delete option is not working for me. The following is a minimal example. $ mkdir box1 box2 $ touch box1/letter box2/extra $ rsync -a -vv box1/ box2/ sending incremental file list delta-transmission disabled for local transfer or --whole-file letter total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 92 bytes received 34 bytes 252.00 bytes/sec total size is 0 speedup is 0.00 $ tree

I think --partial might be a red herring here. It only applies to what happens when rsync is aborted in the middle of a file. What happens without -P? Also, it is worth trying with --inplace. On 12/30/18 5:32 PM, Heiko Schlittermann via rsync wrote: > Hi, > > I used --partial to transfer files from my local computer (rsync 3.1.2, > Debian) to a remote computer (rsync 3.1.1 WD