결론만 말하자면, 서버에서 Ctrl-E 메시지를 보내면 터미널은 자신의 존재를 알려야 하는데,
이러한 이유로 인해서, PuTTY 라는 명령어가 응답 메시지로 기본 저장이 되어있고, 그러다 보니 나도 모르는 사이에
어느샌가 화면 가득 PuTTYPuTTYPuTTYPuTTY 라고 가득 차 있게 되는 것이다.
해결 방법으로는 answerback 메시지를 등록하지 않는 방법 정도인 듯 하다.
A.7.12 When I cat a binary file, I get ‘PuTTYPuTTYPuTTY’ on my command line.
Don't do that, then.
This is designed behaviour; when PuTTY receives the character Control-E
from the remote server, it interprets it as a request to identify
itself, and so it sends back the string ‘PuTTY’
as if that string had been entered at the keyboard. Control-E should
only be sent by programs that are prepared to deal with the response.
Writing a binary file to your terminal is likely to output many
Control-E characters, and cause this behaviour. Don't do it. It's a bad
plan.
To mitigate the effects, you could configure the answerback string to be empty (see section 4.3.7);
but writing binary files to your terminal is likely to cause various
other unpleasant behaviour, so this is only a small remedy.
[출처 : http://www.chiark.greenend.org.uk/~sgtatham/putty/faq.html#faq-puttyputty]
4.3.7 ‘Answerback to ^E’
This option controls what PuTTY will send back to the server if the server sends it the ^E enquiry character. Normally it just sends the string ‘PuTTY’.
If you accidentally write the contents of a binary file to your
terminal, you will probably find that it contains more than one ^E
character, and as a result your next command line will probably read
‘PuTTYPuTTYPuTTY...’ as if you had typed the answerback string multiple
times at the keyboard. If you set the answerback string to be empty,
this problem should go away, but doing so might cause other problems.
Note that this is not the feature of PuTTY which the server will typically use to determine your terminal type. That feature is the ‘Terminal-type string’ in the Connection panel; see section 4.14.3 for details.
You can include control characters in the answerback string using ^C notation. (Use ^~ to get a literal ^.)
[출처 : http://tartarus.org/~simon/putty-snapshots/htmldoc/Chapter4.html#config-answerback]
Answerback to ^E 옵션의 위치
4.14.3 ‘Terminal-type string’
Most servers you might connect to with PuTTY are designed to be
connected to from lots of different types of terminal. In order to send
the right control
sequences to each one, the server will need to know what type of
terminal it is dealing with. Therefore, each of the SSH, Telnet and
Rlogin protocols allow a text string to be sent down the connection
describing the terminal. On a Unix server, this selects an entry from the termcap or terminfo database that tells applications what control sequences to send to the terminal, and what character sequences to expect the keyboard to generate.
PuTTY attempts to emulate the Unix xterm program, and by default it reflects this by sending xterm
as a terminal-type string. If you find this is not doing what you want
- perhaps the remote system reports ‘Unknown terminal type’ - you could
try setting this to something different, such as vt220.
If you're not sure whether a problem is due to the terminal type
setting or not, you probably need to consult the manual for your
application or your server.
[출처 : http://tartarus.org/~simon/putty-snapshots/htmldoc/Chapter4.html#config-termtype]
qlock-install.exe
