What is going on with the new preflight check?

Ok, so yes, theres a new pre-flight check, it is rather annoying I know, but it's meant to be.

You see I was getting a lot of random issues raised about things not working and after much troubleshooting, these issues came down to locale based problems, because the script is written in the standard programnming language of american english, naturally, the assumption is that all our production servers are in either en_US, en_GB or en_AU.

If you're running a server that is not in one of these locales, the script now gracefully detects this and exits. the only way to fix it is to either:

1. Fix your locale (export LC_ALL=en_US) or

2. Clone / Fork my repository, and write apache2buddy to work in your specific locale. You'd need to check it runs properly and catches any words we grep for such as LISTEN, in your native language.

I've decided that I can't possibly write and maintain a script in several different languages, and I leave it up to the power of opensource, and you the reader to be empowered to make it work for you, in your own locale.

Note that changes to locale support will NOT go upstream unless that locale is an english speaking one, like in issue #137 for example.

EDIT: Yes I did someone in Brazil a favour before and this new check breaks that, you'll see on line 740 the word OUÇA. This was a long time ago before I decided that this would be a thing, I don't know what Locale it was, but its a relic left in the code. I still don't plan to offer support for systems running in any other languages / locales.