From owner-freebsd-bugs@FreeBSD.ORG Mon Mar 12 17:30:16 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26377106566B for ; Mon, 12 Mar 2012 17:30:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 14FAA8FC14 for ; Mon, 12 Mar 2012 17:30:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q2CHUFBO030532 for ; Mon, 12 Mar 2012 17:30:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2CHUFYH030529; Mon, 12 Mar 2012 17:30:15 GMT (envelope-from gnats) Date: Mon, 12 Mar 2012 17:30:15 GMT Message-Id: <201203121730.q2CHUFYH030529@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Fabian Keil Cc: Subject: Re: bin/162064: [patch] Loop in fetch(1) when sending SIGINFO after the server stopped sending data X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Fabian Keil List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 17:30:16 -0000 The following reply was made to PR bin/162064; it has been noted by GNATS. From: Fabian Keil To: Mark Johnston Cc: bug-followup@FreeBSD.org Subject: Re: bin/162064: [patch] Loop in fetch(1) when sending SIGINFO after the server stopped sending data Date: Mon, 12 Mar 2012 18:27:08 +0100 --Sig_/qh0FNp./aksmLrhtGYLnbKM Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Mark Johnston wrote: > This is very similar to/exactly the problem I fixed in libfetch a > little while ago. Indeed, I can't reproduce it on my laptop running > CURRENT. See r230307 and bin/153240. I noticed r230307 and while I assumed that it might fix it, I didn't get around to testing it yet. Thanks for the reminder (and the fix of course). I can confirm that the problem is no longer reproducible. As far a I'm concerned the PR can be closed. Fabian --Sig_/qh0FNp./aksmLrhtGYLnbKM Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk9eMfQACgkQSMVSH78upWMK8gCfcy13J9TjGVxdlFbvpl0qxoEs yMoAnRA7iYVPC8eSkHi6D9BRpz7jigog =U8tf -----END PGP SIGNATURE----- --Sig_/qh0FNp./aksmLrhtGYLnbKM--