We have some specialists in our admin staff, only able to administrate LDAP via phpLDAPadmin. But for several days the connection to the LDAP servers was read-only. It took some time to figure out why.
The configuration in
/etc/phpldapadmin/config.php is very extensive, so I always ignored the failure in the following line:
Do you find the crap? If I comment it out the session isn’t read-only anymore. First we thought of a bug and I started to check the source code, but some more considerations let me have an idea. You might know PHP (like some other languages) interprets everything that is not empty or false explicitly as to be true. So
'false' are all true ;-)
Don’t know who inserted this line, but sometimes (or generally?) you just work to correct the work of somebody else…
Again I installed a new kernel and again X isn’t able to start. Of course the last time I installed the proprietary NVIDIA driver I downloaded it to
Does this sound familiar? There is an alternative!
Once you have installed the driver, you’ve also installed a tool called
nvidia-installer . This tool is able to find the newest driver at nvidia.com and to downloads it itself via FTP. Just type the following:
Even if you save your driver persistently, if you installed a new X version and your old driver is out of date you have to get a new driver! So this trick simplifies the world a lot ;-)
I frequently get asked about the error:
So this article is to answer all questions in a time.
I don’t know why, but that grml kernel has a version number of
grml.02 (other kernel versions are also affected). This version string doesn’t meet the criteria for version numbers because it doesn’t start with a digit. So
dpkg is correctly warning. This warning is not critical, you might ignore it without any consequences, or you can install a newer one.
Kernel with corrected version numbers can be found in
grml-testing , so add the following to your
and you’ll find for example the new 2.6.38 kernel. Just for those lazy guys:
So, have fun with your new kernel :-P
I’m sure everyone of you got livid with the return value of the
atan2 functions. Here is a fix.
This is Java code, but easy to adapt for other languages. And since you are here, a little hint: Multiply the result with
180 / Math.PI to receive the angle in degrees.
I just installed Icinga, it was the right decision!
First of all respect to the Icinga guys, the compatibility to Nagios is great! Moving from Nagios to Icinga is mainly copy and paste. Syntax is the same, management structure also equals, you can even use all your previous installed Nagios plugins and the nagios-checker add on. Well done! Except for the web interface (looks much more professional) every feels like Nagios. So I can’t see any reason to stay with Nagios.
Here are some things I had to do:
- First of all I changed the credentials for the web interface:
- This new user needs also authorizations, so you need to edit
- The rights in
www-datawasn’t able to access the directory. So I wasn’t able to schedule manual checks via web. When I changed the permissions everything was fine:
- I added the following into the
/etc/icinga/apache2.conf, to force me to use SSL encryption:
- I shortened the mail subject of the notifications. By default the subject looks like:
But I’m just interested in the important parts, so I changed the following in
the the notifications now come with a subject like this:
All in all I’m glad that I gave Icinga this chance and recommend to test it if you are still using Nagios. Maybe I’ll test some further Icinga features and maybe we’ll migrate at the university..