Re: Bash 4.3 no longer handles traps when reading input with read

On 2/19/14 1:51 AM, konsolebox wrote: > Bash-4.3 handles signals and traps when a read run by the read builtin is > interrupted by a signal. I'm not sure that's the best thing to do, > since traps should really be run when commands finish, but we're going to > try it. > > S

two ESC . in a row on a fresh shell kills it

Try su - nobody #(pristine account) then type : then type ESC . ESC . Whammo! The shell dies! The second ESC . acts like ^D. # su - nobody No directory, logging in with HOME=/ nobody@jidanni5:/$ cd /tmp nobody@jidanni5:/tmp$ script Script started, file is typescript nobody@jidanni5:/tmp$ : nobody