Writing a good, informative and catchy article is very essential for a blog or if it is to be published or submitted elsewhere. Here are some useful points which will help make the article interesting and helpful for the readers.

- To know the audience is very essential so it is imperative to identify what kind of readers are being targeted as they will be from different demographics and it would be important to communicate with them at their level.

- You may start an article with a teaser by applying the inverted pyramid style which will summarize the main idea of the article and will make the reader wonder on the ‘how’ and the ‘why’ aspects of the article.

- Go paragraph-wise and go for shorter paragraphs than the long ones as readers fell lazy when they face up with huge mass of text. Readers do get engaged to shorter paragraphs more but along with being short and to the point the article also has to interesting no matter if it is a little long then.

- It is a good practice to bold the selling points of the page. Bold the points which exactly states what is going to be accomplished from it. Use of bullet point lists is best and is also catchy.

- Talk about the advantages and not the features as it works better. Try being personal and tell them your story as that works for many types of readers. Having a genuine guarantee and backing up of your claims is a great way to gain the trust of the reader.

- Uses of simple and short sentences are always advisable and avoid difficult words for general readers especially if you are targeting an audience from various geographical locations.

- Improve your copy by doing the A/B split (two versions) test and check which works; as there is no other way to know for sure what the customer wants to hear/read.

- Using a bit of humor and engaging the readers with real life examples are good ways to keep them attached to the article.

- The headline or the title should be very well chosen. People read the longest articles and letters if they are attracted to the headline.

- Stick with all facts and figures on proof base only and avoid feathery or over ambitious claims. A reader should never feel a loss of reliability from the article by you being more promotional and less enlightening.

For submitting in free directories a webmaster should just keep in mind that the directories should be SEO friendly. The PR of the directories won’t be a point of concern as you can submit to directories which have no PR also because sooner or later even those directories will gain a decent PR.

If you are hunting around only for directories with high PR you will notice that most of them are paid ones so it won’t be of much use to you.
You may submit to a number of directories in a day say maybe 20, 50, 100 or also 200. The reason it won’t matter to submit to such an amount of directories is because they get crawled by the spiders in a certain number of days and not at once so it’s all fine.

Target different keywords in the title on a daily basis so that all your keywords get upward push in the search rankings which would be beneficial to your web site in an over all perspective.

This has been an ongoing issue with Tiscali BB users, Orange BB users and people who have BB and have Speedtouch modems and the new drivers.

The reason that the error appears is because the new drivers that you get are meant for Windows Vista and not Windows Xp or the other older Windows Operating Systems.

So to get that error resolved, try this, it will work for sure but do it carefully as you have to make changes in Windows Registry. Try it at your own risk and just follow the steps that are given here.

*Start–>Run–>msconfig.
*Click on “Start up” tab:
*In the start up processes look for ” dragdiag.exe “,Please see to it that you find “C:\program files\thomson” next to it.
*Uncheck that option.
*Click ‘apply’ and ‘ok’
*Click ‘close’
*Restart system.

Please let me know if that works as it has worked for all the people that I have tried it with.

**( not sure if it works for Win 98)

Guys!!

I have found some useful shortcut keys for Linux!
# / - root directory

# ./ - current directory

# ./command_name - run a command in the current directory when the current directory is not on the path

# ../ - parent directory

# ~ - home directory

# $ - typical prompt when logged in as ordinary user

# # - typical prompt when logged in as root or superuser

# ! - repeat specified command

# !! - repeat previous command

# ^^ - repeat previous command with substitution

# & - run a program in background mode

# [Tab][Tab] - prints a list of all available commands. This is just an example of autocomplete with no restriction on the first letter.

# x[Tab][Tab] - prints a list of all available completions for a command, where the beginning is “x”

# [Alt][Ctrl][F1] - switch to the first virtual text console

# [Alt][Ctrl][Fn] - switch to the nth virtual text console. Typically, there are six on a Linux PC system.

# [Alt][Ctrl][F7] - switch to the first GUI console, if there is one running. If the graphical console freezes, one can switch to a nongraphical console, kill the process that is giving problems, and switch back to the graphical console using this shortcut.

# [ArrowUp] - scroll through the command history (in bash)

# [Shift][PageUp] - scroll terminal output up. This also works at the login prompt, so you can scroll through your boot messages.

# [Shift][PageDown] - scroll terminal output down

# [Ctrl][Alt][ ] - switch to next X server resolution (if the server is set up for more than one resolution)

