Re: "ctrl+c" disabled!

[Edgar Toernig]

"Bill J.Xu" wrote:
> 
> The following is the stty' result, I think it's right
> ----------------------------------------------------------------------------------
> bash-2.05# stty -a
> speed 9600 baud; rows 0; columns 0; line = 0;
> intr = ^C; quit = ^\; erase = ^?; kill = ^X; eof = ^D; eol = <undef>;
> eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
> lnext = ^V; flush = ^U; min = 1; time = 0;
> -parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts
> -ignbrk -brkint ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff
> -iuclc ixany -imaxbel
> 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
> ----------------------------------------------------------------------------------
> but  ^C is bad

Hmm... looks fine.  intr set to ^C and isig enabled.  Maybe you should check what
the terminal program is actually sending:

  od -tx1

Then type Ctrl-C Ctrl-D.  Should print "00000000 03".

How do you kill the process from telnet?  kill -9 <pid> or kill -2 <pid>?
Maybe sigint is ignored (possible if bash was started with ignored sigint -
broken/strange getty).  Is job control (^Z/fg) working?

Ciao, ET.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/