Date: Fri, 14 Oct 2011 22:50:32 +0200 From: Stefan Bethke <stb@lassitu.de> To: Jilles Tjoelker <jilles@stack.nl> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>, Mikolaj Golub <to.my.trociny@gmail.com> Subject: Re: /usr/bin/script eating 100% cpu with portupgrade and xargs Message-ID: <08C7028B-10E1-4855-B007-D2257216F077@lassitu.de> In-Reply-To: <20111014120336.GB31718@stack.nl> References: <op.v1y8gdtf8527sy@pinky> <20110918045413.GA63773@DataIX.net> <20110918053901.GA31617@icarus.home.lan> <op.v1zrszht8527sy@pinky> <86d3eydsmf.fsf@kopusha.home.net> <CAOnPXZ9z2MoZ7uxyUQzBx3Lz1mhY-2JKxO0mepzMp81J4WEVtw@mail.gmail.com> <20111008002707.GA76128@swelter.hanley.stade.co.uk> <20111012222535.GB79291@swelter.hanley.stade.co.uk> <20111014120336.GB31718@stack.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
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. >=20 >> So far I have been unable to reproduce the problem with portupgrade = (and >> will probably move to portmaster). >=20 >> 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: >=20 >> misc/161526: script outputs corrupt if input is not from a terminal >=20 >> Blast, should of course been bin/ >=20 > 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. >=20 > 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. >=20 > 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. You can easily see this for yourself: # portupgrade -a --batch </dev/null This is on 8-stable from October 5th. Stefan --=20 Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?08C7028B-10E1-4855-B007-D2257216F077>