<?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>workblog &#187; Virtuozzo/Plesk</title>
	<atom:link href="http://iandunn.name/workblog/category/virtuozzo-plesk/feed/" rel="self" type="application/rss+xml" />
	<link>http://iandunn.name/workblog</link>
	<description></description>
	<lastBuildDate>Wed, 25 Aug 2010 22:23:41 +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>PHP Error Logs with Virtuozzo</title>
		<link>http://iandunn.name/workblog/php-error-logs-with-virtuozzo/</link>
		<comments>http://iandunn.name/workblog/php-error-logs-with-virtuozzo/#comments</comments>
		<pubDate>Mon, 10 May 2010 19:26:03 +0000</pubDate>
		<dc:creator>Ian</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Virtuozzo/Plesk]]></category>

		<guid isPermaLink="false">http://iandunn.name/workblog/?p=278</guid>
		<description><![CDATA[Virtuozzo sets domains up to have PHP&#8217;s display_errors flag turned off by default, so that you&#8217;ll only see a blank page when there are critical errors. This is a good thing in production environments because it avoids potential security issues, but it can also be annoying when you&#8217;re trying to debug something.
Instead of displaying the [...]]]></description>
			<content:encoded><![CDATA[<p>Virtuozzo sets domains up to have PHP&#8217;s display_errors flag turned off by default, so that you&#8217;ll only see a blank page when there are critical errors. This is a good thing in production environments because it avoids potential security issues, but it can also be annoying when you&#8217;re trying to debug something.</p>
<p>Instead of displaying the errors, you can configure PHP to log them and then use the logs for debugging. For a Linux environment, you&#8217;ll need to create a file named vhost.conf inside the domain&#8217;s conf directory, <em>/var/www/vhosts/domain.name/conf</em>.</p>
<pre name="code" class="css">

&lt;Directory /var/www/vhosts/domain.name&gt;
php_value error_log /var/www/vhosts/domain.name/statistics/logs/php-errors.log
php_flag display_errors off
php_value error_reporting 6143
php_flag log_errors on
&lt;/Directory&gt;
</pre>
<p>Then create the file and assign it the right permissions</p>
<pre name="code" class="css">

cd /var/www/vhosts/domain.name/statistics/logs/
touch php-errors.log
chown apache php-errors.log
</pre>
<p>And the last thing is to tell Apache to reread the updated conf file</p>
<pre name="code" class="css">

/usr/local/psa/admin/sbin/websrvmng -a
</pre>
]]></content:encoded>
			<wfw:commentRss>http://iandunn.name/workblog/php-error-logs-with-virtuozzo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Firewalling an OpenVZ node and containers</title>
		<link>http://iandunn.name/workblog/firewalling-an-openvz-node-and-containers/</link>
		<comments>http://iandunn.name/workblog/firewalling-an-openvz-node-and-containers/#comments</comments>
		<pubDate>Fri, 30 Apr 2010 17:13:31 +0000</pubDate>
		<dc:creator>Ian</dc:creator>
				<category><![CDATA[Linux/Unix]]></category>
		<category><![CDATA[Virtuozzo/Plesk]]></category>

		<guid isPermaLink="false">http://iandunn.name/workblog/?p=266</guid>
		<description><![CDATA[The OpenVZ wiki has a nice script for firewalling an OpenVZ node and it&#8217;s containers. It creates a service and configures iptables to block all traffic to the node (except the ports you specify), but allow all traffic through to the containers, so that they can manage their own firewall. It also allows the container&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p>The OpenVZ wiki has a nice script for <a href="http://wiki.openvz.org/Setting_up_an_iptables_firewall">firewalling an OpenVZ node and it&#8217;s containers</a>. It creates a service and configures iptables to block all traffic to the node (except the ports you specify), but allow all traffic through to the containers, so that they can manage their own firewall. It also allows the container&#8217;s firewalls to be managed on the node through a simple config file.</p>
]]></content:encoded>
			<wfw:commentRss>http://iandunn.name/workblog/firewalling-an-openvz-node-and-containers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Working with Qmail&#8217;s Queue</title>
		<link>http://iandunn.name/workblog/252/</link>
		<comments>http://iandunn.name/workblog/252/#comments</comments>
		<pubDate>Mon, 08 Mar 2010 22:21:00 +0000</pubDate>
		<dc:creator>Ian</dc:creator>
				<category><![CDATA[Spam]]></category>
		<category><![CDATA[Virtuozzo/Plesk]]></category>

		<guid isPermaLink="false">http://iandunn.name/workblog/?p=252</guid>
		<description><![CDATA[qmqtool is a great tool for viewing and changing messages in qmail&#8217;s queue. It&#8217;ll help you search for and delete spam, for instance. The FAQ has a some examples to get started with.
]]></description>
			<content:encoded><![CDATA[<p><a href="http://freshmeat.net/projects/qmqtool/">qmqtool</a> is a great tool for viewing and changing messages in qmail&#8217;s queue. It&#8217;ll help you search for and delete spam, for instance. The <a title="qmqtool FAQ" href="http://jeremy.kister.net/code/qmqtool/current/FAQ">FAQ</a> has a some examples to get started with.</p>
]]></content:encoded>
			<wfw:commentRss>http://iandunn.name/workblog/252/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Relaying Qmail Through a Spam Filter</title>
		<link>http://iandunn.name/workblog/relaying-qmail-through-a-spam-filter/</link>
		<comments>http://iandunn.name/workblog/relaying-qmail-through-a-spam-filter/#comments</comments>
		<pubDate>Tue, 02 Mar 2010 01:19:47 +0000</pubDate>
		<dc:creator>Ian</dc:creator>
				<category><![CDATA[Linux/Unix]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[Virtuozzo/Plesk]]></category>

		<guid isPermaLink="false">http://iandunn.name/workblog/?p=250</guid>
		<description><![CDATA[If you&#8217;re running a mail service on a web server so it can send out e-mail from contact forms, etc then you&#8217;ll want to make sure it&#8217;s relaying outbound mail through a spam filter, or it could be used to send spam if the forms get hijacked. For qmail, you just need to create /var/qmail/control/smtproutes [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re running a mail service on a web server so it can send out e-mail from contact forms, etc then you&#8217;ll want to make sure it&#8217;s <a href="http://blog.pivotalweb.com/?p=19">relaying outbound mail through a spam filter</a>, or it could be used to send spam if the forms get hijacked. For qmail, you just need to create /var/qmail/control/smtproutes and enter &#8220;:yourmailserver.com&#8221;, then restart. Make sure the spam filter is configured to allow the mail server to relay through it.</p>
]]></content:encoded>
			<wfw:commentRss>http://iandunn.name/workblog/relaying-qmail-through-a-spam-filter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Additional FTP accounts on Plesk for Linux</title>
		<link>http://iandunn.name/workblog/additional-ftp-accounts-on-plesk-for-linux/</link>
		<comments>http://iandunn.name/workblog/additional-ftp-accounts-on-plesk-for-linux/#comments</comments>
		<pubDate>Thu, 12 Mar 2009 15:34:12 +0000</pubDate>
		<dc:creator>Ian</dc:creator>
				<category><![CDATA[Linux/Unix]]></category>
		<category><![CDATA[Virtuozzo/Plesk]]></category>

		<guid isPermaLink="false">http://iandunn.name/workblog/?p=72</guid>
		<description><![CDATA[Before version 9 of Plesk you couldn&#8217;t add additional FTP accounts for a domain through the control panel. This KB explains how to manually add extra FTP accounts that are restricted to their home directory.
]]></description>
			<content:encoded><![CDATA[<p>Before version 9 of Plesk you couldn&#8217;t add additional FTP accounts for a domain through the control panel. This KB explains how to manually <a href="http://kb.parallels.com/en/415">add extra FTP accounts that are restricted to their home directory</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://iandunn.name/workblog/additional-ftp-accounts-on-plesk-for-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
