bu ornekte

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

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:

ssh -ND 1234 user@ip

Setup your web browser to SOCKS proxy and localhost:1234

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 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/

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

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.

You should see something like the following output:

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

IRC is still actually quite popular, albeit with the more technical community. However there are some issues with it, most significantly it’s design doesn’t really allow for the mobility of it’s users from one workstation to another which is fairly common practice in a technical community. History is created in realtime without been stored on the server for user retrieval, much like a real world conversation if your not there then you miss what has been said and you can only gain back that history by asking someone what happend (which isn’t going to be that accurate).

Adapting this design requires a middle man of sorts, in this case a VPS server or even a dedicated server if you have one. Basically you install some software on a server, this software connects to the IRC server on your behalf and constantly maintains the session. You keep the same username/handel/nic and ‘session’ with 100% presence in the channel, therefore you also get 100% of the history on the middel man VPS.

As a client from your workstation you then make an IRC connection not to the main IRC server, but your middle man IRC server. This server will then instantly push you the historical data so you can jump straight into the conversation. great isn’t it!

First we need to install the software:

Next you need to follow through the wizard and create a configuration file, the config file will be stored in ~/.znc/configs/znc.conf once created, just run the following command and follow the instructions:

You will be asked for a port to use, I would suggest using the normal IRC port however if your trying to get around a proxy use something like port 80, only if there is no web server attached!

Finally just setup your IRC client to use the proxy vps as the IRC server either the hostname or IP address should work, also don’t forget to give the user name and password or you will get an authentication error

yum install sysstat

iostat can be useful too, e.g. iostat -dx 5

if you want to see the raw transfer rates rather than the i/o stats, you can do:

iostat -k 10 10

which will update 10 times, once every 10 seconds. I personally prefer iostat -x like gordon recommended, but iostat -k is easier to read the M/s

Gule gule kullan