Spent an hour trying to find the answer to this on the various SO, SF,
other usual suspects, but have failed.
I'm trying to improve a parallel rsync wrapper called parsyncfp (pfp) in
response to a user request. He wants rsync to emit data on multiple
interfaces (one interface per rsync
worked with at UCI a bit?
>
> Anyway, you might consider trying mrsync; it's intended to do rsync over
> multicast.
>
> HTH.
>
> On Fri, Mar 26, 2021 at 12:22 PM Harry Mangalam via rsync <
> rsync@lists.samba.org> wrote:
>
>> Spent an hour trying to find the answer
Thanks very much for the useful answers. Much obliged
Harry
On Mon, Mar 29, 2021 at 5:25 AM Paul Slootman via rsync <
rsync@lists.samba.org> wrote:
> On Fri 26 Mar 2021, Harry Mangalam via rsync wrote:
> >
> > I'm trying to improve a parallel rsync wrapper
Ok, thanks for that explanation.
H
On Sun, Nov 28, 2021, 1:59 PM Kevin Korb wrote:
> Rsync is designed to reduce the amount of data transmitted over the
> network. If rsync isn't networking it can't do that. However, it still
> uses the same code so it is still using a sender and a receiver
Can you elaborate on why this is?
I wrote a parallel rsync wrapper that works very well over networks but is
similarly very slow over local disks. I thought it was a bug in my code but
didn't get around to tracking it down since my use cases were all network/
parallel file systems.
Harry
On Sun,
I may be missing your intent, but why not set up different rsyncd modules
for the different paths?
Or are you saying that the paths change dynamically all the time? In which
case set a cron or triggered script to change the symlinks to the paths..?
H
On Sat, Mar 5, 2022 at 5:08 AM Glen Huang via
Obviously self-promotional, but Parsyncfp?
https://github.com/hjmangalam/parsyncfp
There are other like scripted parallel rsyncs, but I like this one. ;)
Hjm
On Mon, Apr 17, 2023, 3:42 AM just subscribed for rsync-qa from bugzilla
via rsync wrote:
>
