/etc/default/init LANG Setting Not Working


 
Thread Tools Search this Thread
Operating Systems Solaris /etc/default/init LANG Setting Not Working
# 8  
Old 11-16-2015
Okay, so that pointed me in the right direction. My terminal is sending the en_US.UTF-8 LANG setting.

What was curious the same configuration didn't produce the same results on the old server. What I found was that the old server didn't have the en_US.UTF-8 locale installed. So the terminal was attempting to set it but it wasn't accepted on the other side and dropped to the C locale by default.

Code:
bash-3.2# locale -a
C
POSIX
en_CA
en_CA.ISO8859-1
en_CA.UTF-8
en_US
en_US.ISO8859-1
en_US.ISO8859-15
en_US.ISO8859-15@euro
es
es_MX
es_MX.ISO8859-1
es_MX.UTF-8
fr
fr_CA
fr_CA.ISO8859-1
fr_CA.UTF-8
iso_8859_1

The new server has the locale after installing the North America (nam) region from disk. Doesn't look like I can remove en_US.UTF-8 without removing the entire nam region according to localeadm. Had the same trouble when attempting to just install en_US. I had to install all of nam.

Guess I just need to override it in the profiles for the application. Thanks for your help guys.
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. AIX

Undestanding LANG setting in /etc/environment

Hi All, We had issue with a application which reports process counts in log, application used to log process counts as Integer data type (1500). One fine morning we started seeing process counts in application log as Decimal (1,500). Our UNIX admin did investigate and figured-out that... (5 Replies)
Discussion started by: Aaron Boyce
5 Replies

2. Red Hat

init-script failing because of /etc/rc.d/init.d/functions

