Recently I have set up an Apache Tomcat. As a replacement for the Tomcat manager I deployed Psi-Probe for easy deployment and access to statistics.
Afterwards I installed the production software which needs to add a JVM parameter user.country=CH to have the proper date and time format used in Switzerland. This had a unwanted side-effect to Psi-Probe. The Interface switched to German, no way to switch the language back to English. Since my mother tongue is German, no big deal so far. Really? No! I had really problems to understand what navigation items etc. are meaning. The German translation was that bad, it actually crippled the application.
I had the choice to either life with it, or change it and contribute it to the project. I made the later. It was about one hour of work. Hours after submitting, the changed translation file it was in SVN. The next version now comes with a much improved German translation.
This is how open source software works. If someone is not happy with the product, simply change the annoying things and submit it upstream. By the way: Psi-Probe itself is a fork of Lambda-Probe which was not maintained anymore from its origin project owner.
Try to do that with closed source software…
If you try to establish an ISS (Inter Satellite Sync) between two RHN Satellites, do not fully trust the documentation. A slave Satellite must be named by a hostname (IP is not enough) and must have an A and a PTR DNS record or have an /etc/hosts entry. Check it before restarting the satellite by issuing rhn-satellite restart. The check is simply done by entering gethostip rhn.example.com and getent hosts <IP-address> on the commandline.
When Quoting the documentaion at Red Hats web site: http://www.redhat.com/docs/en-US/Red_Hat_Network_Satellite/5.3/Installation_Guide/html/s2-sync-iss-config-master.html: allowed_iss_slaves=rhn.example.com means: A hostname, not just an IP. It is not clearly stated what kind of quality such an entry needs to have.
The Apache httpd is one of the most stable software pieces which is still in use. The latest huge step forward was with the release of 2.0. Quo vadis Apache httpd? The most current release is 2.2.15. During the 2.2.x release cycle, there have basically been only bug-fix releases (Okay, response header rewrite starting on 2.2.9 is a nice feature). This brings me to the question: What is going on with 2.4?
The answer is quite simple: As you can read on http://httpd.apache.org/docs/trunk/new_features_2_4.html, not much. Why is the Apache httpd developing so slow? From my point of view the answer is quite simple: Apache httpd is finished. It is stable, reliable and has (almost) all features people wish. @Apache httpd developers: Great job! Thanks a lot!
Additionally there are tons of external modules to enhance the capabilities of this really great piece of software.
Honestly I can not publish my wish-list for the Apache httpd because there are no open wishes for me. Can someone have such a wish list? Please let us know and write a comment.
Spacewalk 1.0 has been released
Spacewalk is the upstream project for Red Hat’s RHN Satellite software, one of the best systems management software available for Linux Systems.
In the past few weeks one could see a lot of git commits on the source repository of spacewalk. There is no changelog available yet. The road map mentioned compatibility with Apache Tomcat 6.0.x to be able to install spacewalk on Fedora12 and RHEL6.
There should have also been several enhancements in the phyton API and long awaited feature enhancements such as host-renaming (confirmed). Further repository synchronization should be much faster now (Announced in a earlier feature note).
Sorry folks, a lot of “should”, “maybe” etc. I just have been reading the git commit logs and the announcement of the 1.0 release. As long as there is not official changelog available we only can speculate on the precise enhancements.
I’ll install this on my test system soon. If something really uncommon happens or an astonishing new feature appeared, I’ll let you know,