Date: Mon, 18 Jan 2016 22:17:58 +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-30cc59KiqS@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 #16 from Chris Hutchinson <portmaster@bsdforge.com> --- (In reply to fjwcash from comment #15) > Taken from the bbcp website (when in doubt, google it out): >=20 > --ipv4 [who] | -4 [who] > uses the IPv4 TCP stack for command processing and source-target > connections. This option is incompatible with IPv6 addresses. The optional > who argument restricts IPv4 mode to the command if c is specified, the > source if s is specified or the target if t is specified. The default is = cst > (i.e. everywhere). If who is omitted and =E2=80=93-ipv4 is the last optio= n on the > command line it must be followed by the -- option (double dash).=20 >=20 > So, it looks like the "-h" output should be updated to use: >=20 > [-4 [cst]] >=20 > Or similar, with an explanation of what c, s, and t stand for? >=20 >=20 >=20 > On another note, "-4 s" and "-4 t" end with segmentation faults. The only > option that works is "-4 c". >=20 > If needed, I can post core dumps for those two segfaults. A *huge* thanks for all your testing, fjwcash@! I had hoped to do some myself today. But the updating of my dev box last night, went a stray. :-( I'll see if I can get some done tomorrow. But in any event, it looks like we've come a long way, baby! :-) Thanks again, fjwcash! --Chris --=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-30cc59KiqS>