I encountered a problem on one of our database servers. OS: CentOS 5.5 final Kernel: 2.6.18-238.5.1.el5.028stab085.2 (OpenVZ kernel) We wrote some DB-Start/Stop-scripts ("/db2/admin/scripts_dba/start_services.ksh" and ".../stop_services.ksh") to start the database instances. (Database... (1 Reply)
Discussion started by: bakunin
1 Replies

3. Debian

Iomega ix2-200 Custom Debian - Autostart script in init.d not Working

!!Hello Everyone!! I Recently purchased a Iomega iX2-200 NAS that runs a custom debian installed by Iomega (Linux Debian 5.0.2 ( 2.6.22.18 armv5tejl)) . I have SSH access. I installed Transmission since the factory installed torrents manager that Iomega uses is terrible. Transmission-daemon... (1 Reply)
Discussion started by: stejimenez
1 Replies

4. Linux

How to I change init levels after typing init 1

Dear all, I typed in init 1 on my redhat box as root and according to wikipedia (http://en.wikipedia.org/wiki/Runlevel): 1 Single-User Mode Does not configure network interfaces, start daemons, or allow non-root logins So now I can't connect back to it. How do I change the init back to 3?... (8 Replies)
Discussion started by: z1dane
8 Replies

5. UNIX for Dummies Questions & Answers

Setting the $LANG info needed

Hello (Very New to UNIX -Solaris 10) I'm trying to set the LANG variable to C but not sure if it's getting set, need some help on this. Currently I have it set to en_GB.UTF-8 I need to set it to C for an install. but when I run set LANG=C and then run echo $LANG its still set to... (2 Replies)
Discussion started by: deedaz
2 Replies

6. Solaris

Solaris 10 - init stops working

I have a really strange issue on Solaris 10 running on v490. I'm running Oracle 10g on the box. Everything runs fine and all of a sudden I get a call from a DBA. I check and none of the Oracle processes are running. They were definitely running after the system booted and nobody stopped them. I try... (0 Replies)
Discussion started by: GKnight
0 Replies

7. AIX

Setting Variables not working

Hi all, I am trying to set up some variables in a shell script. The variables contain values of various paths needed to run a java module. The problem is the variables dont seem to be setting at all. here is what i am trying to do : JAR_HOME=/home/was5/bdcms/scheduledjobs/lib export... (1 Reply)
Discussion started by: rpandey
1 Replies
Login or Register to Ask a Question
environ(5int)															     environ(5int)

Name
       environ - natural language support (NLS) environment variables

Description
       The  international  environment	variables  are defined for the ULTRIX system and are additional to those described in the ULTRIX reference
       pages, Sections 2 (system calls) and 3 (routines), and the reference page.  The international variables are made available to a process by

       This reference page is divided into two sections.  The first section describes environment variables that can control the  locale  setting.
       The  second  section  describes the variables that control where the function searches for message catalogs and where the function searches
       for language databases.

   Environment Variables That Control the Locale Setting
       The LANG, LC_COLLATE, LC_TYPE, LC_NUMERIC, LC_TIME, and LC_MONETARY environment variables can control the locale setting.  You define these
       variables using the same format as the locale argument to the function.	The following shows the format you use:
       language[_territory[.codeset]][@modifier]
       In  language,  you specify the native language of the user.  You can optionally specify the user's dialect and codeset using _territory and
       codeset.  For example, the following definition of LANG specifies the French native language,  as  spoken  in  France  (as  opposed  to	in
       Switzerland), and the Digital Multinational Character Set:
       LANG = FRE_FR.MCS
       In @modifier, you specify a specific instance of localization data within a single category.  For example, using @modifier, you can specify
       telephone directory ordering of data, as opposed to dictionary ordering of data.  You cannot use @modifier to define the LANG variable.

       The following list describes the environment variables that control the locale setting:

       LANG	      Identifies the user's requirements for native language, local customs, and coded character set. At run time,  you  can  bind
		      the user's language requirements, as specified by the setting of to the execution of a program by calling as follows:
		      setlocale (LC_ALL, "");

		      If  is  not  defined in the current environment, the locale defaults to the C locale.  For more information on the C locale,
		      see the POSIX Conformance Document.

		      System administrators can define to provide a  default setting for the system as a whole, or user's can define  individually
		      using standard command interpreter facilities.

       LC_COLLATE     Contains	the  user's  requirements  for	language,  territory, and codeset for the character collation format.  affects the
		      behavior of regular expressions and the string collation functions in and If is not defined in the current environment, pro-
		      vides the necessary default.

       LC_CTYPE       Contains	the  user's requirements for language, territory, and codeset for the character classification and conversion for-
		      mat.  affects the behavior of the character-handling functions in and If is not defined in the current environment, provides
		      the necessary default.

       LC_MONETARY    Contains	the user's requirements for language, territory, and codeset for the monetary format.  affects the currency string
		      in If is not defined in the current environment, provides the necessary default.

       LC_NUMERIC     Contains the user's requirements for language, territory, and codeset for the numeric data presentation format.  affects the
		      radix  and thousands separator character for the formatted I/O functions in and the string conversion functions in and If is
		      not defined in the current environment, provides the necessary default.

       LC_TIME	      Contains the user's requirements for language, territory, and codeset for the time format.  affects the behavior of the time
		      functions in If is not defined in the current environment, provides the necessary default.

   Environment Variables That Specify Locations
       The NLSPATH and INTLINFO environment variables control where the and functions search for message catalogs and the language databases.  You
       define these variables using a pathname or set of pathnames.  The pathnames can contain variable elements, called substitution fields, that
       allow  your  program  or the setting of other environment variables to affect the setting of NLSPATH and INTLINFO.  The following shows the
       format you use to define these variables:
       variable-name="[:][/directory][/substitution field]
		  [/file-name][:alternate-pathname][:..."
       You specify either NLSPATH or INTLINFO in place of variable-name.

       A colon (:) that precedes other parts of any pathname in the definition specifies the current directory.

       In directory, you can specify a specific directory in which the function searches.  If you need the environment variable  to  be  flexible,
       you  can  use a substitution field in place of or with directory names.	A substitution field consists of a percent sign (%), followed by a
       code letter.  The substitution fields you can use are as follows:

       %N   The value of the name argument you pass to

       %L   The value of the LANG environment variable

       %l   The language element from LANG

       %t   The territory element from LANG

       %c   The codeset element from LANG

       %%   A literal percent sign

       If a substitution field you specify is currently undefined, or substitutes a null string.  Neither function includes the underscore (_)	or
       period (.) separator in or substitutions.

       You  can  specify more than one pathname when you define these environment variables.  You separate each pathname from the one that follows
       it using a colon (:).  If you need to specify the current directory in a pathname other than the first pathname in the list, use  a  double
       colon (::).  The functions interpret the first colon as a separator between pathnames and the second colon as specifying the current direc-
       tory.

       The following describes the ICONV, INTLINFO, and NLSPATH environment variables:

       ICONV	 The ICONV environment variable stores the directory pathname for the conversion codesets used by the command. If this variable is
		 undefined, searches the directory.

		 The following example shows how to define ICONV:
		 ICONV=/usr/lib/international/conversions
		 In this example, is defined as the directory pathname

       INTLINFO  The  INTLINFO environment variable stores the location of the language database. The function reads INTLINFO when it searches for
		 the database.

		 The following example shows how to define INTLINFO:
		 INTLINFO = ":%L:/usr/lib/intln/%L:/usr/lib/intln/ENG_%t.%c"
		 In this example, the function searches for the language database named in the LANG environment variable.  The	function  searches
		 for  the  variable  in the current directory. If the database is not in the current directory, searches in the directory for that
		 same database. Finally, if the database specified by LANG is unavailable, searches in for  the  English  language  database  that
		 matches the current territory and codeset.

       NLSPATH	 The NLSPATH environment variable controls where the function searches for a message catalog.

		 The following example shows defines NLSPATH:
		 NLSPATH=":%N.cat:/nlslib/%N.cat:nlslib/program.cat"
		 This  definition  causes  to search in the current directory for the message catalog named in the name argument you pass.  If the
		 function cannot find the message catalog in the current directory, it searches in the directory.  If the catalog is not  in  that
		 directory, opens the message catalog.

See Also
       exec(2), catopen(3int), intro(3int), setlocale(3), lang(5int)
       Guide to Developing International Software

																     environ(5int)