shukko·0 yorum

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.]]>

shukko·0 yorum

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

shukko·0 yorum

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

shukko·0 yorum

find . -name *.log : xargs rm
was the way I was going to go, but then it said
-bash: /usr/bin/find: Argument list too long
rm: too few arguments

I also tried
mv *.log /dev/null
which generated a similar error.

Silly me, I thought it was rm that was complaining when it was in fact bash!!
Obviously the string that bash generates by expanding wildcard ‘*.log’ is too long for it to pass to any command.
Just like Juri said it is a shell limitation.I have looked, but havent seen any options or shell variables that would let me up this limit.

So I escaped the wildcard and let ‘find’ handle it by
find . -name ‘*.log’ : xargs rm
which did it.

shukko·0 yorum

Acele ile yapmak zorundaydim.
Cikmak zorundayim cunku 🙂
Ama blog mantigina uygun olarak ilk defa bloguma bisiler yazmak geldi bugun icimden. Yazayim..