[email protected] wrote:
The most broken part of bash is its signal handling:
cd /net/somehost/file/dir ; rm -rf *
"somehost" hangs; now you type a ^C to interrupt the "cd".
What happens?
bash-3.2$ sleep 10; echo foo
^C
foo
bash-3.2$
Any other shell:
$ sleep 10; echo foo
^C$
Casper has mentioned this a couple of times on this alias, and I agree
that the example above doesn't behave the way I would want or expect.
Now I'm curious: Is there a faction out there arguing that the current
bash behavior is correct and shouldn't be changed? Does someone actually
rely on the current behavior?
Scott
--
Scott Rotondo
Principal Engineer, Solaris Security Technologies
President, Trusted Computing Group
Phone/FAX: +1 408 850 3655 (Internal x68278)
_______________________________________________
opensolaris-discuss mailing list
[email protected]
