
Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[tlug] Bash question
- Date: Mon, 16 Sep 2019 17:13:54 -1000
- From: "David J Iannucci" <jlinux@example.com>
- Subject: [tlug] Bash question
- User-agent: Cyrus-JMAP/3.1.7-237-gf35468d-fmstable-20190912v1
Hey, I've got a good technical question :=)
I've got an RHEL7 install on a virtual machine at work, and one thing
that is very irritating about it (among others), is that ctrl-C does not
do its job in bash. When I'm running a normal process (like, say,
tail -f), and I hit ctrl-C, "^C" is output, but the process is not
interrupted. I have to do ^Zkill %1, which gets old fast.
I've never seen this sort of thing happen before. How did I get into
this state? Actually, I'm not sure if the box was like this from the
start, or whether it got into this state after I started using it (which
means it's something _I_ did accidentally).
I've done a good 20 minutes of googling but, no solution yet. In
doing so, I learned this command, and this is the output on the box
in question:
$ stty -a
speed 38400 baud; rows 69; columns 141; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = M-^?; eol2 = M-^?; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd -cmspar cs8 -hupcl -cstopb cread -clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc ixany imaxbel iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke
Any clues to help me fix this are much appreciated.
Dave
Home |
Main Index |
Thread Index