From owner-freebsd-questions@freebsd.org Fri May 5 12:00:17 2017 Return-Path: Delivered-To: freebsd-questions@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 93A4CD5F171 for ; Fri, 5 May 2017 12:00:17 +0000 (UTC) (envelope-from secretaria.centrosalud@ampformosa.com.ar) Received: from ws122.host4g.com (ws122.host4g.com [190.210.9.102]) by mx1.freebsd.org (Postfix) with ESMTP id A9A4B2A6 for ; Fri, 5 May 2017 12:00:16 +0000 (UTC) (envelope-from secretaria.centrosalud@ampformosa.com.ar) Received: from ws65.host4g.com (ws65.host4g.com [190.210.9.40]) by ws122.host4g.com (Postfix) with ESMTP id 4EF199942B815 for ; Fri, 5 May 2017 08:59:58 -0300 (ART) Received: from [142.0.42.11] (unknown [142.0.42.11]) by ws65.host4g.com (Postfix) with ESMTPA id 642FE42A1795 for ; Fri, 5 May 2017 08:59:04 -0300 (ART) MIME-Version: 1.0 Subject: Google User To: freebsd-questions@freebsd.org From: "Google Inc" Date: Fri, 05 May 2017 04:59:36 -0700 Reply-To: admin@gpawardteam.com Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: Mail message body X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2017 12:00:18 -0000 Dear Google User, We congratulate you for being selected as one of our winner on the ongoing = award promotion. Find attached document with more information regarding you= r winning. Congratulation, Sundar Pichai, Chief Executive Officer, Google Inc. From owner-freebsd-questions@freebsd.org Fri May 5 13:59:07 2017 Return-Path: Delivered-To: freebsd-questions@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 A05DAD5E03C for ; Fri, 5 May 2017 13:59:07 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7690B1D90 for ; Fri, 5 May 2017 13:59:07 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id v45Dx5UX006661 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 5 May 2017 07:59:06 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id v45Dx5CI006658; Fri, 5 May 2017 07:59:05 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Fri, 5 May 2017 07:59:05 -0600 (MDT) From: Warren Block To: Paul Macdonald cc: freebsd-questions@freebsd.org Subject: Re: Sticky portmaster updates In-Reply-To: <19177a8f-c9cc-da30-2e1e-0f81f049bbc9@ifdnrg.com> Message-ID: References: <19177a8f-c9cc-da30-2e1e-0f81f049bbc9@ifdnrg.com> User-Agent: Alpine 2.21 (BSF 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (wonkity.com [127.0.0.1]); Fri, 05 May 2017 07:59:06 -0600 (MDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2017 13:59:07 -0000 On Thu, 4 May 2017, Paul Macdonald wrote: > > I've noticed recently that on updating ports the update will stick on shell > until return is hit a few times, at which point update continues > > this is a scripted update but essentially just portmaster -a > > ps auxd shows no processes under portmaster > > this is all on FBSD11, amd64 and i'm seeing on several boxes > > anyone else seeing this or have any suggestions? I have not seen this, but it sounds like something waiting for interactive input. That could be something due to the particular shell, terminal, or script.