When you are running the new servers, the one thing you do not want to do – is upgrade the kernel. Because that is the only Linux update operation that requires a reboot once it is done — and in a production environment you often can’t have downtime.
“Yum: prevent a updating the packages”Continue reading
Download the rpm file from java.com. Install using the rpm command:
rpm -Uvh jre-7u17-linux-x64.rpm
Use alternatives to config:
[root@localhost ~]# alternatives --config java
There are 2 programs which provide 'java'.
* 1 /usr/java/latest/jre/bin/java
+ 2 /usr/java/jre1.7.0_17/bin/java
Enter to keep the current selection[+], or type selection number:
Select the java you want to use in my case 2. Test using:
[root@localhost ~]# java -version
java version "1.7.0_17"
Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
Create links in the Mozilla Plugins directory:
[root@localhost ~]# cd /usr/lib64/mozilla/plugins/
[root@localhost ~]# ln -fs /usr/java/latest/lib/amd64/libnpjp2.so
There is no specific command on CentOS to set the default route or gateway, there are several ways to do this on CentOS (as there often are). The method I am showing you will work on all versions of CentOS with or without a GUI and involves directly editing the network configuration file using Vim.
Setting default gateway on CentOS first requires us to open /etc/sysconfig/network config file using Vim:
$ vim /etc/sysconfig/network
You now need to add your default GW, if you don’t know the IP of your default GW (aka default route) then you need to ask your ISP / web host or network admin. The example below assumes our default GW is 192.168.0.1
I always append this information to the bottom on the network config file on CentOS.
After adding the default route (GW) you need to restart the networking service using:
# service networking restart
Frequently, customers want to install software in a virtual machine. This can be OK, but frequently they hit a CPU,memory, or IO limit caused by running in a constrained virtual environment.When this happens, we really like to know if they’re running under virtualization when we try to support them. Here’s some tricks to detect, from
a shell, if the system is virtualized.
The first thing to check is dmesg. On a recently-booted system, checking the
‘dmesg’ command output may be sufficient. Otherwise, try “cat /var/log/dmesg”
instead of “dmesg”