Perkiraan Kiblat MElalui Google Earth

you also can visit this sites to live watching…
http://espn.go.com/espn3/index/_/sport/soccer-futbol (ESPN)
http://www.cbc.ca/sports/?ref=cbcsports (CBC.CA)
http://futbol.univision.com/ (Univision)
http://news.bbc.co.uk/sport2/hi/football/world_cup_2010/matches/match_01/default.stm (BBC)

yum install awstats

Optional: (To see what countries are visiting your website)

# yum install perl-Geo-IP

# yum install GeoIP-data

Prepare the configuration file:

# cd /etc/awstats

# mv awstats.model.conf awstats.model.bak # Keep a backup of the original

# mv awstats.localhost.localdomain.conf awstats.example.com.conf # Change it to your domain

Edit the configuration file:

# vi /etc/awstats/awstats.example.com.conf

In line 51: change LogFile=”/var/log/httpd/access_log” to the location of the access_log file you want to gather statistics.

Ex: LogFile=”/var/log/httpd/example.com-access_log”

In line 153: change SiteDomain=”localhost.localdomain” to SiteDomain=”example.com”

In line 168: change HostAliases=”localhost 127.0.0.1″ to HostAliases=”www.example.com”

In line 203: change DirData=”/var/www/awstats” to your docroot.

Ex: DirData=”/var/www/htdocs/example.com/awstats”

If you installed the Geo-IP plugins you need to enable it:

In line 1305 change #LoadPlugin=”geoip GEOIP_STANDARD /pathto/GeoIP.dat” to LoadPlugin=”geoip GEOIP_STANDARD /var/lib/GeoIP/GeoIP.dat”

Move the awstats directory to your docroot:
//uncessary, check http://shebangme.blogspot.com/2010/06/install-awstats-on-centos-5.html

# mv /var/www/awstats /var/www/htdocs/example.com

Change the permissions to the awstats directory:

# chown -R localuser:apache /var/www/htdocs/example.com/awstats

Edit the awstats.conf to setup the aliases and restrictions:

# vi /etc/httpd/conf.d/awstats.conf

Change the Alias, ScriptAlias and Directory location to where the awstats is in your docroot.

ex:

Alias /awstats/icon/ /var/www/htdocs/example.com/awstats/icon/

ScriptAlias /awstats/ /var/www/htdocs/example.com/awstats/

<Directory /var/www/htdocs/example.com/awstats/>

DirectoryIndex awstats.pl

Options ExecCGI

order deny,allow

deny from all

allow from 192.168.1. 66.80.199.111 # Allow access to awstate from the 192.168.1.0/24 subnet only

</Directory>

#Alias /css/ /var/www/awstats/css/

#Alias /js/ /var/www/awstats/js/

Reload Apache:

# service httpd reload

In case you don’t have the Options FollowSymLinks in httpd.conf, awstats will not work so you need to add it in the /etc/httpd/conf.d/awstats.conf above.

……..

Options ExecCGI

Options FollowSymLinks

……..

Update your statistics:

# cd /var/www/htdocs/example.com/awstats

# perl awstats.pl -config=example.com -update

If you see something like:

Create/Update database for config “/etc/awstats/awstats.example.com.conf” by AWStats version 6.9 (build 1.925)

From data in log file “/var/log/httpd/example.com-access_log”…

Phase 1 : First bypass old records, searching new record…

Direct access after last parsed record (after line 4)

Jumped lines in file: 4

Found 4 already parsed records.

Parsed lines in file: 13

Found 0 dropped records,

Found 0 corrupted records,

Found 0 old records,

Found 13 new qualified records.

Then everything went fine.

If you changed your logs from common to combined it might throw some errors when you update awstats so you need to clean the log file to have only the combined logs:

# cat /dev/null > /var/log/httpd/example.com-access_log

run the update again:

# perl awstats.pl -config=example.com -update

Update for config “/etc/awstats/awstats.example.com.conf”

With data in log file “”

Phase 1:

Seaching new records from beginning of log file

Phase 2:

Found 2389 new qualified records.

Navigate to http://example.com/awstats/awstats.pl

