/usr/bin/script eating 100% cpu with portupgrade and xargs
trociny at freebsd.org
Sat Oct 15 07:31:14 UTC 2011
On Fri, 14 Oct 2011 14:03:37 +0200 Jilles Tjoelker wrote:
JT> 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/
JT> The extra ^D\b\b are the EOF character being echoed. These EOF
JT> characters are being generated by the new script(1) to pass through the
JT> EOF condition on stdin.
JT> One fix would be to change the termios settings temporarily to disable
JT> the echoing but this may cause problems if the application is changing
JT> termios settings concurrently and generally feels bad.
JT> It may be best to remove writing EOF characters, perhaps adding an
JT> option to enable it again if there is a concrete use case for it.
Without passing EOF to the to the program being scripted the following command
will hang forever:
echo 1 |script /tmp/script.out cat
More information about the freebsd-stable