From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 06:48:01 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59259106566B for ; Sun, 23 Oct 2011 06:48:01 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1B1A28FC0C for ; Sun, 23 Oct 2011 06:48:00 +0000 (UTC) Received: by iaky10 with SMTP id y10so8281433iak.13 for ; Sat, 22 Oct 2011 23:48:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=k72vsKsjeynyv+7AHI6Cycpk4UPJBABEJBDy2xaz0Vk=; b=HCmxrR0sOS2snD0Rt4zyHYmTOaW7SLQxEX5aqU/glHj07RDHDQPKsiqSLxbtpmKbHp hMI0bma93j4aeoWYcS92WuTWzH0nSuccWpUXftn4Ja/XObuWYINd4TSEoJst8KyLo2ej lzSE1z7sHvFBTgE9jTn6P9HfPQeZv0SVRrrCs= MIME-Version: 1.0 Received: by 10.231.49.147 with SMTP id v19mr7761449ibf.64.1319352480147; Sat, 22 Oct 2011 23:48:00 -0700 (PDT) Sender: utisoft@gmail.com Received: by 10.231.11.140 with HTTP; Sat, 22 Oct 2011 23:47:59 -0700 (PDT) Received: by 10.231.11.140 with HTTP; Sat, 22 Oct 2011 23:47:59 -0700 (PDT) In-Reply-To: <08C7028B-10E1-4855-B007-D2257216F077@lassitu.de> References: <20110918045413.GA63773@DataIX.net> <20110918053901.GA31617@icarus.home.lan> <86d3eydsmf.fsf@kopusha.home.net> <20111008002707.GA76128@swelter.hanley.stade.co.uk> <20111012222535.GB79291@swelter.hanley.stade.co.uk> <20111014120336.GB31718@stack.nl> <08C7028B-10E1-4855-B007-D2257216F077@lassitu.de> Date: Sun, 23 Oct 2011 07:47:59 +0100 X-Google-Sender-Auth: ewiX8YZG1ZxtY-pU1ZGvqN-k9hE Message-ID: From: Chris Rees To: Stefan Bethke Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-stable@freebsd.org" , Mikolaj Golub , Jilles Tjoelker Subject: Re: /usr/bin/script eating 100% cpu with portupgrade and xargs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 06:48:01 -0000 On 14 Oct 2011 21:50, "Stefan Bethke" wrote: > > > Am 14.10.2011 um 14:03 schrieb Jilles Tjoelker: > > > On Wed, Oct 12, 2011 at 11:25:35PM +0100, Adrian Wontroba wrote: > >> On Sat, Oct 08, 2011 at 01:27:07AM +0100, Adrian Wontroba wrote: > >>> I won't be in a position to create a simpler test case, raise a PR or > >>> try patches till Tuesday evening (UK) at the earliest. > > > >> So far I have been unable to reproduce the problem with portupgrade (and > >> will probably move to portmaster). > > > >> I have however found a different but possibly related problem with the > >> new version of script in RELENG_8, for which I have raised this PR: > > > >> misc/161526: script outputs corrupt if input is not from a terminal > > > >> Blast, should of course been bin/ > > > > The extra ^D\b\b are the EOF character being echoed. These EOF > > characters are being generated by the new script(1) to pass through the > > EOF condition on stdin. > > > > One fix would be to change the termios settings temporarily to disable > > the echoing but this may cause problems if the application is changing > > termios settings concurrently and generally feels bad. > > > > It may be best to remove writing EOF characters, perhaps adding an > > option to enable it again if there is a concrete use case for it. > > I finally figured out why my ports aren't updating anymore: when running portupgrade -a --batch from cron, stdin is /dev/null, and that produces the gobs of ^D in the output, as well as the script file that portupgrade creates. What's worse is that the upgrade never completes. > Worst of all, you're running portupgrade from cron without reading UPDATING, which is just asking for trouble. Chris