CentOS - UTF-8 - unicode start: Difference between revisions

m (corrected minor spelling error.)
No edit summary
Line 2: Line 2:
* You may see many /bin/unicode_start processes running that take up memory and CPU
* You may see many /bin/unicode_start processes running that take up memory and CPU


A solution that seems to work for most:
Edit the file '''/etc/sysconfig/i18n''' from something like this:
 
LANG="en_US.UTF-8"
SUPPORTED="en_US.UTF-8:en_US:en"
SYSFONT="latarcyrheb-sun16"
 
To something like this (no references to UTF-8):
 
LANG="en_US"
SUPPORTED="en_US:en"
SYSFONT="latarcyrheb-sun16"
 
Or, a solution that seems to work for most:
   Edit /etc/sysconfig/i18n
   Edit /etc/sysconfig/i18n
   Remove or comment out all lines that contain UTF-8
   Remove or comment out all lines that contain UTF-8

Revision as of 02:24, 27 January 2007

  • It's been observed that on CentOS the default configuration may not allow zimbra to start.
  • You may see many /bin/unicode_start processes running that take up memory and CPU

Edit the file /etc/sysconfig/i18n from something like this:

LANG="en_US.UTF-8"
SUPPORTED="en_US.UTF-8:en_US:en"
SYSFONT="latarcyrheb-sun16"

To something like this (no references to UTF-8):

LANG="en_US" 
SUPPORTED="en_US:en" 
SYSFONT="latarcyrheb-sun16" 

Or, a solution that seems to work for most:

  Edit /etc/sysconfig/i18n
  Remove or comment out all lines that contain UTF-8
Jump to: navigation, search