>Number:         1788
>Category:       bin
>Synopsis:       /bin/sh -c signal handling error
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Nov 25 08:05:02 1995
>Last-Modified:
>Originator:     Shinya Taniguchi
>Organization:
 ____________________
<                    Shinya Taniguchi (root@peta.phys.sci.osaka-u.ac.jp) >
<----- Department of Physics, Faculty of Science, Osaka University ------>
<--- Tel : +81 6-850-5346 (dial in)    Fax : +81 6-850-5529 ------------->
< Mosaic : http://peta.phys.sci.osaka-u.ac.jp/index.html ________________>
>Release:        NetBSD-current as of Nov. 3
>Environment:
System: NetBSD peta.phys.sci.osaka-u.ac.jp 1.1_ALPHA NetBSD 1.1_ALPHA (PETA) #0: Fri Nov 3 23:38:22 JST 1995 root@peta.phys.sci.osaka-u.ac.jp:/usr/src/current/src/sys/arch/i386/compile/PETA i386


>Description:
When we make command "/bin/sh -c <any executable command>" and hit Ctrl-c,
sometimes the bad situation occur that the process "/bin/sh" is killed unexpectably.
Then we can`t access the command and lose controll.
For example, if you make command "/bin/sh -c vi" and Ctrl-c, then "/bin/sh" is killed  
and the terminali`s behavior becomes strange.
>How-To-Repeat:
env EDITOR=vi crontab -e and hit Ctrl-c
>Fix:
>Audit-Trail:
>Unformatted: