<?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>bernhard.hensler.net &#187; php</title>
	<atom:link href="http://bernhard.hensler.net/blog/tag/php/feed/" rel="self" type="application/rss+xml" />
	<link>http://bernhard.hensler.net/blog</link>
	<description></description>
	<lastBuildDate>Mon, 28 Jun 2010 13:52:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>steps to visualize HTTP server logging &#8211; part I</title>
		<link>http://bernhard.hensler.net/blog/steps-to-visualize-http-server-logging-part-i/</link>
		<comments>http://bernhard.hensler.net/blog/steps-to-visualize-http-server-logging-part-i/#comments</comments>
		<pubDate>Thu, 27 Aug 2009 11:23:20 +0000</pubDate>
		<dc:creator>bernhard</dc:creator>
				<category><![CDATA[container]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[WebSphere]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[WWW]]></category>

		<guid isPermaLink="false">http://bernhard.hensler.net/blog/?p=1405</guid>
		<description><![CDATA[apache
check Apache server version by creating a simple e.g. serverinfo.php file with following statement: &#60;?php phpinfo(); ?&#62;
and open in your browser: http://your host/serverinfo.php. Find the version info in the Apache Version section:
Apache Version &#8211; Apache/2.0.53 (Linux/SUSE)
or run from the command line:
/usr/sbin # apache2ctl -v
Server version: Apache/2.0.53
Server built:   Aug 30 2006 13:14:23
h969344:/usr/sbin #
Next add [...]]]></description>
			<content:encoded><![CDATA[<h2>apache</h2>
<p>check Apache server version by creating a simple e.g. <em>serverinfo.php</em> file with following statement: <em>&lt;?php phpinfo(); ?&gt;</em></p>
<p>and open in your browser: http://your host/serverinfo.php. Find the version info in the Apache Version section:</p>
<blockquote><p><span style="color: #ff0000;">Apache Version</span> &#8211; Apache/2.0.53 (Linux/SUSE)</p></blockquote>
<p>or run from the command line:</p>
<blockquote><p>/usr/sbin # apache2ctl -v</p>
<p>Server version: Apache/2.0.53</p>
<p>Server built:   Aug 30 2006 13:14:23</p>
<p>h969344:/usr/sbin #</p></blockquote>
<p>Next add <em>mod_status</em> to your APACHE_MODULES by editing /etc/sysconfig/apache2 configuration &#8211; the Status module allows a server administrator to find out how well a server is performing. A HTML page is presented that gives the current server statistics in an easily readable form:</p>
<blockquote><p>APACHE_MODULES=</p>
<p>&#8220;access actions alias auth auth_dbm autoindex cgi</p>
<p>dir env expires headers include log_config mime</p>
<p><span style="color: #ff0000;">mod_status</span> negotiation setenvif</p>
<p>ssl suexec userdir php4 rewrite&#8221;</p></blockquote>
<p><span id="more-1405"></span></p>
<p>In the same file and if extended logging is needed, set APACHE_EXTENDED_STATUS=&#8221;<span style="color: #ff0000;">on</span>&#8221; &#8211; be careful here, this will degrade performance.</p>
<p>Edit httpd.conf and add a Location section to your virtualhost section (remove <em>Include /etc/apache2/mod_status.conf</em>):</p>
<blockquote><p>&lt;VirtualHost *:80&gt;</p>
<p>&#8230;.</p>
<p>&lt;Location /<span style="color: #ff0000;">server-status</span>&gt;</p>
<p>SetHandler server-status</p>
<p># Order deny,allow</p>
<p># Deny from all</p>
<p>Allow from .yourdomain</p>
<p>&lt;/Location&gt;</p>
<p>&#8230;.</p>
<p>&lt;/VirtualHost&gt;</p></blockquote>
<p>restart the HTTP server: /usr/sbin/rcapache2 <span style="color: #ff0000;">restart</span></p>
<p>You should see your Apache server status now by issuing this URL: http://yourHost/<span style="color: #ff0000;">server-status<span style="color: #000000;"> </span></span> providing the following information:</p>
<ul style="margin-bottom: 1em; list-style-type: disc;">
<li style="line-height: 1.3em;">The number of worker serving requests</li>
<li style="line-height: 1.3em;">The number of idle worker</li>
<li style="line-height: 1.3em;">The status of each worker, the number of requests that worker has performed and the total number of bytes served by the worker (*)</li>
<li style="line-height: 1.3em;">A total number of accesses and byte count served (*)</li>
<li style="line-height: 1.3em;">The time the server was started/restarted and the time it has been running for</li>
<li style="line-height: 1.3em;">Averages giving the number of requests per second, the number of bytes served per second and the average number of bytes per request (*)</li>
<li style="line-height: 1.3em;">The current percentage CPU used by each worker and in total by Apache (*)</li>
<li style="line-height: 1.3em;">The current hosts and requests being processed (*)</li>
</ul>
<p>The lines marked &#8220;(*)&#8221; are only available if ExtendedStatus is On</p>
<h2>awstats</h2>
<p><span style="color: #ff0000;"><span style="color: #000000;">To display HTTP server log information in a graphical form, install <a href="http://awstats.sourceforge.net/" title="awstats" target="_blank" class="liexternal"><strong>awstats</strong></a>:</span></span></p>
<blockquote><p>AWStats is a free powerful and featureful tool that generates advanced web, streaming, ftp or mail server statistics, graphically.</p></blockquote>
<p>Copy awstats to a directory of your choice, installation defaults to /usr/local/awstats. Then run the awstats configuration process: <em>perl awstats_configure.pl</em>, which will add directives to your httpd.conf and create a configuration file (default location: /etc/awstats)</p>
<blockquote><p>&lt;Directory &#8220;/usr/local/awstats/wwwroot&#8221;&gt;</p>
<p>Options all</p>
<p>AllowOverride None</p>
<p>Order allow,deny</p>
<p>Allow from all</p>
<p>&lt;/Directory&gt;</p>
<p>Alias /awstatsclasses &#8220;/usr/local/awstats/wwwroot/classes/&#8221;</p>
<p>Alias /awstatscss &#8220;/usr/local/awstats/wwwroot/css/&#8221;</p>
<p>Alias /awstatsicons &#8220;/usr/local/awstats/wwwroot/icon/&#8221;</p>
<p>ScriptAlias /awstats/ &#8220;/usr/local/awstats/wwwroot/cgi-bin/&#8221;</p></blockquote>
[SinglePic not found]
<p>Once done run the data import process from the cgi-bin folder of your awstats installation (you can automate this in the config file): perl awstats.pl config=yourdomain. See results of your site: http://yourdomain/awstats/awstats.pl or at this <a href="http://www.nltechno.com/awstats/awstats.pl?config=destailleur.fr" class="liexternal">demo site</a></p>
<p>This <a href="http://bernhard.hensler.net/blog/steps-to-visualize-http-server-logging-part-ii/" title="HTT PServer logging part II" class="liinternal">link</a> to part II of the tutorial.</p>
]]></content:encoded>
			<wfw:commentRss>http://bernhard.hensler.net/blog/steps-to-visualize-http-server-logging-part-i/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>php &amp; post_max_size &#8211; upload_max_filesize</title>
		<link>http://bernhard.hensler.net/blog/php-post_max_size-upload_max_filesize/</link>
		<comments>http://bernhard.hensler.net/blog/php-post_max_size-upload_max_filesize/#comments</comments>
		<pubDate>Tue, 19 Aug 2008 08:35:55 +0000</pubDate>
		<dc:creator>bernhard</dc:creator>
				<category><![CDATA[container]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://bernhard.hensler.net/blog/?p=704</guid>
		<description><![CDATA[Für den upload grösserer Dateien in einem post reicht es nicht, in der php.ini nur den &#8220;upload_max_filesize&#8221; zu erhöhen &#8211; es braucht ebenfalls den &#8220;post_max_size&#8221;.
Wer eine &#8220;globale&#8221; Einstellung vermeiden will, kann die Import Werte auch über eine .htaccess Datei verändern &#8211; so zumindestens lt. diesem Artikel:
how to &#8230;:




* Öffnen oder Anlegen einer Datei .htaccess im [...]]]></description>
			<content:encoded><![CDATA[<p>Für den upload grösserer Dateien in einem post reicht es nicht, in der php.ini nur den &#8220;upload_max_filesize&#8221; zu erhöhen &#8211; es braucht ebenfalls den &#8220;post_max_size&#8221;.</p>
<p>Wer eine &#8220;globale&#8221; Einstellung vermeiden will, kann die Import Werte auch über eine .htaccess Datei verändern &#8211; so zumindestens lt. diesem <a href="http://www.andi.de/2006/11/18/wordpress-upload-aufbohren/" target="_blank" class="liexternal">Artikel</a>:<span id="more-704"></span></p>
<p><a href="#" onclick="xcollapse('X5002');return false;" class="liinternal">how to &#8230;:</a><br />
</p>
<table id="X5002" style="display: none; border: 1px solid #C0C0C0; background-color: #F6F6F6;">
<tr>
<td>
* Öffnen oder Anlegen einer Datei .htaccess im Verzeichnis /wp-admin/ innerhalb der WordPress-Installation.</p>
<p>* Dort z.B. folgende Werte einfügen:</p>
<p>php_value upload_max_filesize &#8220;90M&#8221;<br />
php_value post_max_size &#8220;95M&#8221;<br />
php_value max_execution_time 3200<br />
php_value max_input_time 3200<br />
php_value memory_limit 35M</p>
<p>* Damit wird das Upload-Limit auf 90 Megabyte und die Ausführungszeit auf über 50 Minuten angehoben.<br />
* Dadurch sollte auch der Upload von großen Video-Dateien möglich sein.
</td>
</tr>
</table>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://bernhard.hensler.net/blog/php-post_max_size-upload_max_filesize/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>premature end &#8230;.</title>
		<link>http://bernhard.hensler.net/blog/premature-end/</link>
		<comments>http://bernhard.hensler.net/blog/premature-end/#comments</comments>
		<pubDate>Thu, 03 Aug 2006 16:59:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[container]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://bernhard.hensler.net/blog/?p=151</guid>
		<description><![CDATA[http://wordpress.org/support/topic/76274

Thanks Yosemite, you were right. My host was cool, they said
&#8220;This error is due to the fact that the maximum size of php files which were to be executed was 8MB, I increased this size to 32 and the problem is solved as I checked it.Please let us know if the problem persists.&#8221;


03.08.06
set maximum memory [...]]]></description>
			<content:encoded><![CDATA[<p>http://wordpress.org/support/topic/76274</p>
<blockquote><p>
Thanks Yosemite, you were right. My host was cool, they said</p>
<p>&#8220;This error is due to the fact that the maximum size of php files which were to be executed was 8MB, I increased this size to 32 and the problem is solved as I checked it.Please let us know if the problem persists.&#8221;
</p></blockquote>
<p>
03.08.06<br />
set maximum memory for execution of php files to 16mb in php.ini</p>
<p>siehe auch: http://bernhard.hensler.net/blog/?p=704</p>
]]></content:encoded>
			<wfw:commentRss>http://bernhard.hensler.net/blog/premature-end/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