If the update time on the upper left hand corner is the same as the time you run the awstats.pl update and you can see the statistics, then everything works fine.

Setup the cron job (it will run hourly and redirect the output to /dev/null so it’s not going to send an email to root every hour) :

cd /etc/cron.hourly

echo “perl /var/www/htdocs/example.com/awstats/awstats.pl -config=example.com -update > /dev/null 2>&1″ > awstats.sh

chmod 755 awstats.sh

test the script:

./awstats.sh

Refresh your browser and if the update time changes then you are all set.

Enjoy the statistics on your website!

If you are using Gnome, click on “System => Administration => Network”.

From the Network Configuration window, select your NIC from de “Devices” tab and click on the “Edit” button.

Select “Statically set IP addresses” and enter the IP address, subnet mask and default gateway. Click OK when done.

Now back to the Network Configuration window, select the DNS tab. Enter your hostname and your DNS servers.

Click on “File => Save” when you’re done.

Setting Up A Static IP Address Using The Command Line

Log on as root, change directory to /etc/sysconfig/networking/devices and list all available devices.

# cd /etc/sysconfig/networking/devices
# ls

Find the configuration file corresponding to the NIC for which you want to set a static IP and edit it.

# vi ifcfg-eth0

I prefer using “joe” as a text editor rather than “vi”. You can install “joe” by issuing “yum install joe”. To invoke joe’s help menu, type “CTRL+K, H” from within the application.

Now set the parameters below according to your settings (those in bold characters only):

DEVICE=eth0
BOOTPROTO=none
HWADDR=00:0C:29:DE:94:8B
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
NETMASK=255.255.255.0
IPADDR=192.168.0.100
GATEWAY=192.168.0.1

Save the configuration file and exit the text editor.

To set the nameservers, change directory to /etc and edit resolv.conf.

# cd /etc
# vi resolv.conf

The file format should be like this:

search your-dns-search-path
nameserver dns1-ip-address
nameserver dns2-ip-address
nameserver dns3-ip-address

Now save the configuration file and exit the text editor. To apply changes, we need to bring the network interface down and back up.

# ifdown eth0
# ifup eth0

If you intend to do that remotely, reboot the server instead as you would be disconnected from your server after issuing the “ifdown” command.

Unlocking the Blackberry.

First of all, this is not a guide on how to remove carrier information from a Blackberry. If you’re unable to use a different SIM card than the one that was originally supplied with your device, look elsewhere. However if, like many others you have a Blackberry that is locked by a BES, meaning you’re unable to change certain settings, or install Third Party Applications then read on. Essentially, the problem is that your Blackberry has at some point been connected to a BES (Blackberry Enterprise Server), and this BES has placed a restrictive Security Policy (or IT Policy) on your device. A quick check to see if this is the case can be done by going to Options/Security on your Device. If you see any references to IT Policy whatsoever, then you have a potentially restrictive IT Policy that can be removed.

The Disclaimer/Intended Use.

This guide is intended for use by people that own their own Blackberry, and for whatever reason, have inherited a company’s IT Policy on their Device. Really, there are two scenarios where this guide is useful.

You, like me, bought a Blackberry on EBay and are unable to make changes to the settings or install Third Party Applications. You have a Blackberry that was previously connected to a company’s BES and, for whatever reason; you no longer intend to make connections to that BES. If you’re still connected to a Company BES, and simply want to install the latest and greatest Third Party Application I wouldn’t recommend this approach. Go talk to your administrators and ask them to grant you the appropriate rights. There are two problems in using this guide to bypass your Company’s Security Policy. Firstly, whenever you reconnect to the Company Server, your security settings will revert back to how they were. Secondly, and (perhaps) more importantly, you run the risk of getting fired.

Procedure

Method One

Method 1: IT Policy Removal (Preferred)

If you have any 8xxx or 9xxx device the best method for removing IT policy is to update it to OS 4.3 or higher (if possible) and you can use JL_Cmder’s “resettofactory” command to remove ALL IT policy, Firewall restrictions and Application Permission settings. After you’ve upgraded to OS 4.3 or higher, simply backup the device using Desktop Manager, close Desktop Manager, then run JL_Cmder and execute the “resettofactory” command. The device will do a security wipe of the device; (meaning wipe your data but leave the OS, DO NOT use the “Wipe” command in JL_Cmder) then reboot leaving the OS, 3rd party apps but no data AND, best of all, NO IT policy whatsoever. When you’re done, simply restore your backup and you’re good to go with no policy or locked firewall. You can downgrade back to the old OS if you desire, too.

