Date: Sat, 22 Oct 2016 22:06:12 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 213712] net/mosh: Can't connect since FreeBSD 11 Message-ID: <bug-213712-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213712 Bug ID: 213712 Summary: net/mosh: Can't connect since FreeBSD 11 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: zi@FreeBSD.org Reporter: listat2016@apz.fi Flags: maintainer-feedback?(zi@FreeBSD.org) Assignee: zi@FreeBSD.org Since upgrading to FreeBSD 11 from 10.3 mosh has trouble connecting to the server. Curiously it does work pretty reliably when the server has SMP, virtualized or not, but UP systems just give the error: /usr/bin/mosh: Did not find mosh server startup message. It seems I'm hitting a problem discussed here: https://lists.freebsd.org/pipermail/freebsd-current/2016-August/062987.html The thread has a mention of a patch for UP systems, but it's not clear if t= he patch has been added to ports. I've tried both; building the version from latest ports and the pre-compiled version available with pkgng. The FreeBSD version I'm using is: FreeBSD basestar4 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu S= ep 29 01:43:23 UTC 2016=20=20=20=20 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 and it's virtualized with KVM. Mosh server appears to start when run from s= hell over ssh, but it can't seem to handle starting it itself. --=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-213712-13>