Redefine Ctrl+C as the SIGINT

[pgymjp]

Hello,
I've done some hunting on this and other forums as well as my own system and have come up dry. I have a SLES10 box where root is using the Korn shell as the default. There was a lot of system configuration done by the vendor of the app that sits on this box and one of the "features" is that Ctrl+C no longer sends a SIGINT. I just get "^C" when I try. Needless to say, I'd like to redefine this so that I can kill commands/scripts without the need to manually whack the PID.

Where is the Ctrl+C defined and what steps do I take to redefine it to its default behavior?

Thanks,
Jeff

[gogalthorp]

You could start a bash shell just by typing bash at the command line.

[reed9]

According to my google-fu, stty is the command you want.

I would try adding a line to your ~/.kshrc file as such

stty intr '^C'

Make sure to source the file after.

[gogalthorp]

Since this is a root problem the file will be in /root

[reed9]

Since this is a root problem the file will be in /root

True. But if he's logged in as root, ~ points to /root.