Date: Thu, 22 Feb 2018 16:42:59 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 197035] sysutils/bbcp: segmentation fault and core dump when running latest version (20150113) Message-ID: <bug-197035-13-vpiJiJlTg8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-197035-13@https.bugs.freebsd.org/bugzilla/> References: <bug-197035-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D197035 --- Comment #25 from fjwcash@gmail.com --- Sending server: # freebsd-version -ku 10.3-RELEASE-p20 10.3-RELEASE-p22 # pkg info -x bbcp bbcp-20150116 Command used: bbcp -4 c -N io "${zfs} send -I ${localpool}/${localfs}/${site}@${lastsnap} ${localpool}/${localfs}/${site}@${yesterday}" rsbackup@${remserver}:"${zfs} recv ${recvopts} ${rempool}" Receiving server: # freebsd-version -ku 10.3-RELEASE-p20 10.3-RELEASE-p22 # pkg info -x bbcp bbcp-20150116 Everything works beautifully. And, reading back through this bug report, Comment 14 shows things working. :) At least for IPv4 connections. I hav= e no IPv6 systems to test that side of things with. Reading through Comment 14, it was the "-4 c" that made things work without segmentation faults for us. As far as our setup goes, this bug has been worked around / mitigated / avo= ided (solved?) by the use of "-4 c". As far as I am concerned, this is no longe= r an issue. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-197035-13-vpiJiJlTg8>