dokumani hazirladiktan sonra elbette benden once baskalarinin bu isle ugrastigini ve hazirladigini gordum

onlarida not ettim dokumanin icine.

IRC kurulumu

1- unreal ircd nin .tar.gz guncel versyonunu http://www.unrealircd.com/?page=downloads adresinden indirin
2- ftp ile unreal ircd kurulum yapilacak hesaba girin
3- ana dizin altinda IRC diye bir klasor olusturun
4- indirdiginiz .tar.gz dosyayi buraya upload edin
5- ssh ile putty kullanarak servera baglanin
6- sirayla yapilmasi gereken putty komutlari

# cd IRC
# tar zxvf Unreal3.2.5.tar.gz
# cd Unreal3.2
# ./Config

burada What is the hostname of the server running your IRCd?
sorusuna kadar entera basin bu soru yazdiginda ekrana irc serverin adini yazin.

ornegin

irc.geyikhane.com

NOT: daha onceden bu isimi DNS kaydini serverda acmis olmaniz lazim
veyahut bu isimde bir subdomain acmis olmaniz lazim.

geri kalan sorularida enter enter diye gecebilirsiniz.

config islemi bittikten sonra

# make

# make install

diyoruz bu son komutta hata verme olasiligi yuksek bu dosyayi konfig dosyasi icindeki yerine kopyalamadigina yonelik bi hata ama zaten biz ozel bir yol belirtmedigimiz icin ciddiye almaya gerek yok

unreal irc serverimiz su an calismaya hazir

ama calismadan once bir konfigurasyon dosyasi hazirlamaliyiz.

standart olarak bu dosya

unrealircd.conf adinda olmali ve kurulumu yaptigimiz

/home/kullaniciadi/IRC/Unreal3.2 dizini icinde yer almali

bu ayni dizin icinde zaten irc serverimizi baslatmak ve durdurmak icin kullanacagimiz
./unreal program kisayoluda var

konfigurasyon dosyamizi ayarladiktan sonra

./unreal star diyerek serverimizi calistirabilir
./unreal stop diyerek durdurabilir
./unreal restart diyerek calisan serveri bastan baslatabilir
./unreal rehas diyerek calisan serveri durdurmadan konfigurasyon dosyalarini yeniden sisteme tanitabiliriz.

simdi gelelim konfigurasyon dosyasina:

gene putty ustunden su komutlari yaziyoruz

# cp doc/example.conf unrealircd.conf

konfigurasyon dosyamizi yerine attik

simdi dosyamizi irc serverimizin ayarlarina gore ayarlamamiz lazim

# nano unrealircd.conf

diyoruz

acilan nano metin editoru ile dosyamizda gerekli degisiklikleri yapiyoruz

unrealin konfigurasyon dosyasinda yapilabilecek 10larca degisiklik var

server ip adresi izin verilen port adresleri eger varsa servis konfigurasyonlari oper izinleri sifreleri vb vb

bu konfigurasyon detaylarina bu belgede girmek cok vakit alacagi icin bu adrese goz atabilirsiniz:

http://www.goodmax.net/unreal/unrealircd.conf

ornek konfigurasyon dosyasi

ve

burada da unreal ile ilgili ileri duzey bilgi var

http://www.mirchane.com/unrealircd.php

ve bu adresdede bu yukaridaki yazdigim herseyin resimli anlatimi ve fazlasi var

http://www.frmtr.com/showthread.php?t=87480

—————

konfigurasyon dosyamizi editleyip canimizin istedigi gibi hazirladiktan sonra
tek yapmamiz gereken

./unreal start

irc serveriniz hazirdir

gule gule kullanin

Find is a versatile tool which can be used to locate files and directories satisfying different user criteria. But the sheer number of options for this command line tool makes it at the same time both powerful and encumbering for the user. Here I will list a few combinations which one can use to get useful results using find command.

Find all HTML files starting with letter ‘a’ in your current directory (Case sensitive)
$ find . -name a\*.html

Same as above but case insensitive search.
$ find . -iname a\*.html

Find files which are larger than 5 MB in size.
$ find . -size +5000k -type f