Download JL_Cmder from this link: http://www.blackberryforums.com/general-blackberry-discussion/18789-jl_cmder.html

If your 7xxx or 8xxx device is running OS 4.2 or lower (look in Options >About) and you can’t upgrade it to OS 4.3 or higher you will NOT be able to use method 1 above and you will need to use method #2 below:

Method Two

Step 1

Ensure the Blackberry Desktop Manager is installed using Blackberry Internet Service, and not Blackberry Enterprise Server. If you are unsure, it would probably be a good idea to uninstall the Desktop Manager and start again.

If you don’t have the CD that came with your Blackberry, the Software can be downloaded here. BlackBerry Software Site

Step 2

Download the file policy.bin Download Here. and save it in your Blackberry installation directory (C:\Program Files\Research In Motion\BlackBerry).

Step 3

Wipe your Blackberry, creating a backup if necessary. Select Options/Security/Wipe (Newer 4.2 OS Devices Goto Options/Security Options/General Settings/Wipe) on the Device.

If this option is unavailable, you may have to install the latest software on your Blackberry. You need to Download and install the latest Desktop Manger Software, then the latest Handheld Software. Connect your device, open the Desktop Manager, select Application Loader, and follow the prompts.

Step 4

Close the Desktop Manager if it is open.

Step 5

From the Windows Start Menu select Run…, and at the prompt type regedit. In the tree on the left hand side, navigate to:

HKEY_Current_Users\Software\Research In Motion\BlackBerry\PolicyManager

Right-Click the Policy Manager Folder and select New/String Value. Name the value Path. Now, Double-Click the Path Subkey and set Value Data to:

C:\Program Files\Research In Motion\BlackBerry\policy.bin

Step 6

Open the Desktop Manager.

Step 7

Connect the Device.

Verification

Once complete, the Options/Security screen on your Blackberry should not contain references to an IT Policy, you should now be able to change all settings (including password prompts), and install Third Party Applications.

Jakarta – Gara-gara letusan gunung api di Islandia, MotoGP Jepang yang sedianya digelar akhir pekan ini ditunda. Sirkuit Motegi baru akan menggelar balap MotoGP pada 3 Oktober mendatang.

Seperti diberitakan sebelumnya, akibat letusan Gunung Eyjafjallajokull di Eropa, banyak penerbangan dari dan ke ‘Benua Biru’ tersebut terpaksa dibatalkan. Kejadian tersebut berimbas pada seri kedua MotoGP musim 2010 yang sebelumnya direncanakan digelar sepanjang akhir pekan ini di Jepang.

Seperti telah diprediksi, Motegi harus menunggu lama untuk akhirnya bisa menggelar kompetisi antara Valentino Rossi, Jorge Lorenzo, Casey Stoner dan belasan pembalap lainnya. Jepang yang tadinya menjadi seri kedua musim ini harus menerima dipindah menjadi seri ke-14, dengan race yang akan dilangsungkan pada 3 Oktober 2010.

“Carmelo Ezpeleta, dengan mendapat persetujuan dari Grand Prix Promoter, Mobilityland Corporation, memutuskan menunda GP Jepang yang direncanakan digelar 25 April 2010. The Grand Prix Permanent Bureau mengajukan usulan pada FIM untuk menjadwalkan ulang GP Jepang pada 3 Oktober 2010,” demikian pernyataan resmi yang dirilis Dorna dan MotoGP.

Kondisi ini membuat GP Spanyol di Sirkuit Jerez pada 2 Mei mendatang menjadi seri kedua di musim ini. Namun kekhawatiran kalau balapan tersebut juga bakal tertunda masih ada lantaran larangan penerbangan di Eropa masih berlaku hingga kini.
( din / roz )

Tetap update informasi di manapun dengan http://m.detik.com dari browser ponsel anda! 

