Skip to main content

A new locale

I cannot say that I completely understand how this works. I cannot even say that I understand even the basics. In this case, however, I managed to let my intuition guide me and I seem to have gotten to the finish line.

The challenge ahead of me is that I'm getting a new warning message from mercurial when I attempt to pull the latest changesets from my repository:
-bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)

I have 3 machines. My desktop, a development system and a mercurial repository. Let's call them desk, dev, and repo; respectively.

My .profile on my desktop had a few interesting statements:
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8

And the values were brought forward to my dev machine. Assuming that term has a way to pull these values from nested terminal sessions. Then when I issue mercurial commands on the dev machine I see the warnings I mentioned earlier.

I logged into all three machines and I executed the command: locale. The results on my desktop and dev were the same (en_US.UTF-8). And on the repo server it was POSIX. Well, I want to repeat that I still do not completely understand why but the following worked.

Option #1: remove the two export lines from my desktop config. This was a snore and sort of expected. Since nothing was being pulled forward through the terminal sessions they each must have used their default values.

Option #2: This is the option that I executed. And for no particular reason over #1. It was all intuition. On both my dev and repo systems I executed the following:
locale
sudo dpkg-reconfigure locales
sudo locale-gen en_US.UTF-8

And then tested the hg command again. It worked. I'm not sure what the side effects are going to be but for the time being all is well. (I remember a time when I was cut/pasting T-SQL using Microsoft's SQL Server and whatever my code editor was at the time but I was in unicode hell.)

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…