ssh -X login@haslo
http://www.softprayog.in/troubleshooting/x-window-remote-display
![]() ![]() ![]() ![]() ![]() |
|
ssh -X login@haslo
http://www.softprayog.in/troubleshooting/x-window-remote-display
For years we’ve used bash scripting to ensure that all of our server configurations are standardised, so that we can expect servers with the same role to have the exact same configuration profile and exhibit the exact same behaviour. We’re in the process of moving to Chef but we’re not quite there yet. Recently we decided to redesign our network architecture with a higher level of focus around High Availability. This new design introduces Percona XtraDB Cluster and we’re writing our installation and configuration scripts to ensure that our new cluster boxes are both tuned and standardised.
We have base template linux VM’s in both VMWare and Oracle VirtualBox, and also templates that are specific to server roles such as web servers, HAproxy servers or MySQL Cluster servers. If we need to test a new configuration, or add a new node to the cluster, we just clone the appropriate template add some minor configuration and we’re good.
However if you clone a VMWare or Oracle VirtualBox VM, you’ll notice that it kills your network interfaces throwing errors like the one listed below:
#ifup eth0 Device eth0 does not seem to be present, delaying initialisation |
What’s happening here is that when you clone your VM, VirtualBox and VMWare apply a new MAC Address to your network interfaces but they don’t update the linux configuration files to mirror these changes and so the kernel doesn’t firstly can’t find or start the interface that matches it’s configuration (with the old MAC Address) and it finds a new interface (the new MAC Address) that it has no configuration information for. The result is that only your networking service can only start the loopback networking interface and eth0 is dead.
So here’s how we fix it:
# rm -f /etc/udev/rules.d/70-persistent-net.rules |
# reboot |
# vim /etc/sysconfig/networking/devices/ifcfg-eth0 |
Remove the MACADDR entry or update it to the new MACADDR for the interface (listed in this file: /etc/udev/rules.d/70-persistent-net.rules).
Remove the UUID entry
Save and exit the file
# service network restart |
SOURCE:
yum install aaaaa
yum provides aaaaa
yum search aaaa
yum grouplist | less
Połącz z serwerem:
sftp://user@example.com:22 ftp://user@example.com:21
I had the need to maintain more than one Java version on a Red Hat Linux machine. I was able to install a new version of Java, and then configure the machine to use the new version by default. It’s also very easy to switch back to using the previous version of Java.
The first step is to download the Java version that you want from the Oracle/Java web site. In my case, I downloaded the following file.
Executing this file as root will perform the installation. You’ll, of course, have to make the file executable after download. By default, the installation “wanted” to install Java in the following directory.
I still wanted to make the new installation the default Java used by the machine. Linux has a nice utility called alternatives to do this, and more specifically, the update-alternatives command. With this command, I was able to first register the newly installed Java as a version of Java that would be recognized by the utility, and I was then able to use the utility to make the new version of Java the default version. When I used the utility to make the newly installed Java the default, the /usr/bin/java on the machine was modified to point to the new version.
Here is the script that I used to have the new version of Java recognized by the alternatives utility.
JAVA_HOME=/usr/java/jre1.6.0_27
# The following command added the new java installation as a java alternative.
# The slave commands bring the related commands with it.
update-alternatives \
–install /usr/bin/java java $JAVA_HOME/bin/java 1 \
–slave /usr/bin/javac javac $JAVA_HOME/bin/javac \
–slave /usr/bin/javadoc javadoc $JAVA_HOME/bin/javadoc \
–slave /usr/bin/jar jar $JAVA_HOME/bin/jar \
–slave /usr/bin/keytool keytool $JAVA_HOME/bin/keytool \
–slave /usr/local/java java_home $JAVA_HOME# A web site suggested that these steps would also be required, but they were not
#ln -s /etc/alternatives/java /usr/bin/java
#ln -s /etc/alternatives/javac /usr/bin/javac
#ln -s /etc/alternatives/javadoc /usr/bin/javadoc
#ln -s /etc/alternatives/jar /usr/bin/jar
#ln -s /etc/alternatives/keytool /usr/bin/keytool
#ln -s /etc/alternatives/java_home /usr/local/java
It’s important to make sure that JAVA_HOME is set to point to the new installation directory. The update-alternatives command links multiple Java utility programs together so that when you switch from one Java version to the next, the proper versions of the related tools come with it (note the slave option in the script above). One web site I visited indicated that I would have to update symbolic links, but the links were made automatically when I tried this on Red Hat 5 and 6.
Running the script above does not make the new version of Java the default. It simply registers that version of Java as a known version of java. Run the following command to change the default.
You should see the following after entering the above command.
There are 3 programs which provide ‘java’.Selection Command———————————————–1 /usr/lib/jvm/jre-1.5.0-gcj/bin/java*+ 2 /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java3 /usr/java/jre1.6.0_27/bin/javaEnter to keep the current selection[+], or type selection number:
I entered 3, and pressed the enter key, and the newly installed version of Java became the default. You can run the update-alternatives command again to change the version back.
I assume that this works on other flavors of Linux as well, but I’ve never tried. I have done this on both Red Hat Linux 5 and 6
SOURCE:
http://mikes-web-site.blogspot.com/2012/02/maintaining-multiple-java-versions-on.html
Fedora 64 bit: /usr/lib64/mozilla/plugins
chmod 755 libflasplayer.so
check the output of lsmod
and look for iwlwifi
and iwldvm
to see if the module is loaded, if not, you can load it yourself using modprobe -v iwldvm
yum search iwl
you’ll see iwl6000-firmware, iwl6000g2b-firmware, and so on.
lshw – hardware monitor
monitor
xrandr
xrandr –output DVI-1 –right-of DisplayPort-0
/usr/bin/mysqldump –user=root –password=haslo –max_allowed_packet=99M –default-character-set=latin1 -c –insert-ignore –skip-set-charset -r 130619_latin1_biblioteka.sql biblioteka
file
nazwa_pliku_dumpa.sql (pokazuje w jakim jest kodowaniu)
iconv -f ISO8859-2 -t UTF-8 nazwa_pliku_dumpa.sql > nazwa_pliku_dumpa-utf-8.sql
drop database
CREATE DATABASE nazwa_bazy_danych CHARACTER SET utf8 COLLATE utf8_general_ci
mysql -uroot -ppassword --default-character-
set
=utf8 nazwa_bazy_danych < nazwa_pliku_dumpa-utf-8.sql
zmiana templateów:
for i in *.tpl; do iconv -f ISO8859-2 -t UTF-8 $i > $i”_utf8″; done
for i in *.tpl; do mv “$i” “$(basename “$i” .tpl).tpl_iso8859_2″; done
MAIL FROM:<God@heaven.af.mil> 250 ok RCPT TO:<angels@heaven.af.mil> 250 ok DATA 354 ok Hi, guys. Just testing our new mail system. . 250 Written safely to disk. #902487694.289148.12219.
Strona startowa: www.jaceksen.pl