Calendar MotoGP Season 2010 | Schedule Circuits MotoGP Season 2010. Hi MotoGP fans around the world. MotoGP season 2009 is over now it’s time to begin 2010 season. Is Rossi will become world champion again? What actually Lorenzo is going to beat “The Doctor”. From the busy guessing who won this 2010 season, following a complete list of MotoGP season 2010. And don’t go any where we will back to you for the streaming live MotoGp 2010 via ustream tv, trans7, justin tv, iphone, freedocast, sopcast, atdhe in hotfreez.com :

2010 MotoGP Calender
11 Apr. 2010 Qatar, Losail
25 Apr. 2010 Japan, Motegi –> postponed  3 Oct. 2010
02 May 2010 Spain, Jerez
23 May 2010 France, Le Mans
06 Jun. 2010 Italy, Mugello
20 Jun. 2010 Great Britain, Silverstone
26 Jun. 2010 Netherlands, TT Circuit
04 Jul. 2010 Catalonia, Barcelona
18 Jul. 2010 Germany, Sachsenring
25 Jul. 2010 United States, Laguna Seca
15 Aug. 2010 Czech Republic, Brno
29 Aug. 2010 United States, Indianapolis
05 Sep. 2010 San Marino, Misano
19 Sep. 2010 Hungary, Balatonring
10 Oct. 2010 Malaysia, Sepang
17 Oct. 2010 Australia, Phillip Island
31 Oct. 2010 Portugal, Estoril
07 Nov. 2010 Valencia, Valencia

Incoming search terms for the article:motogp tv schedule, motogp television schedule, motogp trans7, trans7 motogp 2010, trans 7 moto gp, motogp 2010 tv coverage, motogp trans 7, moto gp television coverage, trans7 motogp, motogp television coverage, motogp 2010 tv schedule, moto gp trans 7, moto gp tv schedule, trans 7 motogp 2010, motogp tv coverage 2010, moto gp freedocast, moto gp of japan 2010 tv coverage, motogp 2010 schedule trans7, mOTOgp TV SCHEDULE 2010, schedule motogp trans7

Install Apache

Add ports to firewall

• You may need to add a firewall rule to allow port 80
• vi /etc/sysconfig/iptables – add the following lines, if they don’t already exist
• -A RH-Firewall-1-INPUT -m state –state NEW -m tcp -p tcp –dport 80 -j ACCEPT

Install SARG

• cd /usr/src – optional, this is just where I like to keep the source archives
• wget http://dag.wieers.com/rpm/packages/sarg/sarg-2.2.1-1.el4.rf.i386.rpm – download the SARG rpm to your /usr/src folder
• yum install gd gd-devel
• rpm -i /usr/src/sarg-2.2.1-1.el4.rf.i386.rpm – install SARG using the Red Hat Package manager
• vi /etc/httpd/conf.d/sarg.conf

• add an additional Allow from line for each computer you want to be able to see the reports, or comment out the Deny from all, and Allow from lines to give access to all.

Configure DansGuardian and SARG to work with each other

• vi /etc/dansguardian/dansguardian.conf

• change the setting logfileformat to equal 3 – sets DansGuardian to log in squid log file format
• :wq – save the changes to the file and quit

• vi /etc/sarg/sarg.conf

• change the setting access_log to point to your dansguardian logs. Under default settings, it should be /var/log/dansguardian/access.log
• change any other settings you want to change
• :wq – save the changes to the file and quit

• Check the sarg scripts in the cron folders. You will need to make some changes to point to the DansGuardian log files

• vi /etc/cron.daily/sarg – really no changes here
• vi /etc/cron.weekly/sarg – change the log file paths to the path of your DansGuardian log files
• vi /etc/cron.monthly/sarg – change the log file paths to the path of your DansGuardian log files

• /usr/bin/sarg – run sarg to create a ONE-SHOT report

Start Apache

• /etc/init.d/httpd start – Start Apache

Test Configuration

• browse to your DansGuardian machine using your favorite internet browser. You will have to add /sarg to the end of the url. (ex. http://192.168.0.1/sarg Check to make sure the ONE-SHOT report was generated.

• wait for the cron jobs to run and generate the rest of the reports

Done