From owner-freebsd-ports@freebsd.org Thu Aug 11 23:51:45 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E22CBBB51A3; Thu, 11 Aug 2016 23:51:45 +0000 (UTC) (envelope-from cgull@glup.org) Received: from glup.org (216-15-121-172.c3-0.smr-ubr2.sbo-smr.ma.static.cable.rcn.com [216.15.121.172]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A248D1619; Thu, 11 Aug 2016 23:51:45 +0000 (UTC) (envelope-from cgull@glup.org) Received: from lister.boston.niksun.com (unknown [4.16.10.2]) by glup.org (Postfix) with ESMTPSA id A4595854C4; Thu, 11 Aug 2016 19:51:38 -0400 (EDT) Authentication-Results: glup.org; dmarc=none header.from=glup.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=glup.org; s=201009; t=1470959498; bh=beyw0oerXH2M/hp8m7Jg2IbJjxy6Qn7HvWezE3UPoLs=; h=Subject:To:References:Cc:From:Message-ID:Date:MIME-Version: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=JDOXsvII2HEtipKwMDqk9Lq41PNv6627W0ODIuZ0c1u9nWKz5ehSO7LX/oIdlJ+QG flGh7IBGo/ngml7iFcAAKa9a0Ji6y7FmbmjxBMoNbpbKIyMOoByYUXebHiOr59A4Zr o1i9hiEl8q7tpHQ/jGJVEgvPmfvbvd/zMpH53oOMEFuVJEmJydNqQC/vvD8s98mq1e s/PR8DAo8YO4eNUy8JQAc9+jX7nySasokfO8ygoGcvCfLjuVhzAjcM2hhZSuA6XUGx HJryVY+JtEg8d2qxU4tQng0Sr4tn4Is7k6BDurEUk1FzwHW2QRzDS8aWHw6BfNAkv+ +CbM8c/LG+Kkw== Subject: Re: Mosh regression between 10.x and 11-stable To: Peter Jeremy References: <20160810081831.GA65184@server.rulingia.com> <20160811101928.GC65184@server.rulingia.com> <68d0a6d4-2078-000c-6e22-b0b8721dfd2b@glup.org> <20160811195348.GD65184@server.rulingia.com> Cc: mosh-devel@mit.edu, freebsd-current@freebsd.org, freebsd-ports@freebsd.org From: John Hood Message-ID: <971e1e82-1b95-d1e4-6053-a8548fc1d109@glup.org> Date: Thu, 11 Aug 2016 19:51:37 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160811195348.GD65184@server.rulingia.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2016 23:51:46 -0000 That's interesting (not in a good way). Next thing to try: mosh --server='/usr/local/bin/mosh-server 2>/dev/null' peter@VPS (with an unmodified mosh-server) Mosh prints the 'MOSH CONNECT ...' message on stdout, then forks. The parent exits immediately, and the child prints verbose and copyright info to stderr. I'm wondering if the race is that the parent and child writes appear mixed together, corrupting the expected message. You might try adding a 'print;' in the while loop that digests this input in the mosh script. That'll tell us whether the script is not getting 'MOSH CONNECT...' at all, or if it's corrupted. You'll have to run mosh inside /usr/bin/script to capture that. regards, --jh On 08/11/16 03:53 PM, Peter Jeremy wrote: > On 2016-Aug-11 12:30:23 -0400, John Hood wrote: >> I still can't reproduce this on 3 different 11.0-BETA4 servers and a >> variety of clients and networks. Can you try and identify a more >> portable repro or at least figure out why it fails on your system? >> >> Please try applying this patch, too. It's a shot in the dark, though. > That patch seems to fix the problem I'm seeing. Not waiting for output > to drain is consistent with the symptoms I'm seeing, though I have no > idea why only my Linux client is affected. >