Re: rsync 3.0.9 segmentation fault

2015-04-07 Thread Paul Slootman
On Tue 07 Apr 2015, Aron Rotteveel wrote: Anyone have any other ideas I could try to debug this issue? :) You could try using the latest version of rsync? 3.1.1 was released some time ago. Paul -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or

Re: rsync 3.0.9 segmentation fault

2015-04-07 Thread Aron Rotteveel
*Betreff:* Re: rsync 3.0.9 segmentation fault In addition to my last message: * Client (sender) has 16GB's or RAM, of which only 6.5GB is used during peak. * I tried using --no-inc-recursive, but it does not solve the issue. What currrently is puzzling me is the question of why I am

Re: rsync 3.0.9 segmentation fault

2015-04-07 Thread Aron Rotteveel
Both server and client are running 3.1.1 now but the problem still persists. Op 7 apr. 2015 10:35 AM schreef Paul Slootman paul+rs...@wurtel.net: On Tue 07 Apr 2015, Aron Rotteveel wrote: Anyone have any other ideas I could try to debug this issue? :) You could try using the latest version

Re: Re: rsync 3.0.9 segmentation fault

2015-03-27 Thread Aron Rotteveel
! ) regards roland *Gesendet:* Donnerstag, 19. März 2015 um 12:24 Uhr *Von:* Aron Rotteveel rotteveel.a...@gmail.com *An:* devz...@web.de *Betreff:* Re: rsync 3.0.9 segmentation fault In addition to my last message: - Client (sender) has 16GB's or RAM, of which only 6.5GB is used during

Re: rsync 3.0.9 segmentation fault

2015-03-27 Thread Aron Rotteveel
*Betreff:* Re: rsync 3.0.9 segmentation fault In addition to my last message: * Client (sender) has 16GB's or RAM, of which only 6.5GB is used during peak. * I tried using --no-inc-recursive, but it does not solve the issue. What currrently is puzzling me is the question of why I am

Re: rsync 3.0.9 segmentation fault

2015-03-27 Thread Aron Rotteveel
...@web.de mailto:devz...@web.de *Betreff:* Re: rsync 3.0.9 segmentation fault In addition to my last message: * Client (sender) has 16GB's or RAM, of which only 6.5GB is used during peak. * I tried using --no-inc-recursive, but it does not solve the issue. What currrently

Aw: Re: Re: rsync 3.0.9 segmentation fault

2015-03-27 Thread devzero
roland Gesendet:Freitag, 27. Mrz 2015 um 12:19 Uhr Von:Aron Rotteveel rotteveel.a...@gmail.com An:devz...@web.de Cc:rsync@lists.samba.org Betreff:Re: Re: rsync 3.0.9 segmentation fault Hi Roland, Thanks for the reply. Memory usage on both machines seem fine. The server has 4GBs of RAM

Re: rsync 3.0.9 segmentation fault

2015-03-27 Thread Kevin Korb
...@web.de mailto:devz...@web.de mailto:devz...@web.de mailto:devz...@web.de *Betreff:* Re: rsync 3.0.9 segmentation fault In addition to my last message: * Client (sender) has 16GB's or RAM, of which only 6.5GB is used during peak. * I tried using --no-inc-recursive, but it does

Re: rsync 3.0.9 segmentation fault

2015-03-27 Thread Kevin Korb
...@gmail.com *An:* devz...@web.de mailto:devz...@web.de mailto:devz...@web.de mailto:devz...@web.de mailto:devz...@web.de mailto:devz...@web.de mailto:devz...@web.de mailto:devz...@web.de *Betreff:* Re: rsync 3.0.9 segmentation fault In addition to my last message: * Client (sender) has 16GB's

Re: rsync 3.0.9 segmentation fault

2015-03-27 Thread Aron Rotteveel
...@web.de mailto:devz...@web.de mailto:devz...@web.de mailto:devz...@web.de mailto:devz...@web.de *Betreff:* Re: rsync 3.0.9 segmentation fault In addition to my last message: * Client (sender) has 16GB's or RAM, of which only 6.5GB is used during peak. * I tried using --no-inc

Re: Aw: Re: rsync 3.0.9 segmentation fault

2015-03-19 Thread Kevin Korb
://rsync.samba.org/FAQ.html#5 ! ) regards roland *Gesendet:* Donnerstag, 19. März 2015 um 12:24 Uhr *Von:* Aron Rotteveel rotteveel.a...@gmail.com *An:* devz...@web.de *Betreff:* Re: rsync 3.0.9 segmentation fault In addition to my last message: * Client (sender) has 16GB's or RAM, of which only

Aw: Re: rsync 3.0.9 segmentation fault

2015-03-19 Thread devzero
Hi Aron, i hope its ok for you if i bring this back on-list. Your issue and the way or possible fix to resolve it may be interesting for others too (that may include future searches etc) so with 3.1.1 we are a step further i dont really have a clue whats happening here but my next