Hi, Sorry to bring back an old message. I encoutered the same problem recently on OpenBSD 7.0-stable with openrsync while it was working fine a few days ago. I knew I must have broken something. Indeed I deleted rsync because I didn't use it anymore or so I thought. So I installed it back and the problem was solved. >From what I gathered openrsync is still a work in progress : "we are still working on it... so please wait" states the project website [1].
While running openrsync you can see calls to rsync with ps. Now that I have a better understanding of the problem, I see that the answer was right in your report as it states : openrsync: : exec[0] = rsync I hope it could help other people who might do the same mistake I did. Robin [1] https://www.openrsync.org/ 2 février 2021 17:16 "Scott Bennett" <sbennett1...@gmail.com> a écrit: >> Synopsis: openrsync(1) error: unexpected end of file >> Category: system >> Environment: > > System : OpenBSD 6.8-current && OpenBSD 6.8 > Details : OpenBSD 6.8-current (GENERIC.MP) #449: Fri Jan 22 20:48:33 MST 2021 > dera...@octeon.openbsd.org:/usr/src/sys/arch/octeon/compile/GENERIC.MP > > Architecture: OpenBSD.octeon OpenBSD.amd64 OpenBSD.i386 > Machine : octeon amd64 i386 >> Description: > > openrsync(1) errors when attempting to sync local files (error output > below). I've reproduced this on octeon 6.8-current, i386 6.8-current, > and amd64 6.8-release. amd64 6.7-stable does not produce this error and > achieves the desired result. > >> How-To-Repeat: > > $ mkdir ~/mydir > $ touch ~/mydir/a ~/mydir/b > $ openrsync -tvvv --del -r ~/mydir /tmp > openrsync: : exec[0] = rsync > openrsync: : exec[1] = --server > openrsync: : exec[2] = --delete > openrsync: : exec[3] = -r > openrsync: : exec[4] = -t > openrsync: : exec[5] = -v > openrsync: : exec[6] = -v > openrsync: : exec[7] = -v > openrsync: : exec[8] = . > openrsync: : exec[9] = /tmp > openrsync: error: unexpected end of file > openrsync: error: io_read_nonblocking > openrsync: error: io_read_buf > openrsync: error: io_read_int > >> Fix: > > unknown > > dmesg: [dmesg deleted]
