When I remote login with ssh to a S10 system, even though I have only
LANG environment set at local machine, I also get LC_ALL setting at
the remote machine. This affects application execution behavior since
not all users or applications are also checking and setting LC_ALL.
ssh must not set LC_ALL by itself unless the LC_ALL is set at the local
machine.
To reproduce:
1. From a local machine, set LANG to for instance en_US.UTF-8 (in csh example
at below):
system% setenv LANG en_US.UTF-8
system% locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_ALL=
2. Remote login using ssh at a S10 system. After the login, see LC_ALL is
set by ssh which is not necessary and must not be set by the ssh:
system% ssh sparc-build.sfbay
guest@sparc-build's password:
Last login: Mon Jan 24 16:56:50 2005 from system
Sun Microsystems Inc. SunOS 5.10 s10_74l1 January 2005
sparc-build% locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_ALL=en_US.UTF-8
sparc-build%
xxxxx@xxxxx.com 2005-1-25 01:08:36 GMT
Work Around
Set LC_ALL in the local machine.
xxxxx@xxxxx.com 2005-1-25 01:24:46 GMT