# [Ctrl][Alt][-] - change to previous X server resolution

# [Ctrl][Alt][BkSpc] - kill the current X server. Used when normal exit is not possible.

# [Ctrl][Alt][Del] - shut down the system and reboot

# [Ctrl]c - kill the current process

# [Ctrl]d - logout from the current terminal

# [Ctrl]s - stop transfer to current terminal

# [Ctrl]q - resume transfer to current terminal. This should be tried if the terminal stops responding.

# [Ctrl]z - send current process to the background

# reset - restore a terminal to its default settings

# [Leftmousebutton] - Hold down left mouse button and drag to highlight text. Releasing the button copies the region to the text buffer under X and (if gpm is installed) in console mode.

# [Middlemousebutton] - Copies text from the text buffer and inserts it at the cursor location. With a two-button mouse, click on both buttons simultaneously. It is necessary for three-button emulation to be enabled, either under gpm or in XF86Config.

Enjoy…

You can set up awstats just like Webalizer to access it outside of cPanel. It is so simple to set up and configure it so that you can access it outside cPanel.

Friends! Just follow the steps given below and you will be able to access Awstats outside of cPanel.

==========================================================

Step 1.

Download awstats from http://awstats.sourceforge.net

Step 2.

Uncompress awstats-6.6.tgz in user’s home folder

Step 3.

Copy the contents of the uncompressed cgi-bin folder to the user cgi-bin directory (this includes awstats.pl, awstats.model.conf, and the lang, lib and plugins sub-directories).
Path for cgi-bin dir of awstats is Awstats6.6/wwwroot/cgi-bin .

Step 4.

If necessary edit the first (top-most) line of awstats.pl file that is
#!/usr/bin/perl
Change it to the path where your Perl interpreter is already installed. Default value works for most of Unix OS, but it also might be
#!/usr/local/bin/perl

Step 5.

Move AWStats icon sub-directories and its content into a directory say paublic_html folder ,readable by your web server, for example /home/users/public_html/icons

Step 6.

Copy awstats.model.conf file into a new file named awstats.myvirtualhostname.conf. This new file must be stored in
/home/user/public_html/cgi-bin.

Step 7.

Edit this new config file with your own setup :
- Change LogFile value with full path of your web server log file
(The path is:
LogFile=”/usr/local/apache/domlogs/domain.com”).

- Check if LogFormat has the value “1″ (it means “NCSA apache combined/ELF/XLF log format”).

- Change DirIcons parameter to reflect relative path of icon directory.
(DirIcons=”/icons”)

- Edit SiteDomain parameter with the main domain name or the intranet web server name used to reach the web site to analyze (Example: www.mydomain.com).

IMPORTANT!
- Change DirData to use the same Statics file than Cpanel Awstats and do not loose any entry.
(DirData=”/home/user/tmp/awstats/”)

Step 8.

Access AwStats by the URL:

www.domain.com/cgi-bin/awstats.pl?config=domain.com

Cheers!!!!! You have configured Awstats to be viewable outside of cPanel!

We will need to optimize and tune MySQL to identify the queries that are causing the problems. How can we find out what queries are taking a long time to complete? How can we see what queries are slowing down the mysql server.

If we take the most expensive 10 queries and we optimize them properly (maybe running them more efficiently, or maybe they are just missing a simple index to perform properly), then we will immediately see the result on the overall mysql performance. Then we can iterate this process and optimize the new top 10 queries.

Activate the logging of mysql slow queries :

The first step is to make sure that the mysql server will log slow queries and to properly configure what we are considering as a slow query.

Firstly, check on the mysql server if we have slow query logging enabled ;

———————————————————————
# mysqladmin var |grep log_slow_queries

| log_slow_queries | OFF |
———————————————————————

If log_slow_queries is ON then we already have it enabled. This setting is disabled by default - meaning that if you don’t have log_slow_queries defined in the mysql server config this will be disabled.

The mysql variable long_query_time (default 1) defines what is considered as a slow query. In the default case, any query that takes more than 1 second will be considered a slow query.

In order to do to do this in your mysql server config file(/etc/my.cnf in case of RHEL/Centos)in the mysqld section we need to add:

———————————————————————
[mysqld]
long_query_time = 1
log-slow-queries = /var/log/mysql/mysql-slow.log
———————————————————————

This configuration will log all queries that take more than 1 sec in the file /var/log/mysql/mysql-slow.log.

Once you have done the proper configurations to enable mysql to log slow queries, you will have to reload the mysql service in order to activate the changes.