Olivier Antoine([email protected]) on 2019.08.19 11:34:06 +0200: > Hi, > On i386: before patch: > $ dd if=/dev/urandom of=in bs=1M count=2k > $ openrsync --rsync-path=/usr/bin/openrsync -av in localhost:out > Transfer starting: 1 files > sender.c:551: error: in: mmap: Cannot allocate memory > client.c:85: error: rsync_sender > receiver.c:345: error: poll: hangup > server.c:145: error: rsync_receiver > > With your patch: > $ patch -p0 < /tmp/1 > Hmm... Looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |diff --git usr.bin/rsync/uploader.c usr.bin/rsync/uploader.c > |index fd07b22caeb..cce8b47a4c9 100644 > |--- usr.bin/rsync/uploader.c > |+++ usr.bin/rsync/uploader.c > -------------------------- > Patching file usr.bin/rsync/uploader.c using Plan A... > Hunk #1 succeeded at 158. > Hunk #2 succeeded at 741. > Hunk #3 succeeded at 910. > Hmm... Ignoring the trailing garbage. > done > > $ cd usr.bin/rsync/ && make -j3 && doas make install > ??? > > $ openrsync --rsync-path=/usr/bin/openrsync -av in localhost:out > Transfer starting: 1 files > sender.c:551: error: in: mmap: Cannot allocate memory > client.c:85: error: rsync_sender > receiver.c:345: error: poll: hangup > server.c:145: error: rsync_receiver > > From what I see, the mmap problem is on sender.c
Thanks, i'll work on that one too. /Benno
