<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Kurinchi Blogger Scribbles ... &#187; php.ini</title>
	<atom:link href="http://kurinchilamp.kurinchilion.com/tag/phpini/feed" rel="self" type="application/rss+xml" />
	<link>http://kurinchilamp.kurinchilion.com</link>
	<description>On Open Source Technologies</description>
	<lastBuildDate>Mon, 02 Jan 2012 06:14:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>PHP: ‘Fatal error: Allowed memory size of 8388608 bytes exhausted’</title>
		<link>http://kurinchilamp.kurinchilion.com/2010/08/php-%e2%80%98fatal-error-allowed-memory-size-of-8388608-bytes-exhausted%e2%80%99.html</link>
		<comments>http://kurinchilamp.kurinchilion.com/2010/08/php-%e2%80%98fatal-error-allowed-memory-size-of-8388608-bytes-exhausted%e2%80%99.html#comments</comments>
		<pubDate>Tue, 03 Aug 2010 03:24:46 +0000</pubDate>
		<dc:creator>kurinchilamp</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[allowed memory exhaust]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[fatal error]]></category>
		<category><![CDATA[memory limit]]></category>
		<category><![CDATA[php.ini]]></category>

		<guid isPermaLink="false">http://kurinchilamp.kurinchilion.com/?p=869</guid>
		<description><![CDATA[Reason why you see this message is due to PHP memory leakage. PHP is trying to load a large image or file into memory and is not finding enough space for it to load. If you think, that you will need the necessary feature to upload large files then there are two ways by which [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Reason </strong>why you see this message is due to PHP memory leakage. PHP is trying to load a large image or file into memory and is not finding enough space for it to load.</p>
<p>If you think, that you will need the necessary feature to upload large files then there are two ways by which you can enable this feature.</p>
<p><em>i) Edit the physical file and have the line</em><br />
<strong>ini_set(&#8220;memory_limit&#8221;,&#8221;20M&#8221;);</strong></p>
<p><em>ii) Edit php.ini </em>and add the following line. You need to restart the apache/IIS server once php.ini file is modified.<br />
<strong>memory_limit=32M</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://kurinchilamp.kurinchilion.com/2010/08/php-%e2%80%98fatal-error-allowed-memory-size-of-8388608-bytes-exhausted%e2%80%99.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PHP: What is PEAR?</title>
		<link>http://kurinchilamp.kurinchilion.com/2009/10/php-what-is-pear.html</link>
		<comments>http://kurinchilamp.kurinchilion.com/2009/10/php-what-is-pear.html#comments</comments>
		<pubDate>Fri, 09 Oct 2009 17:23:00 +0000</pubDate>
		<dc:creator>kurinchilamp</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[PEAR]]></category>
		<category><![CDATA[pear settings]]></category>
		<category><![CDATA[php.ini]]></category>

		<guid isPermaLink="false">http://kurinchilamp.kurinchilion.com/?p=694</guid>
		<description><![CDATA[PEAR stands for PHP Extension and Application Repository. To learn more about the PEAR library click here If you are beginner, the following link will help you tread with the library usage PEAR Manual Installation instructions clearly walks through the steps for PEAR configuration. There may be cases where you may want to use PEAR [...]]]></description>
			<content:encoded><![CDATA[<p><strong>PEAR </strong>stands for <strong>PHP Extension and Application Repository</strong>.</p>
<p>To learn more about the PEAR library <a href="http://pear.php.net/manual/en/about.pear.php" target="_new">click here </a></p>
<p>If you are beginner, the following link will help you tread with the library usage <a href="http://pear.php.net/manual/en/installation.php" target="_new">PEAR Manual</a></p>
<p>Installation instructions clearly walks through the steps for PEAR configuration. There may be cases where you may want to use PEAR libraries for specific projects only in which case you can install PEAR library for that specific purpose. To use it in projects, PEAR path should be set in <strong>php.ini </strong>settings or should be included in the project configuration&#8217;s physical path.</p>
]]></content:encoded>
			<wfw:commentRss>http://kurinchilamp.kurinchilion.com/2009/10/php-what-is-pear.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PHP removing deprecated related errors from display</title>
		<link>http://kurinchilamp.kurinchilion.com/2009/08/php-removing-deprecated-related-errors-from-display.html</link>
		<comments>http://kurinchilamp.kurinchilion.com/2009/08/php-removing-deprecated-related-errors-from-display.html#comments</comments>
		<pubDate>Tue, 01 Sep 2009 01:29:01 +0000</pubDate>
		<dc:creator>kurinchilamp</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[deprecated error]]></category>
		<category><![CDATA[E_DEPRECATED]]></category>
		<category><![CDATA[nusoap]]></category>
		<category><![CDATA[PHP error]]></category>
		<category><![CDATA[php.ini]]></category>

		<guid isPermaLink="false">http://kurinchilamp.kurinchilion.com/?p=655</guid>
		<description><![CDATA[To remove deprecated warning message displays when executing PHP programs, open php.ini file and ADD to it error_reporting = E_ALL &#038; ~E_DEPRECATED This is the setting for the production environment where you would not like to display the deprecated function related errors. Sample error message Assigning the return value of new by reference is deprecated [...]]]></description>
			<content:encoded><![CDATA[<p>To remove <em>deprecated </em>warning message displays when executing PHP programs, open <strong>php.ini </strong>file and ADD to it</p>
<p><strong>error_reporting = E_ALL &#038; ~E_DEPRECATED</strong></p>
<p>This is the setting for the production environment where you would not like to display the deprecated function related errors.</p>
<p><em>Sample error message</em><br />
Assigning the return value of new by reference is deprecated in <strong>nusoap.php</strong> on line 7381</p>
]]></content:encoded>
			<wfw:commentRss>http://kurinchilamp.kurinchilion.com/2009/08/php-removing-deprecated-related-errors-from-display.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to turn off register_globals via php.ini?</title>
		<link>http://kurinchilamp.kurinchilion.com/2009/07/how-to-turn-off-register_globals-via-php-ini.html</link>
		<comments>http://kurinchilamp.kurinchilion.com/2009/07/how-to-turn-off-register_globals-via-php-ini.html#comments</comments>
		<pubDate>Thu, 16 Jul 2009 13:54:06 +0000</pubDate>
		<dc:creator>kurinchilamp</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[.htaccess]]></category>
		<category><![CDATA[PHP security]]></category>
		<category><![CDATA[php.ini]]></category>
		<category><![CDATA[register globals]]></category>

		<guid isPermaLink="false">http://kurinchilamp.kurinchilion.com/?p=503</guid>
		<description><![CDATA[It is always secured to turn OFF register_globals in PHP applications. Earlier, we have seen how to turn OFF register_globals setting via .htaccess file and in this blog we will use php.ini instead. Using a text editor create a file called php.ini. This will be our first step. Next, we need to add the following [...]]]></description>
			<content:encoded><![CDATA[<p>It is always secured to turn OFF register_globals in PHP applications. Earlier, we have seen how to turn OFF register_globals setting via .htaccess file and in this blog we will use php.ini instead.</p>
<p>Using a text editor create a file called php.ini. This will be our first step.</p>
<p>Next, we need to add the following line of code in php.ini<br />
<strong>register_globals = off</strong></p>
<p>Upload php.ini file to the root folder where your application resides.</p>
]]></content:encoded>
			<wfw:commentRss>http://kurinchilamp.kurinchilion.com/2009/07/how-to-turn-off-register_globals-via-php-ini.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PHP: Fatal error: Maximum execution time of 30 seconds exceeded</title>
		<link>http://kurinchilamp.kurinchilion.com/2009/05/php-fatal-error-maximum-execution-time-of-30-seconds-exceeded.html</link>
		<comments>http://kurinchilamp.kurinchilion.com/2009/05/php-fatal-error-maximum-execution-time-of-30-seconds-exceeded.html#comments</comments>
		<pubDate>Fri, 29 May 2009 01:58:12 +0000</pubDate>
		<dc:creator>kurinchilamp</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[PHP error]]></category>
		<category><![CDATA[php.ini]]></category>
		<category><![CDATA[set_time_limit]]></category>

		<guid isPermaLink="false">http://kurinchilamp.kurinchilion.com/?p=376</guid>
		<description><![CDATA[This error happens when the execution time of the PHP script exceeds the time limit for program execution in Php.ini file. By default the timer is set to 30 seconds in php.ini and you can track the time limit by tracing for &#8216;max_execution_time&#8217; directive in php.ini. A quick way to find the execution time set [...]]]></description>
			<content:encoded><![CDATA[<p>This error happens when the execution time of the PHP script exceeds the time limit for program execution in Php.ini file. </p>
<p>By default the timer is set to <strong>30 seconds</strong> in <strong>php.ini</strong> and you can track the time limit by tracing for &#8216;max_execution_time&#8217; directive in php.ini. </p>
<p>A quick way to find the execution time set for PHP is to check the <strong>phpinfo()</strong> function. </p>
<p><strong>Solution</strong>:<br />
You can set the time limit by issuing &#8220;<strong>set_time_limit(60);</strong>&#8221; statement to increase the time limit.</p>
<p>A better way would be trace where the bottlenecks are in the program to identify what causes the time lag. Possible causes may be </p>
<p>* Poorly structured queries<br />
* Never ending iterations<br />
* Read lock on files when they are opened by multiple sources etc.</p>
]]></content:encoded>
			<wfw:commentRss>http://kurinchilamp.kurinchilion.com/2009/05/php-fatal-error-maximum-execution-time-of-30-seconds-exceeded.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

