On Sun, Jun 27, 2010 at 02:13:01PM +0930, Damon McMahon wrote:
> Greetings,
>
> I need someone to hit me with a clue-stick here. I was trying to get a
> status of ping(1) using ^T but it appeared not to be sending a SIGINFO
> command. Reading through the man pages I see that stty(1) defines this
> behaviour, and sure enough...
>
> # stty -a
> speed 9600 baud; 24 rows; 80 columns;
> lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl
> -echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo
> -extproc -xcase
> iflags: -istrip icrnl -inlcr -igncr -iuclc ixon -ixoff ixany imaxbel
> -ignbrk brkint -inpck -ignpar -parmrk
> oflags: opost onlcr -ocrnl -onocr -onlret -olcuc oxtabs -onoeot
> cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -mdmbuf
> cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>;
> eol2 = <undef>; erase = ^?; intr = ^C; kill = ^U; lnext = ^V;
> min = 1; quit = ^\; reprint = ^R; start = ^Q; status = <undef>;
> stop = ^S; susp = ^Z; time = 0; werase = ^W;
>
> Yep, status is not bound to ^T
>
> My question is where in the boot or logon process is stty(1) executed,
> or more to the point, why is my system not configured with the default
> behaviour?
What makes you think this would be the default behaviour? (I really
don't know - but it works the same for me...)
Joachim
