I assume you are talking about BASH (shell) commands.
* type "stty -g"
* if you see " -echo "
* then type "stty echo". this should solve the problem
* if you see " echo ", your problem might be in your terminal/terminal emulator
Of course the characters do not echo back at me until the moment I hit the Enter key. I've go dozens of systems loaded in my ASA application and this system is the only one that behaves in this manner.
That is getting me a little closer, but I'm still struggling with the exact syntax. I've tried to understand what I'm reading in the man pages, but it's eluding me.
dadmin@Service800A> stty -echo [type this in and hit return]
dadmin@Service800A> bash: lskdfj: command not found [try typing characters, no echo]
dadmin@Service800A> stty: when specifying an output style, modes may not be set
dadmin@Service800A> speed 38400 baud; rows 24; columns 80; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
lnext = ^V; flush = ^O; 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
dadmin@Service800A> stty: when specifying an output style, modes may not be set
dadmin@Service800A>
OK,
Note the "-echo" in the "stty -g" output. This is your problem. Just type "stty echo" and you will be happy - at least until you login next time. If the problem returns next time you login, you might look at your ".bashrc" and/or ".bash_profile" files to see if there is a "stty -echo" in one of those files.
I do the command as you've laid it out, but the characters do not echo until after I hit the carriage return/enter key.
dadmin@Service800A> stty echo
dadmin@Service800A> server
SERVER STATUS
Cluster ID: 001
Duplication: hw
Standby Busied? no
Standby Refreshed? yes
Standby Shadowing: on
Duplication Link: up
Elapsed Time since Init/Interchange: 186d 10:14:47
Service800A Service800B
ID: 001 (1) ID: 002 (2)
Mode: Active Mode: Standby
Major Alarms: yes Major Alarms: no
Minor Alarms: no Minor Alarms: no
Control Network: 1 / 1 / 2 Control Network: 1 / 1 / 2
Server Hardware: okay Server Hardware: okay
Processes: okay Processes: okay
dadmin@Service800A>
1. try "stty sane" #(I don't expect it to help, but it is easy)
2. It sounds like you are in "line buffered" mode. Are you logging in directly to the Bash shell, are you doing a "go shell" in ASA, or are you starting bash (shell) in some other way?
I'm logging into CM and using the "go shell" command. This is so strange and should be so simple, that I'm starting to think it may be specific to this load. I'll try the "stty sane" tomorrow and let you know what happens.
Definityandcmuk, how did you fix yours in the past?
Sounds like a SAT bug to me. Maybe someone should report it to Avaya.
OK, here are some alternative ways to try to solve the problem:
1. do not "go shell". Use a login that starts at bash and then you can start SAT manually, if necessary. This will almost undoubtedly solve the buffering problem, but may not be the way you want to work.
2. after you "go shell", type "exec bash". There is a small chance this might solve the buffering problem.
3. {note, this is a ugly kludge, but it will probably work} after you type "go shell", type the following:
ed # this starts the ed editor
!bash # note the exclamation, this starts a fresh bash
# now type your bash commands
# to return to SAT, type the following:
exit # exits "new" bash
q # exits ed.
exit # exits the funky bash. I said this was ugly!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.