Here the ‘+’ in ‘+5000k’ indicates greater than and k is kilobytes. And the dot ‘.’ indicates the current directory. The -type option can take any of the following values:

f – file
d – directory
l – symbolic link
c – character
p – named pipe (FIFO)
s – socket
b – block device

Find all empty files in your directory
$ find . -size 0c -type f

… Which is all files with 0 bytes size. The option -size can take the following:

c – bytes
w – 2 byte words
k – kilo bytes
b – 512 byte blocks

Note: The above command can also take the -empty parameter.

Find is very powerful in that you can combine it with other commands. For example, to find all empty files in the current directory and delete them, do the following:

$ find . -empty -maxdepth 1 -exec rm {} \;

To search for a html file having the text ‘Web sites’ in it, you can combine find with grep as follows:

$ find . -type f -iname \*.html -exec grep -s “Web sites” {} \;

… the -s option in grep suppresses errors about non-existent or unreadable files. And {} is a placeholder for the files found. The semicolon ‘;’ is escaped using backslash so as not to be interpreted by bash shell.

Note: You can use the -exec option to combine any command in Linux with the find command. Some of the useful things you can do with it are as follows:

Compress log files on an individual basis
$ find /var -iname \*.log -exec bzip {} \;

Find all files which belong to user lal and change its ownership to ravi
# find / -user lal -exec chown ravi {} \;

Note: You can also use xargs command instead of the -exec option as follows:
$ find /var -iname \*.log | xargs bzip –

Find all files which do not belong to any user:
$ find . -nouser

Find files which have permissions rwx for user and rw for group and others :
$ find . -perm 766

… and then list them.

$ find . -perm 766 -exec ls -l {} \;

Find all directories with name music_files
$ find . -type d -iname \*music_files\*

Suppose you want to find files of size between 700k and 1000k, do the following:
$ find . \( -size +700k -and -size -1000k \)

And how about getting a formatted output of the above command with the size of each file listed ?

$ find . \( -size +700k -and -size -1000k \) -exec du -Hs {} \; 2>/dev/null

… here, the ‘2>/dev/null’ means all the error messages are discarded or suppressed.

You can also limit your search by file system type. For example, to restrict search to files residing only in the NTFS and VFAT filesystem, do the following:

$ find / -maxdepth 2 \( -fstype vfat -or -fstype ntfs \) 2> /dev/null

These are the most common uses of the find command. You can see additional uses by reading the find manual.

]]>

/etc dizinimiz olsun
icinde bi dolu dosyamiz olsun
bu dosyalarin icinde istedigimiz bir kelimeyi veya yumagini nasil ariyoruz.
farkli sekilleri ile soyle oluyor.
LKD listelerini uzaktan takip et yakala 😀

Secenek 1


Merhaba,
bu islem icin grep komutunu kullanabilirsiniz. ornegin,
#grep -r "85.247.28.245" /etc
seklinde bir kullanim ile IP adresinin gectigi tum dosyalarin listesini alabilirsiniz. isterseniz > dosya ile de ciktiyi bir dosyaya yazdirabilirsiniz.
Kolay gelsin...

Secenek 2


Selamlar.

ilgili klasore gecip

# find . | xargs egrep -i “88.247.28.245”

yazarsaniz size gectigi dosyalari gosterecektir.

Secenek 3


