Date: Tue, 8 Apr 2003 00:14:22 +1000 (EST) From: Tim Robbins <tim@robbins.dropbear.id.au> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/50679: vi invoked from chpass and vipw exits on ^C Message-ID: <20030407141422.3A994C90D@dilbert.robbins.dropbear.id.au> Resent-Message-ID: <200304071420.h37EKDRu061987@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 50679 >Category: bin >Synopsis: vi invoked from chpass and vipw exits on ^C >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Apr 07 07:20:12 PDT 2003 >Closed-Date: >Last-Modified: >Originator: Tim Robbins >Release: FreeBSD 5.0-CURRENT, 8 April 2003 >Organization: The FreeBSD Project >Environment: System: FreeBSD 5.0-CURRENT, 8 April 2003 Problem also occurs on a system from March 30 ie. before Jeff's thread signal mask code was committed. >Description: If you run chpass or vipw and press ^C in vi, vi exits immediately and says: Error: input: Input/output error instead of writing Interrupted and continuing. This is a regression over 4.x (specifically 4.8). It may be necessary to press ^C more than once to trigger the bug sometimes (esp. for vipw). >How-To-Repeat: See above. >Fix: Not known. Suspect signal handling bug in libutil. Needing to press ^C twice to get vipw's vi invocation to die makes me think of SA_RESETHAND. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030407141422.3A994C90D>