Hello,

Say you are running bash and are managing jobs with Ctrl Z, Ctrl D, Ctrl |, etc., or send a backspace as Ctrl H, etc. etc. These are ASCII control codes in the 0 - 31 range that bash picks up.

My question: Are these mapped directly to standard POSIX process signals like SIGKILL, SIGTERM, etc? If so, is there a comprehensive listing some place of how each ASCII control character correlates to the corresponding POSIX process signal?

Stated another way, are ASCII control codes in bash more or less "hotkeys" for various signals you could send to PIDS via kill?

Any illuminating information would be appreciated -- I understand the signals and the codes, just not how they relate to eachother.

Thanks,
Jameson

No - the mapping is done per terminal session though of course there are defaults.

You can run "stty -a" to see a lot of these.

Other capabilities are related to terminfo. If you do "echo $TERM" you'll see your session has a defined terminal type (often xterm or vt100 for most things these days since you're usually emulating a physical terminal - in the old days you were usually on a physical serial terminal of one sort or another). You can dump the terminfo information with the infocmp command. (e.g. infocmp xterm).

For most commands there are man(ual) pages that can be accessed by typing man <command> (e.g. man infocmp, man stty). Also for many configuration files there are man pages (e.g. man terminfo).

Only Control-C, Control-\ and Control-Z (and perhaps a couple more) are related to signals. The other control characters are used to send instructions to the terminal driver, like ringing a bell, tab, backspace, newline, end-of-file, suspend/resume output, page-feed, escape and the likes but this isn't done by sending signals which would be overkill.