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 '/'.
eg:
$ ^C
$ /fred
/fred: not found
$ ^C
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
--
David Laight: david@l8s.co.uk