$ mail -s “Subject: Test email from linux server” info@test.com

Press the “Return” key

Enter the body part of the email

Press ctrl + D

Enter a CC email if you would like (e.g. info2@test.com)

Press ctrl + D again

Then check the mail box to see if the mail has arrived.

Method 2:

$ echo “Enter the body part of the email” | mail -s “Subject: Test email from linux server” info@test.com -c info2@test.com

For example,

$ dig -x 217.83.122.34

;; ANSWER SECTION:

34.122.83.217.in-addr.arpa. 66372 IN PTR mail.example.com.

$ dig mail.example.com

;; ANSWER SECTION:

mail.example.com. 900 IN A 217.83.122.34

Check the IP address that is getting resolved matches the name that is getting returned back.

$ php -version

Check Linux Version

$ cat /etc/*-release (or redhat-release)

Create a repo file with the content given below. As you can note, we are looking for package upgrade related to php only.

$ vi /etc/yum.repos.d/CentOS-phpupgrade.repo

# CentOS5-Upgrade:
# This repository is a proving grounds for packages on their way to CentOSPlus and CentOS Extras.
# They may or may not replace core CentOS packages, and are not guaranteed to function properly.
# These packages build and install, but are waiting for feedback from testers as to
# functionality and stability. Packages in this repository will come and go during the
# development period, so it should not be left enabled or used on production systems without due
# consideration.
[cent5-upgrade]
name=CentOS5 Upgrade
baseurl=http://dev.centos.org/centos/$releasever/testing/$basearch/
enabled=1
gpgcheck=1
gpgkey=http://dev.centos.org/centos/RPM-GPG-KEY-CentOS-testing
includepkgs=php*

Update the repository

$ yum update

Restart Apache server

$ service http restart

Check the PHP version that is installed

$ php -version

Check the package repository

$ rpm -qa | grep php

Maintenance check

All Web sites should be thoroughly tested using a site maintenance tool in order to catch errors in operation before customers are brought to the site. HTML errors can hinder a search engine spider’s ability to index a site, it can also keep a search engine from reading a page or cause it to be viewed in a manner different from how it was intended. NetMechanic’s HTML Toolbox or another site maintenance tool, must be used by the Webmaster, to avoid potential visitor disasters due to site errors.

Submission service

Selecting a search engine submission service requires careful thought and important decisions. Using an auto submission service is a good place to begin. Most search engines like Alta Vista, HotBot and InfoSeek automatically spider a site, index it and hopefully add it to their search database without any human involvement. Some engines, like Yahoo, are done completely with human review and for many reasons are best submitted individually.

Understanding the waiting periods

A variety of waiting periods must be endured with each search engine before there is even a hope of being listed. There is 4-6 weeks of wait period in normal stance.

Promotion exercise

To improve site rankings and increase understanding of the listing process, there are many tasks that can be done on a regular or semi-regular basis. Optimizing rankings within the search engines is also to help ensure that a site attracts the right traffic.

Crunching and examining log files

Data contained in log files is an excellent resource for identifying which engines are sending the majority of traffic to a site. It can also show which key words or gateway pages are generating the strongest traffic and what are those visitors doing when they enter the site.

Searching the Search Engines

Conduct a search of the search engines to analyze where the highest rankings of the site have materialized and what keywords are generating the best rankings.
Different search engines use different rules to rank pages. Individual gateway pages should be created based on the knowledge and interpretation of what each search engine is using to determine top rankings. Several pages can be tested out on one or more engines and the pages that have the most success can be kept, while the unsuccessful pages can be dumped or revised to achieve a higher ranking.

Periodic update on how search engines work

Each search engine uses different rules to determine how well a Web page matches a particular query. As a result, building a single page that gets a good score in all the major engines is just about impossible. Learning how each engine ranks pages is also hard, since the engines often keep this information as a closely guarded secret. However, with a little patience, some experimentation and reverse engineering, the way that many of the search engines work can be discovered.

Resubmitting the site

For engines that reject a site or don’t list it high enough, it is strongly recommended that more information is learned about the engine’s criteria before resubmitting. This information should then be incorporated into gateway pages or key word revisions in order to have greater success with subsequent submissions.
Fine tune the page (or pages) make adjustments to TITLE tags and META tags, then after resubmitting the site, track the results to further learn about the engine’s criteria and which adjustments made an impact on the rankings.

Checking log files for traffic being directed to erroneous pages on the site

There may be external links pointing to pages that don’t exist in your site or pages that have been removed from your site. Don’t dump these pages or remove them from the search engine as most people will do when they redesign their site. Any page with a high ranking is of value. If a page is bringing traffic to a site, leave that page on the search engine, don’t change it but rather redirect the traffic to valid pages in the site.

To see if SELinux is set, type

$ sestatus

To list all port, try the semanage command

$ semanage port -l

To check for a specific port that is opened

$ semanage port -l | grep 8085

To allow access to a specific port

$ semanage port -a -t http_port_t -p tcp 8085

Following command should help you set/change MySQL password

$ mysql -u root -p

mysql> use mysql;
mysql> show tables;
mysql> desc user;
mysql> update user set password=PASSWORD(‘mypassword’) where User=’root’;
mysql> flush privileges;
mysql> \q

Now you need to enter the new password for the user ‘root’ to gain access to mysql.

Point to note:

Prior to MySQL 4.1 PASSWORD function returns 16 byte string and in later versions it returns 41 byte string. In later versions, passwords begin with “*”. When users migrate databases from one version to other there are chances for the application to break if this factor is not considered. In later versions, if users want to still use the old form of password hashing there is a function “OLD_PASSWORD” available to them.

Fine tune the TITLE tag to increase traffic to the site

Improving the TITLE tag is one technique that applies to just about all the search engines. The appearance of key words within the page title is one of the biggest factors determining a Web site’s score in many engines. Changing title of the web pages to include some site keywords which works well with each of the pages can greatly increase the chance of the page getting noticed by the search engines and can increase the page rank of the site as well.

Keyword selection

Choosing the keywords which pertain to the company’s product / services is a key factor of SEO. Searching the keywords through Word Tracker tool for the domain specific words and analyzing the keyword trend of the competitors would be a great start in keyword organization on the pages.

The larger the number of key words used, the more the relevance of any one key word getting diluted. One way to get around this is to create gateway pages and keeping the pages one to two page deep.

Creating gateway pages that are specific to focus the purpose of the site

Gateway pages are designed with keywords for specific submission to search engine(s). They should be tuned with a specific set of key words, boosting the chance that these key words will be given a heavy weight. To do this, several copies of a page should be made, one for each set of key words. These pages will be used as entry points only, to help people find the site, therefore, they don’t need to fit within the normal structure of the site. This provides the page developer with greater flexibility in establishing key words and tags that will encourage a stronger ranking with the search engines. Each gateway page then can be submitted separately to the search engines.

Ensuring that a proper site technology being used

Often the latest technology being built into a site can confuse the search engine spiders. Frames, CGI scripts, image maps and dynamically generated pages are all recently created technology that many spiders don’t know how to read. With frames for instance, the syntax of the FRAMESET tag fundamentally changes the structure of an HTML document. This can cause problems for search engines and browsers that don’t understand the tag. Some browsers can’t find the body of the page and viewing a page through these browsers can create a blank page.

FRAMES Vs. Site Content

Ensure that NOFRAMES section is applied to the page if FRAMES are widely used across. Have meaningful content in the frame section with links to appropriate non-frame section of the pages to help the crawler. This tag will not affect the way a page looks but it will help a page get listed with the major search engines.

Essence of a Site map

Site map is a back door entrance for the crawler to cycle its search across various cross-sections in the site.

Blogging

Maintain a blog pertaining to the site. Crawlers like blogs as its content change frequently. Link the blog feed to sections within the site to make the content relevant to the targeted keywords.

Participation in communities

Active participation in industry related or industry specific forums, blogs and develop a strategy to link back to vital pages/sections within your site.

$/etc/init.d/mysqld start
$/etc/init.d/mysqld restart
$/etc/init.d/mysqld stop

In windows, mysql runs as a service.
C:> net stop mysql
C:> net start mysql

In such scenarios when a database call is made after the application migration happens, users often run into errors which can send them in circles between the migration servers.

Solution to this problem is to add a single line of text under my.cnf (MySQL configuration file) under [mysqld]