Subject: shell blocking ^C
To: None <email@example.com>
From: David Laight <firstname.lastname@example.org>
Date: 10/22/2002 17:36:56
I think this might have been introduced by the recent vfork
changes to /sbin/sh - OTOH it might be a bug in my local changes :-(
Can someone please check whether the 'current' /bin/sh still
acts on ^C at the command line (by putting out a new prompt)
after it fails to exec a command whose path includes a '/'.
/fred: not found
At this point I don't get a new prompt.
(The ^C may, or may not be echoed.)
The problem is an unmatched INTOFF...
David Laight: email@example.com