Here’s a simple way of changing your Ubuntu server so it won’t be using the splash screen. Great for seeing console, if you’re not using VESA or just plain being old school. first: # sudo nano /etc/grub/menu.lst look for # defoptions= quiet splash change it to – important leave the # in the line. # defoptions= now just run the grub updating tool and you’ll start up without the splash...
When you start up your Windows Mobile device (with a custom ROM) in Canada and probably some other parts of the world, the handy little wizard will tell you that there’s no operator in the database, with a message like this: "The operator does not exist in the database. Please contact your operator for the connection settings". If you want to fix it, just do this: Start->Settings->Connections->Connection Wizard->Menu->untick auto check
For any of you using Nagios Administrator, and you’re native English speakers, the fact that it always defaults to German may irk you. Here’s how to do it. Thanks to h-w on the Nagios Portal Forums. # cd /var/www/nagiosadmin # cd apps/backend/config/ # nano i18n.yml and change the default_culture: de to default_culture: en # cd /var/www/nagiosadmin # ./symfony clear-cache Now you should be good to go and it will load up in english....
It’s easy, once you have nagiosadministrator installed, you’ll probably notice there’s no easy way to actually reach nagios. To add a quick button to the toolbar to do this, follow these steps: SSH to server running nagios/nagiosadministrator Go to your nagios administrator directory, ours is /var/www/nagiosadmin Now, edit the menu file # nano apps/backend/lib/topMenu.class.php Now, change the first class topMenu from this class topMenu { protected static $items = array( 'contact' => 'Contacts', 'contactgroup' => 'Contact Groups', 'os' => 'Operating Systems', 'service' => 'Services', 'hostgroup' => 'Host Groups', 'host' => 'Hosts', 'command' => 'Commands', 'template' => 'Templates', 'generator' => 'Generator' ); to this...
Tonight we decided we’d had enough of VMWare Server 2.0’s issues and shakiness. We started getting the following error, because as it turns out (we’re stupid for not thinking of this ahead of time – lesson learned) VMWare server beta’s have an expiry date, along with it’s bugs. Today we started getting this error: “VCommand error: This product has expired.” This box holds some Asterisk Development stuff and some other Dev systems that we couldn’t really have go down on us....