If you want to access an iLO behind a firewall, there are some TCP ports that need to be opened on the firewall to allow all iLO traffic to flow through. Here is a list of the default ports used by iLO, but these can be modified on iLO’s Administration… Access… Services… tab.

ILO FUNCTION SOCKET TYPE PORT NUMBER
———————- ———– ———–
Secure Shell (SSH) TCP 22
Remote Console/Telnet TCP 23
Web Server Non-SSL TCP 80
Web Server SSL TCP 443
Terminal Services TCP 3389
Virtual Media TCP 17988
Shared Remote Console TCP 9300
Console Replay TCP 17990
Raw Serial Data TCP 3002


perl -MCPAN -eshell

install Term::ReadKey
install DBD::mysql

exit

Quick Linux Tip:

If you’re trying to delete a very large number of files at one time (I deleted a directory with 485,000+ today), you will probably run into this error:

/bin/rm: Argument list too long.

The problem is that when you type something like “rm -rf *”, the “*” is replaced with a list of every matching file, like “rm -rf file1 file2 file3 file4″ and so on. There is a reletively small buffer of memory allocated to storing this list of arguments and if it is filled up, the shell will not execute the program.

To get around this problem, a lot of people will use the find command to find every file and pass them one-by-one to the “rm” command like this:

find . -type f -exec rm -v {} \;

My problem is that I needed to delete 500,000 files and it was taking way too long.

I stumbled upon a much faster way of deleting files – the “find” command has a “-delete” flag built right in! Here’s what I ended up using:

find . -type f -delete

Using this method, I was deleting files at a rate of about 2000 files/second – much faster!

You can also show the filenames as you’re deleting them:

find . -type d -print -delete

…or even show how many files will be deleted, then time how long it takes to delete them:

root@devel# ls -1 | wc -l && time find . -type f -delete
real    0m3.660s
user    0m0.036s
sys     0m0.552s

Options +FollowSymlinks
RewriteEngine on
rewritecond %{http_host} ^domain.com [nc]
rewriterule ^(.*)$ http://www.domain.com/$1 [r=301,nc]

bu ornekte

siteye domain.com olarak girenleri www.domain.com a yonlendirdik

root@yedek:~# cat /etc/debian_version
6.0.3

debian kurduk standart br sekilde lvm ile
daha sonra lvm mizi yeni diskler ekleyerek buyuttuk
legacy grub lvmyi sikine takmasada kullandigim grub2 default gelen yeni debian ile yeni kernel guncellemesinde sicti.
neden
cunku grub2 lvm de ne oluyor bitiyor onemsiyor.
benim icin acil cozum gerekli idi
su sekilde yaptim

1- aptitude purge grub
2- aptitude purge grub-common (30 tane sey sorcak he de gec)
3- aptitude install grub-pc (grub2 paketi bu olsa gerek)
bunlari yapamadi gene hata verdi
cunku disk uid leri ile ilgili bir salaklik vardi
o zaman su komutu calistirdim

#1 | Written by drdrape about 4 months ago.

You can also run
sudo grub-mkdevicemap
which will update /boot/grub/device.map automatically

device mapi guncelledi kendisi
sonra oldu bitti

detayli hata logu ve basima gelende su posttakine benzer bir durumdu.


While installing security updates in a seldomly used virtual machine, the latest kernel package was ready to be configured when I got the following error:

Setting up linux-image-2.6.32-5-amd64 (2.6.32-31) ...
Running depmod.
Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.32-5-amd64 /boot/vmlinuz-2.6.32-5-amd64
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 2.6.32-5-amd64 /boot/vmlinuz-2.6.32-5-amd64
Generating grub.cfg ...
/usr/sbin/grub-probe: error: Couldn't find PV pv1. Check your device.map.
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.32-5-amd64.postinst line 799.
dpkg: error processing linux-image-2.6.32-5-amd64 (--configure):
subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
linux-image-2.6.32-5-amd64

First I didn't quite get the line about "Couldn't find PV pv1. Check your device.map", but after some time it dawned on me that "PV" might mean "physical volume", a term used by LVM. I also remembered that I extended the LVM volume group with an additional block device that I attached to the virtual machine.

If it’s a Linux box

ssh -ND 1234 user@ip

Setup your web browser to SOCKS proxy and localhost:1234

Option 2: Mount your own ISO via KVM virtual media

1. At the top left, choose ‘Virtual Media’ -> ‘Virtual Storage’.
2. Choose the ‘CDROM&ISO’ tab on the dialog box that pops up.
3. Change logical drive type to ‘ISO file’.
4. Press ‘Open Image’ and select the ISO file on your local system.
5. Press ‘Plug In’ and then ‘OK’


Remmina is a remote desktop client written in GTK+, aiming to be useful for system administrators and travellers, who need to work with lots of remote computers in front of either large monitors or tiny netbooks. Remmina supports multiple network protocols in an integrated and consistant user interface. Currently RDP, VNC, NX, XDMCP and SSH are supported.

Remmina is released in separated source packages:

“remmina”, the main GTK+ application
“remmina-plugins”, a set of plugins

Remmina is free and open-source software, released under GNU GPL license.

http://remmina.sourceforge.net/

 

proxmox uzerinde kvm qemu ile

virtio disk ve network driverlarini kullanarak centos makinasi kurduk

kurulumdan sonra

cat /proc/cpuinfo dedigimizde Qemu Virtual CPU yaziyor

uygulamalar begenmeyip tiri viri yapiyorsa, su sekilde yapacagiz

vm noduna login ettikten sonra

nano /etc/qemu-server/VMID.conf

an alta ekle

args: -cpu host

VM yi stop et , start et , reboot is gormez

artik sanal makinamiz host node cpu sunu gorecek

cat /proc/cpuinfo

original: http://pingbin.com/2011/07/view-the-routing-cache-and-hits/

Most of us check the normal thinks like traceroute or arp on a web server, but actually checking recent routing table lookup’s can be a great tool. Doing this you can see if your actually using the right interface or if the application is even requesting the traffic to be routed by your OS.

When debugging a networking issue it can be invaluable to see your linux servers current routes to get an idea of what’s going on, also you can view the number of hits these routes have recently gotten, just look in the use column of the output table.

1
route -neeC

You should see something like the following output:

1
2
3
4
5
6
7
8
root@:/# route -neeC
Kernel IP routing cache
Source          Destination     Gateway         Flags Metric Ref    Use Iface    MSS   Window irtt  TOS HHRef HHUptod     SpecDst
78.46.172.35    208.43.68.59    192.0.2.1             0      0        2 venet0   1500  0      800   0   -1    0      78.46.172.35
67.228.213.178  78.46.172.35    78.46.172.35    l     0      0       23 lo       0     0      0     0   -1    0      78.46.172.35
78.46.172.35    72.46.130.42    192.0.2.1             0      0        1 venet0   1500  0      875   0   -1    0      78.46.172.35
82.103.128.63   78.46.172.35    78.46.172.35    l     0      0       23 lo       0     0      0     0   -1    0      78.46.172.35
78.46.172.35    174.34.156.130  192.0.2.1             0      0        1 venet0   1500  0      735   0   -1    0      78.46.172.35

From the above we can see some very interesting stats such as the interface used, source and destination IP’s, metric, number of ‘uses’ and even the interface MTU