Problem Description: When SecureCRT remotely connects to CentOS, restarting the service will show garbled characters.
Workaround:
1, Modify the configuration of the remote Linux machine
[[Email protected] ~] #vi/etc/sysconfig/i18n
Change Lang to a character set that supports UTF-8
such as: lang= "ZH_CN. Utf-8″ or lang= "en_US. Utf-8″ This article modifies the latter
2. Modify The session Options of the Secure CRT
Options->session options->appearance->font-> New Arial Character set: Chinese GB2312->character encoding to UTF-8
3, OK.
Securefx Login Chinese garbled
Problem description
SecureCRT and Securefx The general options inside has been set to UTF-8, but in the securecrt of the new Chinese folder, in the Securefx is still garbled, this problem, find a lot of methods, and finally solved, here and everyone share under.
View server encoding
Look at the Linux code, modify it for your own needs, this article will have UTF-8 as an example to illustrate.
To modify the configuration file for a Linux server:
[Email protected] ~]# vi/etc/sysconfig/i18n
If you select the Chinese system when installing the system, change the Lang field to:
Lang= "ZH_CN. UTF-8 "
If the English system is selected when installing the system, change the Lang field to:
Lang= "en_US. UTF-8 "
General Solutions
1. Right-click on the SecureCRT Connection tab.
2. In the pop-up window, select the "Appearance" tab in the left column and select UTF8 in the right window:
3. In this case, the Chinese is displayed normally in the SECURECRT:
In this case, although the Chinese can be displayed, but the new Chinese folder in Securefx is still garbled in the SECURECRT, how is this problem solved? It needs to be configured by modifying the configuration file, which is described below.
Configuration file to set up
1. Locate the Securefx Configuration folder (Options-Global options, General Configuration folder), such as: C:\Users\ZhangYQ\AppData\Roaming\VanDyke\Config;
2. In the sessions subdirectory under the Configuration folder, locate the session file (. ini extension) for the SECURECRT connection, and double-click open;
3. Find filenames Always use UTF8, change the parameter after the = number to 00000001, save exit.
SECURECRT Login CentOS 6.4 garbled problem