By Shamly, on December 31st, 2010
The location of the php.ini file depends on the Linux distribution (windows distribution does not have a major impact) you are using (RHEL, Ubuntu, etc), PHP version and how it has been installed with the Apache web server. Normally the php.ini file are stored in one of the following (but not limited to) locations in a linux machine:
Click Here to Read the Full Post →
By Shamly, on December 12th, 2010
I always run linux applications manually using the terminal during the development stage. This has helped me immensely as I could see all the messages that were printed on to the linux console. I also had the habit of forgetting to start the Java program once the linux machine reboots. Well how many of you have had that experience? Ohh yes, I forgot to mention that I will be using a compiled java program as an example executable file for this tutorial.
Though this is acceptable for a system that is under development, it is not suitable to run an executable program using a terminal in production environment. So I would go about setting up a cron job to check if the process is running and start it up if it is not, using a shell script. This tutorial will give you an understanding of how to check for a running processes and start the process if not running using a shell script in linux.
Click Here to Read the Full Post →
By Shamly, on December 6th, 2010
Introduction
I have been using PHPMailer to send emails for some time now. PHPMailer is a fully featured email transfer class for PHP and its popularity has grown rapidly over the years. Recently I had to send e-mail messages using the GMail SMTP server for one of my clients.
Up to now I had only sent email messages using SMTP servers provided by the hosting company. The difference here is that I had to use SSL encryption to send emails. Using hosting company SMTP server has its drawbacks as there is a chance that your website IP address is already on a blacklist simply because someone else had abused the service before you.
Click Here to Read the Full Post →
By Shamly, on August 12th, 2010
WordPress has finally decided to move on to supporting PHP version 5 and dropping support for PHP version 4 since PHP 5 adds many new features and design changes that make developing robust, secure, feature-rich software faster and easier. This decision is in-line with many open-source projects such as Joomla and Drupal, who have already decided to move to PHP 5. Not only will WordPress drop support for PHP 4, but will also discontinue support for MySQL 4 as well.
Our approach with WordPress has always been to make it run on common server configurations. We want users to have flexibility when choosing a host for their precious content. Because of this strategy, WordPress runs pretty much anywhere. Web hosting platforms, however, change over time, and we occasionally are able to reevaluate some of the requirements for running WordPress. Now is one of those times. You probably guessed it from the title — we’re finally ready to announce the end of support for PHP 4 and MySQL 4!
In less exciting news, we are also going to be dropping support for MySQL 4 after WordPress 3.1. Fewer than 6 percent of WordPress users are running MySQL 4. The new required MySQL version for WordPress 3.2 will be 5.0.15.
Click Here to Read the Full Post →
|
|
Recent Comments