<?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>Debian Tutorials &#187; etch</title>
	<atom:link href="http://www.debiantutorials.com/tag/etch/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.debiantutorials.com</link>
	<description>Copy/Paste tutorials for Debian based Linux distros</description>
	<lastBuildDate>Tue, 27 Dec 2011 01:15:56 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Installing Dovecot IMAP and POP daemon with MySql backend</title>
		<link>http://www.debiantutorials.com/installing-dovecot-imap-and-pop-daemon-with-mysql-backend/</link>
		<comments>http://www.debiantutorials.com/installing-dovecot-imap-and-pop-daemon-with-mysql-backend/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 15:06:03 +0000</pubDate>
		<dc:creator>aip</dc:creator>
				<category><![CDATA[Lenny]]></category>
		<category><![CDATA[Mail]]></category>
		<category><![CDATA[dovecot]]></category>
		<category><![CDATA[etch]]></category>
		<category><![CDATA[imap]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[pop3]]></category>

		<guid isPermaLink="false">http://www.debiantutorials.net/?p=197</guid>
		<description><![CDATA[Dovecot is an open source IMAP and POP3 server for Linux/UNIX-like systems, written primarily with security in mind. Dovecot primarily aims to be a lightweight, fast and easy to set up open source mailserver. It's assumed that you have already installed and configured Postfix according to this tutorial: Installing Postfix with MySql backend and SASL [...]]]></description>
			<content:encoded><![CDATA[<p>Dovecot is an open source IMAP and POP3 server for Linux/UNIX-like systems, written primarily with security in mind. Dovecot primarily aims to be a lightweight, fast and easy to set up open source mailserver.</p>
<p>It's assumed that you have already installed and configured Postfix according to this tutorial:<br />
<a href="http://www.debiantutorials.net/installing-postfix-with-mysql-backend-and-sasl-for-smtp-authentication/">Installing Postfix with MySql backend and SASL for SMTP authentication</a></p>
<p>1. Install required packages</p>
<p><code>apt-get install dovecot-imapd dovecot-pop3d<br />
</code><span id="more-197"></span></p>
<p>2. Configure Dovecot (pico /etc/dovecot/dovecot.conf)</p>
<p><code>protocols = imap imaps pop3 pop3s<br />
ssl_disable = no<br />
mail_location = maildir:/home/vmail/%d/%n<br />
auth default {<br />
	passdb sql {<br />
	  args = /etc/dovecot/dovecot-sql.conf<br />
	}<br />
	userdb sql {<br />
	  args = /etc/dovecot/dovecot-sql.conf<br />
	}<br />
}<br />
disable_plaintext_auth = no<br />
user = vmail<br />
</code></p>
<p><em>Add or edit the above properties and leave everything else with the default value or configure according to your needs</em></p>
<p>3. Configure the MySql connector (pico /etc/dovecot/dovecot-sql.conf)</p>
<p><code>driver = mysql<br />
connect = host=127.0.0.1 dbname={database} user={username} password={password}<br />
default_pass_scheme = CRYPT<br />
password_query = SELECT email as user, password FROM users WHERE email = '%u'<br />
user_query = SELECT CONCAT('/home/vmail/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1),'/') as home, '5000' as uid, '5000' as gid FROM users WHERE email = '%u'<br />
</code></p>
<p><em>{database} = MySql database name<br />
{username} = MySql username<br />
{password} = MySql password</em></p>
<p>4. Restart Dovecot daemon</p>
<p><code>/etc/init.d/dovecot restart<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.debiantutorials.com/installing-dovecot-imap-and-pop-daemon-with-mysql-backend/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Installing Courier POP3 and IMAP daemon with MySql backend</title>
		<link>http://www.debiantutorials.com/installing-courier-pop3-and-imap-daemon-with-mysql-backend-install-courier/</link>
		<comments>http://www.debiantutorials.com/installing-courier-pop3-and-imap-daemon-with-mysql-backend-install-courier/#comments</comments>
		<pubDate>Sun, 25 Oct 2009 11:02:31 +0000</pubDate>
		<dc:creator>aip</dc:creator>
				<category><![CDATA[Lenny]]></category>
		<category><![CDATA[Mail]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[courier]]></category>
		<category><![CDATA[etch]]></category>
		<category><![CDATA[imap]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[pop3]]></category>

		<guid isPermaLink="false">http://www.debiantutorials.net/?p=191</guid>
		<description><![CDATA[The Courier mail transfer agent (MTA) is an integrated mail/groupware server based on open commodity protocols, such as ESMTP, IMAP, POP3, LDAP, SSL, and HTTP. Courier provides ESMTP, IMAP, POP3, webmail, and mailing list services within a single, consistent, framework. In this tutorial we'll only use the Courier POP3 and IMAP services. It's assumed that [...]]]></description>
			<content:encoded><![CDATA[<p>The Courier mail transfer agent (MTA) is an integrated mail/groupware server based on open commodity protocols, such as ESMTP, IMAP, POP3, LDAP, SSL, and HTTP. Courier provides ESMTP, IMAP, POP3, webmail, and mailing list services within a single, consistent, framework. In this tutorial we'll only use the Courier POP3 and IMAP services.</p>
<p>It's assumed that you have already installed and configured Postfix according to this tutorial: <a href="http://www.debiantutorials.net/installing-postfix-with-mysql-backend-and-sasl-for-smtp-authentication/">Installing Postfix with MySql backend and SASL for SMTP authentication</a></p>
<p>1. Install required packages</p>
<p><code>apt-get install courier-authdaemon courier-authlib-mysql courier-pop courier-pop-ssl courier-imap courier-imap-ssl<br />
</code><span id="more-191"></span></p>
<p>2. Make Courier use MySql backend (pico /etc/courier/authdaemonrc)</p>
<p><code>authmodulelist="authmysql"<br />
</code></p>
<p>3. Configure the MySql connector (pico /etc/courier/authmysqlrc)</p>
<p><code>MYSQL_SERVER 127.0.0.1<br />
MYSQL_USERNAME {username}<br />
MYSQL_PASSWORD {password}<br />
MYSQL_PORT 0<br />
MYSQL_DATABASE {database}<br />
MYSQL_USER_TABLE users<br />
MYSQL_CRYPT_PWFIELD password<br />
MYSQL_UID_FIELD 5000<br />
MYSQL_GID_FIELD 5000<br />
MYSQL_LOGIN_FIELD email<br />
MYSQL_HOME_FIELD "/home/vmail"<br />
MYSQL_MAILDIR_FIELD CONCAT(SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1),'/')<br />
MYSQL_QUOTA_FIELD quota<br />
</code></p>
<p><em>{database} = MySql database name<br />
MySql username<br />
MySql password</em></p>
<p>4. Restart Courier daemons</p>
<p><code>/etc/init.d/courier-authdaemon restart<br />
/etc/init.d/courier-imap restart<br />
/etc/init.d/courier-imap-ssl restart<br />
/etc/init.d/courier-pop restart<br />
/etc/init.d/courier-pop-ssl restart<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.debiantutorials.com/installing-courier-pop3-and-imap-daemon-with-mysql-backend-install-courier/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MySql database replication (master/slave)</title>
		<link>http://www.debiantutorials.com/mysql-database-replication-masterslave/</link>
		<comments>http://www.debiantutorials.com/mysql-database-replication-masterslave/#comments</comments>
		<pubDate>Sun, 04 Oct 2009 23:14:27 +0000</pubDate>
		<dc:creator>aip</dc:creator>
				<category><![CDATA[Lenny]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[etch]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[replication]]></category>

		<guid isPermaLink="false">http://www.debiantutorials.net/?p=125</guid>
		<description><![CDATA[In this tutorial we'll create a simple one-way master/slave database replication. You must have at least one master and one slave but you can use multiple slaves. Master 1. Configure master to listen on all ip addresses (pico /etc/mysql/my.cnf) #bind-address = 127.0.0.1 Comment out this line or remove it 2. Configure server id, log file [...]]]></description>
			<content:encoded><![CDATA[<p>In this tutorial we'll create a simple one-way master/slave database replication. You must have at least one master and one slave but you can use multiple slaves.</p>
<p><strong>Master</strong></p>
<p>1. Configure master to listen on all ip addresses (pico /etc/mysql/my.cnf)</p>
<p><code>#bind-address            = 127.0.0.1<br />
</code><span id="more-125"></span></p>
<p><em>Comment out this line or remove it</em></p>
<p>2. Configure server id, log file location and which databases are allowed to be replicated (pico /etc/mysql/my.cnf)</p>
<p><code>server-id               = 1<br />
log_bin                 = /var/log/mysql/mysql-bin.log<br />
binlog_do_db            = {database}<br />
</code></p>
<p><em>Replace {database} with the one you would like to replicate</em></p>
<p>3. Restart MySql</p>
<p><code>/etc/init.d/mysql restart<br />
</code></p>
<p>4. Create a user and allow it to act as slave for this server (mysql -u root -p)</p>
<p><code>GRANT REPLICATION SLAVE ON *.* TO {username}@'{ip}' IDENTIFIED BY '{password}';<br />
FLUSH PRIVILEGES;<br />
</code></p>
<p><em>{username} = Your preferred username<br />
{password} = Your password<br />
{ip} = IP address of the slave system or % to allow all ip addresses</em></p>
<p>5. Show current log file and position (mysql -u root -p)</p>
<p><code>SHOW MASTER STATUS;<br />
</code></p>
<p>This will return something like this:</p>
<p><code>+------------------+----------+--------------+------------------+<br />
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB |<br />
+------------------+----------+--------------+------------------+<br />
| mysql-bin.000004 |     2751 | {database}   |                  |<br />
+------------------+----------+--------------+------------------+<br />
</code></p>
<p><em>Keep the file name and position. It will be used later on the slave</em></p>
<p>6. Transfer data from the master to the slave</p>
<p>You can do this using various methods including exporting and importing using phpMyAdmin, creating a database dump from the master and import to the slave and "LOAD DATA FROM MASTER".</p>
<p><strong>Slave</strong></p>
<p>1. Configure this server to be a slave for the master MySql server (pico /etc/mysql/my.cnf)</p>
<p><code>server-id               = 2<br />
master-host             = {master_ip}<br />
master-user             = {username}<br />
master-password         = {password}<br />
master-connect-retry    = 60<br />
replicate-do-db         = {database}<br />
</code></p>
<p><em>{master_ip} = The ip of the master server<br />
{username} = The username you provided earlier on the master server<br />
{password} = The password you provided earlier on the master server<br />
{database} = The database you want to replicate</em></p>
<p>2. Restart MySql</p>
<p><code>/etc/init.d/mysql restart<br />
</code></p>
<p>3. Final configurations to make the slave replicate with the master (mysql -u root -p)</p>
<p><code>SLAVE STOP;<br />
CHANGE MASTER TO MASTER_HOST='{master_ip}', MASTER_USER='{username}', MASTER_PASSWORD='{password}', MASTER_LOG_FILE='{log_file}', MASTER_LOG_POS={log_position};<br />
SLAVE START;<br />
</code></p>
<p><em>{master_ip} = The ip of the master server<br />
{username} = The username you provided earlier on the master server<br />
{password} = The password you provided earlier on the master server<br />
{log_file} = Log file name from the master (ex. mysql-bin.000004)<br />
{log_position} = Log position from the master (ex. 2751)</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.debiantutorials.com/mysql-database-replication-masterslave/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Port forwarding with iptables</title>
		<link>http://www.debiantutorials.com/port-forwarding-with-iptables/</link>
		<comments>http://www.debiantutorials.com/port-forwarding-with-iptables/#comments</comments>
		<pubDate>Wed, 30 Sep 2009 23:46:03 +0000</pubDate>
		<dc:creator>aip</dc:creator>
				<category><![CDATA[Lenny]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[etch]]></category>
		<category><![CDATA[iptables]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[routing]]></category>

		<guid isPermaLink="false">http://www.debiantutorials.net/?p=122</guid>
		<description><![CDATA[In this tutorial we'll set up a simple port forwarding (NAT) using iptables. 1. Enable ip forward echo "1" > /proc/sys/net/ipv4/ip_forward 2. Append routing rules to the nat table iptables -t nat -A PREROUTING -p tcp -s 0/0 -d {local_ip} --dport {local_port} -j DNAT --to {destination_ip}:{destination_port} iptables -t nat -A POSTROUTING -o eth0 -d {destination_ip} [...]]]></description>
			<content:encoded><![CDATA[<p>In this tutorial we'll set up a simple port forwarding (NAT) using iptables.</p>
<p>1. Enable ip forward</p>
<p><code>echo "1" > /proc/sys/net/ipv4/ip_forward<br />
</code><span id="more-122"></span></p>
<p>2. Append routing rules to the nat table</p>
<p><code>iptables -t nat -A PREROUTING -p tcp -s 0/0 -d {local_ip} --dport {local_port} -j DNAT --to {destination_ip}:{destination_port}<br />
iptables -t nat -A POSTROUTING -o eth0 -d {destination_ip} -j SNAT --to-source {local_ip}<br />
</code></p>
<ul>
<li>{local_ip}: A ip address mapped on the local system</li>
<li>{local_port}: The port you would like to listen on</li>
<li>{destination_ip}: Destination ip address</li>
<li>{destination_port}: Destination port</li>
</ul>
<p>3. Now you can access http://{local_ip}:{local_port} and would actually be getting response from http://{destination_ip}:{destination_port}</p>
<p><strong>A working example</strong></p>
<p>If the ip address of your system is 32.64.128.200 and you import the following rules, you would be able to connect to http://32.64.128.200:8080 and actually see the Google search engine because 216.239.59.105:80 is one of Google's web servers.</p>
<p><code>iptables -t nat -A PREROUTING -p tcp -s 0/0 -d 32.64.128.200 --dport 8080 -j DNAT --to 216.239.59.105:80<br />
iptables -t nat -A POSTROUTING -o eth0 -d 216.239.59.105 -j SNAT --to-source 32.64.128.200<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.debiantutorials.com/port-forwarding-with-iptables/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Installing Zend Optimizer</title>
		<link>http://www.debiantutorials.com/installing-zend-optimizer/</link>
		<comments>http://www.debiantutorials.com/installing-zend-optimizer/#comments</comments>
		<pubDate>Sat, 26 Sep 2009 09:26:05 +0000</pubDate>
		<dc:creator>aip</dc:creator>
				<category><![CDATA[Jaunty Jackalope]]></category>
		<category><![CDATA[Karmic Koala]]></category>
		<category><![CDATA[Lenny]]></category>
		<category><![CDATA[Squeeze]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[etch]]></category>
		<category><![CDATA[jaunty]]></category>
		<category><![CDATA[karmic]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[zend]]></category>

		<guid isPermaLink="false">http://www.debiantutorials.net/?p=109</guid>
		<description><![CDATA[The Zend Optimizer enables you to run Zend Guard encoded files. 1. Download a copy of Zend Optimizer / Guard from the location below and put it into /tmp http://www.zend.com/en/products/guard/downloads 2. Extract cd /tmp tar zxvf ZendOptimizer-3.3.9-linux-glibc23-i386.tar.gz Replace with your actual filename 3. Create a directory to contain Zend optimizer mkdir /usr/local/lib/Zend 3. Move the [...]]]></description>
			<content:encoded><![CDATA[<p>The Zend Optimizer enables you to run Zend Guard encoded files.</p>
<p>1. Download a copy of Zend Optimizer / Guard from the location below and put it into /tmp</p>
<p><code>http://www.zend.com/en/products/guard/downloads<br />
</code><span id="more-109"></span></p>
<p>2. Extract</p>
<p><code>cd /tmp<br />
tar zxvf ZendOptimizer-3.3.9-linux-glibc23-i386.tar.gz<br />
</code></p>
<p><em>Replace with your actual filename</em></p>
<p>3. Create a directory to contain Zend optimizer</p>
<p><code>mkdir /usr/local/lib/Zend<br />
</code></p>
<p>3. Move the Zend optimizer lib to a permanent location</p>
<p><code>mv ZendOptimizer-3.3.9-linux-glibc23-i386/data/5_2_x_comp/ZendOptimizer.so /usr/local/lib/Zend/<br />
</code></p>
<p><em>Your ZendOptimizer directory name may be different since it includes version numbers and platform. I'm using the 5_2_x_comp directory because I have PHP 5.2 installed.</em></p>
<p>4. Add reference to your php.ini file (pico /etc/php5/apache2/php.ini)</p>
<p><code>zend_extension = /usr/local/lib/Zend/ZendOptimizer.so<br />
zend_optimizer.optimization_level = 15<br />
</code></p>
<p>5. Restart apache</p>
<p><code>/etc/init.d/apache2 restart<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.debiantutorials.com/installing-zend-optimizer/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
		<item>
		<title>Using Debian Volatile to keep your packages updated</title>
		<link>http://www.debiantutorials.com/using-debian-volatile-to-keep-your-packages-updated/</link>
		<comments>http://www.debiantutorials.com/using-debian-volatile-to-keep-your-packages-updated/#comments</comments>
		<pubDate>Sat, 22 Aug 2009 13:13:29 +0000</pubDate>
		<dc:creator>aip</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Lenny]]></category>
		<category><![CDATA[apt]]></category>
		<category><![CDATA[etch]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[volatile]]></category>

		<guid isPermaLink="false">http://www.debiantutorials.net/?p=96</guid>
		<description><![CDATA[Some packages aim at fast moving targets, such as spam filtering and virus scanning, and even when using updated data patterns, they do not really work for the full time of a stable release. The main goal of volatile is allowing system administrators to update their systems in a nice, consistent way, without getting the [...]]]></description>
			<content:encoded><![CDATA[<p>Some packages aim at fast moving targets, such as spam filtering and virus scanning, and even when using updated data patterns, they do not really work for the full time of a stable release. The main goal of volatile is allowing system administrators to update their systems in a nice, consistent way, without getting the drawbacks of using unstable, even without getting the drawbacks for the selected packages. So debian-volatile will only contain changes to stable programs that are necessary to keep them functional.<span id="more-96"></span></p>
<p>1. Add volatile archive to apt sources (pico /etc/apt/sources.list)</p>
<p>Etch:<br />
<code>deb http://volatile.debian.org/debian-volatile etch/volatile main contrib non-free<br />
</code></p>
<p>Lenny:<br />
<code>deb http://volatile.debian.org/debian-volatile lenny/volatile main contrib non-free<br />
</code></p>
<p><em>Note. Only add one of the line depending on your Debian version.</em></p>
<p>2. Update apt repository</p>
<p><code>apt-get update<br />
</code></p>
<p>3. Upgrade you packages</p>
<p><code>apt-get dist-upgrade<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.debiantutorials.com/using-debian-volatile-to-keep-your-packages-updated/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Add an additional IP address to your server</title>
		<link>http://www.debiantutorials.com/add-an-additional-ip-address-to-your-server/</link>
		<comments>http://www.debiantutorials.com/add-an-additional-ip-address-to-your-server/#comments</comments>
		<pubDate>Wed, 05 Aug 2009 22:47:22 +0000</pubDate>
		<dc:creator>aip</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Lenny]]></category>
		<category><![CDATA[etch]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[network]]></category>

		<guid isPermaLink="false">http://www.debiantutorials.net/?p=94</guid>
		<description><![CDATA[1. Open the network configuration file (pico /etc/network/interfaces) Check the name of your network interface. You should see a line similar to this one: "iface eth0 inet static". In my case the name is eth0. Add these lines to the end of the file: auto eth0:1 iface eth0:1 inet static address 192.168.1.3 netmask 255.255.255.0 broadcast [...]]]></description>
			<content:encoded><![CDATA[<p>1. Open the network configuration file (pico /etc/network/interfaces)</p>
<p>Check the name of your network interface. You should see a line similar to this one: "iface eth0 inet static". In my case the name is eth0.</p>
<p>Add these lines to the end of the file:</p>
<p><code>auto eth0:1<br />
iface eth0:1 inet static<br />
address 192.168.1.3<br />
netmask 255.255.255.0<br />
broadcast 192.168.1.255<br />
network 192.168.1.0<br />
</code><span id="more-94"></span></p>
<p><em>Replace eth0 by your network interface name. If you are adding multiple IP addresses to the same system, you can increase the number after "eth0:".</em></p>
<p>2. Activate the new virtual network interface</p>
<p><code>ifup eth0:1<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.debiantutorials.com/add-an-additional-ip-address-to-your-server/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Monitoring multiple servers with Munin</title>
		<link>http://www.debiantutorials.com/monitoring-multiple-servers-with-munin/</link>
		<comments>http://www.debiantutorials.com/monitoring-multiple-servers-with-munin/#comments</comments>
		<pubDate>Mon, 06 Jul 2009 23:56:32 +0000</pubDate>
		<dc:creator>aip</dc:creator>
				<category><![CDATA[Lenny]]></category>
		<category><![CDATA[Monitoring]]></category>
		<category><![CDATA[etch]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[munin]]></category>

		<guid isPermaLink="false">http://www.debiantutorials.net/?p=68</guid>
		<description><![CDATA[Munin is a network/system monitoring application that presents output in graphs through a web interface. Its emphasis is on simple plug and play capabilities. A large number of monitoring plugins are available. Using Munin you can easily monitor the performance of your computers, networks, SANs, and quite possibly applications as well. It makes it easy [...]]]></description>
			<content:encoded><![CDATA[<p>Munin is a network/system monitoring application that presents output in graphs through a web interface. Its emphasis is on simple plug and play capabilities. A large number of monitoring plugins are available. Using Munin you can easily monitor the performance of your computers, networks, SANs, and quite possibly applications as well. It makes it easy to determine "what's different today" when a performance problem crops up. It makes it easy to see how you're doing capacity wise on all limited resources.</p>
<p></p>
<p><strong>Master monitoring server</strong></p>
<p>1. Install Munin and Munin node daemon:</p>
<p><code>apt-get install munin munin-node<br />
</code><span id="more-68"></span></p>
<p>2. Configure server being monitored (pico /etc/munin/munin.conf):</p>
<p><code>[host.domain.com]<br />
address xxx.xxx.xxx.xxx<br />
use_node_name yes<br />
</code></p>
<p><em>Replace host.domain.com with the server's fully qualified domain and xxx.xxx.xxx.xxx with it's IP address. Type this code for each and every server being monitored including the master server.</em></p>
<p>3. Configure the Munin node daemon (pico /etc/munin/munin-node.conf).</p>
<p>Set the master server host name (Must be the same as used in /etc/munin/munin.conf):</p>
<p><code>host_name host.domain.com<br />
</code></p>
<p>4. Restart Munin node daemon:</p>
<p><code>/etc/init.d/munin-node restart<br />
</code></p>
<p>&nbsp;<br />&nbsp;</p>
<p><strong>All other servers being monitored</strong></p>
<p>1. Install Munin and Munin node daemon:</p>
<p><code>apt-get install munin munin-node<br />
</code></p>
<p>2. Configure the Munin node daemon (pico /etc/munin/munin-node.conf).</p>
<p>Set this server's host name (Must be the same as used in /etc/munin/munin.conf on the master server):</p>
<p><code>host_name host.domain.com<br />
</code></p>
<p>Allow the master server to connect and grab data:</p>
<p><code>allow ^xxx\.xxx\.xxx\.xxx$<br />
</code></p>
<p><em>Replace ^xxx\.xxx\.xxx\.xxx$ with your server's IP address. For example if the master server's IP address is 192.168.1.1, you would use: ^192\.168\.1\.1$. The master server will connect to this server on port 4949 so make sure that port isn't blocked on firewalls.</em></p>
<p>3. Restart Munin node daemon:</p>
<p><code>/etc/init.d/munin-node restart<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.debiantutorials.com/monitoring-multiple-servers-with-munin/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Installing ionCube</title>
		<link>http://www.debiantutorials.com/installing-ioncube/</link>
		<comments>http://www.debiantutorials.com/installing-ioncube/#comments</comments>
		<pubDate>Mon, 18 May 2009 21:57:43 +0000</pubDate>
		<dc:creator>aip</dc:creator>
				<category><![CDATA[Jaunty Jackalope]]></category>
		<category><![CDATA[Karmic Koala]]></category>
		<category><![CDATA[Lenny]]></category>
		<category><![CDATA[Squeeze]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[etch]]></category>
		<category><![CDATA[ioncube]]></category>
		<category><![CDATA[jaunty]]></category>
		<category><![CDATA[karmic]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://debiantutorials.net/?p=55</guid>
		<description><![CDATA[ionCube protects software written using the PHP programming language from being viewed, changed, and run on unlicensed computers. 1. Download ionCube loaders wget http://downloads.ioncube.com/loader_downloads/ioncube_loaders_lin_x86.tar.gz 2. Extract tar zxvf ioncube_loaders_lin_x86.tar.gz 3. Move to a permanent location mv ioncube /usr/local/ 4. Add reference to your php.ini file (pico /etc/php5/apache2/php.ini) zend_extension = /usr/local/ioncube/ioncube_loader_lin_5.2.so There are a few versions [...]]]></description>
			<content:encoded><![CDATA[<p>ionCube protects software written using the PHP programming language from being viewed, changed, and run on unlicensed computers.</p>
<p>1. Download ionCube loaders</p>
<p><code>wget http://downloads.ioncube.com/loader_downloads/ioncube_loaders_lin_x86.tar.gz<br />
</code><span id="more-55"></span></p>
<p>2. Extract</p>
<p><code>tar zxvf ioncube_loaders_lin_x86.tar.gz<br />
</code></p>
<p>3. Move to a permanent location</p>
<p><code>mv ioncube /usr/local/<br />
</code></p>
<p>4. Add reference to your php.ini file (pico /etc/php5/apache2/php.ini)</p>
<p><code>zend_extension = /usr/local/ioncube/ioncube_loader_lin_5.2.so<br />
</code></p>
<p><em>There are a few versions of the loader in the tar archive and you can choose the one that suites your needs</em></p>
<p>5. Restart apache</p>
<p><code>/etc/init.d/apache2 restart<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.debiantutorials.com/installing-ioncube/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Installing PowerDNS on etch/lenny</title>
		<link>http://www.debiantutorials.com/installing-powerdns-on-eth-lenny/</link>
		<comments>http://www.debiantutorials.com/installing-powerdns-on-eth-lenny/#comments</comments>
		<pubDate>Sat, 16 May 2009 23:15:18 +0000</pubDate>
		<dc:creator>aip</dc:creator>
				<category><![CDATA[DNS]]></category>
		<category><![CDATA[Lenny]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[etch]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[powerdns]]></category>

		<guid isPermaLink="false">http://debiantutorials.net/?p=45</guid>
		<description><![CDATA[The PowerDNS Nameserver is a modern, advanced and high performance authoritative-only nameserver. It is written from scratch and conforms to all relevant DNS standards documents. Furthermore, PowerDNS interfaces with almost any database. This tutorial has been tested and is working on Debian etch and lenny 1. Install the PowerDNS server and MySql backend using apt [...]]]></description>
			<content:encoded><![CDATA[<p>The PowerDNS Nameserver is a modern, advanced and high performance authoritative-only nameserver. It is written from scratch and conforms to all relevant DNS standards documents. Furthermore, PowerDNS interfaces with almost any database.</p>
<p>This tutorial has been tested and is working on Debian etch and lenny</p>
<p>1. Install the PowerDNS server and MySql backend using apt</p>
<p><code>apt-get install pdns-server pdns-backend-mysql<br />
</code><span id="more-45"></span></p>
<p>2. Create a new database (or use existing) and execute the following SQL queries to create the PowerDNS table structure:</p>
<p><code>create table domains (<br />
id		 INT auto_increment,<br />
name		 VARCHAR(255) NOT NULL,<br />
master		 VARCHAR(128) DEFAULT NULL,<br />
last_check	 INT DEFAULT NULL,<br />
type		 VARCHAR(6) NOT NULL,<br />
notified_serial INT DEFAULT NULL,<br />
account         VARCHAR(40) DEFAULT NULL,<br />
primary key (id)<br />
)type=InnoDB;<br />
&nbsp;<br />
CREATE UNIQUE INDEX name_index ON domains(name);<br />
&nbsp;<br />
CREATE TABLE records (<br />
id              INT auto_increment,<br />
domain_id       INT DEFAULT NULL,<br />
name            VARCHAR(255) DEFAULT NULL,<br />
type            VARCHAR(6) DEFAULT NULL,<br />
content         VARCHAR(255) DEFAULT NULL,<br />
ttl             INT DEFAULT NULL,<br />
prio            INT DEFAULT NULL,<br />
change_date     INT DEFAULT NULL,<br />
primary key(id)<br />
)type=InnoDB;<br />
&nbsp;<br />
CREATE INDEX rec_name_index ON records(name);<br />
CREATE INDEX nametype_index ON records(name,type);<br />
CREATE INDEX domain_id ON records(domain_id);<br />
&nbsp;<br />
create table supermasters (<br />
ip VARCHAR(25) NOT NULL,<br />
nameserver VARCHAR(255) NOT NULL,<br />
account VARCHAR(40) DEFAULT NULL<br />
);<br />
</code></p>
<p>3. Configure PowerDNS to use the MySql backend by adding this line into the configuration file (pico /etc/powerdns/pdns.conf)</p>
<p><code>launch=gmysql<br />
</code></p>
<p>4. Configure MySql login information for the PowerDNS server that can read from the tables you created earlier by adding lines similar to these (pico /etc/powerdns/pdns.d/pdns.local)</p>
<p><code>gmysql-host=127.0.0.1<br />
gmysql-user=pdns<br />
gmysql-password=password<br />
gmysql-dbname=pdns<br />
</code></p>
<p><em>Replace the username, password and dbname with a valid login information and database name.</em></p>
<p>5. Restart PowerDNS</p>
<p><code>/etc/init.d/pdns restart<br />
</code></p>
<p>Now you should have a fully functional PowerDNS server installed. To manage the database (adding zones and records), consider using the <a href="http://www.poweradmin.org">Poweradmin</a> web-based administration tool.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.debiantutorials.com/installing-powerdns-on-eth-lenny/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