grep 88\.247\.28\.245 /etc/*
yardimiyla bakabilirsiniz..

Play Lists are great. Your station can support many kinds of players by creating and deploying play lists to your loudcity custom content area. Not only that, your play lists can tell the player to do things like:

-Connect to the Broadband stream
-Is The Broadband stream full? Then connect to the dialup stream

Below are examples for these popular playlist formats:

.PLS (Winamp,Real, iTunes)
.ASX (Windows Media Player)
.RAM (Real Player)
You can create playlist files with any text editor, like Notepad. After you create a playlist, upload it to your Custom Content folder at LoudCity and link to it from your custom paunch page.

We hope you find these samples helpful.

.PLS (WinAmp, iTunes)
For the most part, WinAmp will respond to .PLS files. iTunes and Real Player also will if configured to do so. Windows Media Player will, but generally speaking, WindowsMedia player can’t play SHOUTcast streams this way. More on Windows Media Player support later.

Sample filename: myplaylist.pls
Sample URL: http://www.myserver/myplaylist.pls
Play List Contents:


numberofentries=9
File1=http://myBroadbandshoutcastserver:8080
Title1=My Station – www.mysite.com
Length1=-1
File2=http://myDialupshoutcastserver:8082
Title2=My Station – www.mysite.com
Length2=-1
Version=2

When the player loads this play list, it will first attempt to connect to the Broadband stream. If the Broadband stream is unavailable then the player will connect to the Dialup stream.

You can also put an intro track in the play list. This would be played when a listener first connects to your station (“You are listening to….My Station”).


numberofentries=3
File1=http://mysite.com/intro.mp3
Title1=My Station – www.mysite.com
Length1=-1
File2=http://myBroadbandshoutcastserver:8080
Title2=My Station – www.mysite.com
Length2=-1
File3=http://myDialupshoutcastserver:8082
Title3=My Station – www.mysite.com
Length3=-1
Version=2

.ASX (Windows Media Player)
.ASX files are a great way to get Windows Media Player to stream Windows Media streams, or SHOUTcast streams. Important: do not add the traditional /listen.pls to the end of your SHOUTcast URL. Windows Media Palyer doesn’t like this.

Sample filename: broadband.asx
Sample URL: http://www.myserver/broadband.asx
Play List Contents:

When the player loads this play list, it will first attempt to connect to the Broadband stream. If the Broadband stream is unavailable then the player will connect to the Dialup stream.

You’ll also notice you can give your radio show and the different streams a friendly name for Windows Media Player to display.

Windows Media Player & SHOUTcast:

Getting Windows Media player to stream SHOUTcast sources is easy. You simply follow the same format above, but put the URL’s to your SHOUTcast sources in the tags.

.RAM (Real/RealOne Player)
.RAM files are used to launch the Real player. Real player works very will with SHOUTcast streams. RAM files can be very minimalistic.

Sample filename: broadband.ram
Sample URL: http://www.myserver/broadband.asx
Play List Contents:

http://MyShoutcastServer:8080
http://MyShoutcastServer:8082

When the player loads this play list, it will first attempt to connect to the Broadband stream. If the Broadband stream is unavailable then the player will connect to the Dialup stream.]]>

Tamda bu konu hakkinda muhabbet gecmis lkd listedelerinde.
Alinti yapayim dursun lazim olur gunu gelince.
***

#!/bin/bash
# findstring.sh:
# Find a particular string in binaries in a specified directory.
# usage: ./findstring.sh dir str

for file in $( find $1 -type f | sort )
do
strings -f $file | grep “$2” | sed -e “s%$1%%”
done

***

find . -type f -print -exec grep mail '{}' \;

komutu icinde bulundugun dizin ve latinda tum dosylarda icinde
mail gecen satirlari yazar.

***

asagıdaki komut bulundugun klasordeki ve ek olarak xxx
klasorundeki butun php uzantili dosyalarin icerisinde mail kelimesi
gecen satirlari gosterecektir.

cat *.php xxx/*.php | grep mail

Other files you may want to have a look at will be in /var/adm & /var/log (depending on your server).

A good way to determine what is taking up the most space and what can be cleaned up is to first determine what directories are using the most.

For example, if you have a /var partition and want to calculate which directories are using the most space, do this:

# cd /var
# du -skx * : sort -n

It will show you each directory directly under /var and the amount of space it is using in kilobutes. You can then use that info to determine if it is indeed log files in /var/log. Or maybe your mail server has a lot of extra queue files that are not getting processed and they are taking up your disk space… stuff like that.

Another thing to look for is extraneous core files from crashed processes that you do not need for debugging purposes. Usually they’re not that big but for bigger apps (database, etc) they can get quite large.

You can do one of two commands to find core files:

* traditional find command – this is more resource intensive if you have a large amount of data, but is the “best” because it works on EVERY Unix server

# find / -name core -print

* locate, which should work on most Linux machines but may not tell you about recent core files:

# locate core