<?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>DiegoWoitasen</title>
	<atom:link href="http://www.woitasen.com.ar/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.woitasen.com.ar</link>
	<description>Linux, BSD &#38; Free Software</description>
	<lastBuildDate>Thu, 19 Apr 2012 18:47:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Load balance between source IPs in Linux</title>
		<link>http://www.woitasen.com.ar/2012/03/load-balance-between-source-ips-in-linux/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=load-balance-between-source-ips-in-linux</link>
		<comments>http://www.woitasen.com.ar/2012/03/load-balance-between-source-ips-in-linux/#comments</comments>
		<pubDate>Tue, 20 Mar 2012 00:30:07 +0000</pubDate>
		<dc:creator>Diego Woitasen</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[System Administration]]></category>
		<category><![CDATA[iproute]]></category>
		<category><![CDATA[iptables]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[netfilter]]></category>

		<guid isPermaLink="false">http://www.woitasen.com.ar/?p=177</guid>
		<description><![CDATA[Today I received a question about how to distribute the outgoing connections between several IP addresses attached to an interface. Suppose that you have 3 IPs in the eth0 interface and you want to do round robin between that IPs for outgoing connections. With regular iproute commands you can&#8217;t. Doing some tricks with fwmarks, ip rule <a href='http://www.woitasen.com.ar/2012/03/load-balance-between-source-ips-in-linux/' class='excerpt-more'>[...]</a>]]></description>
		<wfw:commentRss>http://www.woitasen.com.ar/2012/03/load-balance-between-source-ips-in-linux/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>My two commits to the Linux Kernel</title>
		<link>http://www.woitasen.com.ar/2012/03/my-two-commits-to-the-linux-kernel/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=my-two-commits-to-the-linux-kernel</link>
		<comments>http://www.woitasen.com.ar/2012/03/my-two-commits-to-the-linux-kernel/#comments</comments>
		<pubDate>Thu, 15 Mar 2012 20:34:25 +0000</pubDate>
		<dc:creator>Diego Woitasen</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[kernel]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://www.woitasen.com.ar/?p=169</guid>
		<description><![CDATA[Four years ago I had nothing to do and started to read some pieces of the kernel code. I read about the BLK, a feature that kernel developers have been trying to remove the last years (I&#8217;m not sure if they have finished). My small contribution to that task was this two patches that I <a href='http://www.woitasen.com.ar/2012/03/my-two-commits-to-the-linux-kernel/' class='excerpt-more'>[...]</a>]]></description>
		<wfw:commentRss>http://www.woitasen.com.ar/2012/03/my-two-commits-to-the-linux-kernel/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Script to print WWIDs of SCSI devices</title>
		<link>http://www.woitasen.com.ar/2012/01/script-to-print-wwids-of-scsi-devices/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=script-to-print-wwids-of-scsi-devices</link>
		<comments>http://www.woitasen.com.ar/2012/01/script-to-print-wwids-of-scsi-devices/#comments</comments>
		<pubDate>Thu, 26 Jan 2012 20:34:36 +0000</pubDate>
		<dc:creator>Diego Woitasen</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.woitasen.com.ar/?p=166</guid>
		<description><![CDATA[I wrote this super script to print the WWIDs of SCSI devices &#160;]]></description>
		<wfw:commentRss>http://www.woitasen.com.ar/2012/01/script-to-print-wwids-of-scsi-devices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>About the &#8220;_s&#8221; in the LDAP library (Python and others)</title>
		<link>http://www.woitasen.com.ar/2012/01/about-the-_s-in-the-ldap-library-python-and-others/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=about-the-_s-in-the-ldap-library-python-and-others</link>
		<comments>http://www.woitasen.com.ar/2012/01/about-the-_s-in-the-ldap-library-python-and-others/#comments</comments>
		<pubDate>Sun, 15 Jan 2012 01:14:11 +0000</pubDate>
		<dc:creator>Diego Woitasen</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.woitasen.com.ar/?p=164</guid>
		<description><![CDATA[If you have coded using LDAP libraries you should have notice about functions that ends with and without &#8220;_s&#8221;. That &#8220;s&#8221; means synchronous: the functions return when the operation is finished. The functions without the &#8220;s&#8221; are asynchronous: the functions return instantaneously without waiting for the end of the operation. The idea behind async functions is <a href='http://www.woitasen.com.ar/2012/01/about-the-_s-in-the-ldap-library-python-and-others/' class='excerpt-more'>[...]</a>]]></description>
		<wfw:commentRss>http://www.woitasen.com.ar/2012/01/about-the-_s-in-the-ldap-library-python-and-others/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Source routing with Squid</title>
		<link>http://www.woitasen.com.ar/2012/01/source-routing-with-squid/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=source-routing-with-squid</link>
		<comments>http://www.woitasen.com.ar/2012/01/source-routing-with-squid/#comments</comments>
		<pubDate>Mon, 09 Jan 2012 02:18:39 +0000</pubDate>
		<dc:creator>Diego Woitasen</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[Services]]></category>
		<category><![CDATA[iproute]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[routing]]></category>
		<category><![CDATA[squid]]></category>

		<guid isPermaLink="false">http://www.woitasen.com.ar/?p=159</guid>
		<description><![CDATA[This is a small HOWTO about doing source routing with Squid and Linux. With Squid you can specifiy the outgoing IP address using ACLs. That means that you can select the outgoing IP using the information inside HTTP messages, thing that you can&#8217;t do with a firewall. The syntax is simple: acl somedomain dstdomain somedomain.com <a href='http://www.woitasen.com.ar/2012/01/source-routing-with-squid/' class='excerpt-more'>[...]</a>]]></description>
		<wfw:commentRss>http://www.woitasen.com.ar/2012/01/source-routing-with-squid/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to install 389 Directory Server in Debian</title>
		<link>http://www.woitasen.com.ar/2011/11/how-to-install-389-directory-server-in-debian/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=how-to-install-389-directory-server-in-debian</link>
		<comments>http://www.woitasen.com.ar/2011/11/how-to-install-389-directory-server-in-debian/#comments</comments>
		<pubDate>Wed, 09 Nov 2011 21:03:09 +0000</pubDate>
		<dc:creator>Diego Woitasen</dc:creator>
				<category><![CDATA[Services]]></category>
		<category><![CDATA[389 directory server]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[ldap]]></category>
		<category><![CDATA[redhat directory server]]></category>
		<category><![CDATA[squeeze]]></category>

		<guid isPermaLink="false">http://www.woitasen.com.ar/?p=150</guid>
		<description><![CDATA[I documented the procedure in the 389DS Wiki: http://directory.fedoraproject.org/wiki/Howto:DebianPackages Tested on Debian Squeeze, current status: works for me Feedback is welcome!]]></description>
		<wfw:commentRss>http://www.woitasen.com.ar/2011/11/how-to-install-389-directory-server-in-debian/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Apache Directory Studio</title>
		<link>http://www.woitasen.com.ar/2011/11/apache-directory-studio/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=apache-directory-studio</link>
		<comments>http://www.woitasen.com.ar/2011/11/apache-directory-studio/#comments</comments>
		<pubDate>Tue, 01 Nov 2011 20:51:49 +0000</pubDate>
		<dc:creator>Diego Woitasen</dc:creator>
				<category><![CDATA[Services]]></category>
		<category><![CDATA[apache directory studio]]></category>
		<category><![CDATA[ldap]]></category>
		<category><![CDATA[ldap browser]]></category>
		<category><![CDATA[ldap client]]></category>

		<guid isPermaLink="false">http://www.woitasen.com.ar/?p=146</guid>
		<description><![CDATA[One of the tools that I&#8217;ve looked for in Linux was a good graphical LDAP client. I had ADS (Apache Directory Studio) in my list but I&#8217;ve never tried until today. It&#8217;s very complete and the interface is very good. It&#8217;s a pure LDAP client, it&#8217;s not a frontend for LDAP user administration or things <a href='http://www.woitasen.com.ar/2011/11/apache-directory-studio/' class='excerpt-more'>[...]</a>]]></description>
		<wfw:commentRss>http://www.woitasen.com.ar/2011/11/apache-directory-studio/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Auditing user actions after sudo</title>
		<link>http://www.woitasen.com.ar/2011/11/auditing-user-actions-after-sudo/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=auditing-user-actions-after-sudo</link>
		<comments>http://www.woitasen.com.ar/2011/11/auditing-user-actions-after-sudo/#comments</comments>
		<pubDate>Tue, 01 Nov 2011 01:45:08 +0000</pubDate>
		<dc:creator>Diego Woitasen</dc:creator>
				<category><![CDATA[System Administration]]></category>
		<category><![CDATA[audit]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[login]]></category>
		<category><![CDATA[pam]]></category>
		<category><![CDATA[pam_script]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[su]]></category>
		<category><![CDATA[sudo]]></category>

		<guid isPermaLink="false">http://www.woitasen.com.ar/?p=140</guid>
		<description><![CDATA[It&#8217;s a very well known issue that if you award sudo to an user and he/she executes a shell, you lost what the user does. I receive a requirement in a project to find out how to have a registry of the user actions after sudo. Linux offers a way to this, using the &#8220;Audit&#8221; <a href='http://www.woitasen.com.ar/2011/11/auditing-user-actions-after-sudo/' class='excerpt-more'>[...]</a>]]></description>
		<wfw:commentRss>http://www.woitasen.com.ar/2011/11/auditing-user-actions-after-sudo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IP FQDN HOSTNAME!!!</title>
		<link>http://www.woitasen.com.ar/2011/10/132/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=132</link>
		<comments>http://www.woitasen.com.ar/2011/10/132/#comments</comments>
		<pubDate>Tue, 11 Oct 2011 14:05:06 +0000</pubDate>
		<dc:creator>Diego Woitasen</dc:creator>
				<category><![CDATA[System Administration]]></category>

		<guid isPermaLink="false">http://www.woitasen.com.ar/?p=132</guid>
		<description><![CDATA[There are a lot of people that don&#8217;t understand how to configure /etc/hosts. There are services that complains about that, for example: Zimbra, Apache, Squid, etc. The right syntax of every entry in /etc/hosts file MUST be: For example: 1.2.3.4 myserver.example.com myserver If you write that wrong, there are some functions of libc that don&#8217;t <a href='http://www.woitasen.com.ar/2011/10/132/' class='excerpt-more'>[...]</a>]]></description>
		<wfw:commentRss>http://www.woitasen.com.ar/2011/10/132/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Zimbra archiving with compression, the numbers</title>
		<link>http://www.woitasen.com.ar/2011/10/zimbra-archiving-with-compression-the-numbers/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=zimbra-archiving-with-compression-the-numbers</link>
		<comments>http://www.woitasen.com.ar/2011/10/zimbra-archiving-with-compression-the-numbers/#comments</comments>
		<pubDate>Thu, 06 Oct 2011 15:28:01 +0000</pubDate>
		<dc:creator>Diego Woitasen</dc:creator>
				<category><![CDATA[Services]]></category>
		<category><![CDATA[System Administration]]></category>
		<category><![CDATA[archiving]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[mail]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[zimbra]]></category>

		<guid isPermaLink="false">http://www.woitasen.com.ar/?p=128</guid>
		<description><![CDATA[Today I calculated the space saved in one of the stores thanks to archiving+compression in one of the Zimbra servers that I&#8217;ve installed more than one ayer ago. The archiving volume has 273GB of email that uses 159GB of disk after compression. That&#8217;s 42% of saving. I&#8217;m using a script to archive mails in the <a href='http://www.woitasen.com.ar/2011/10/zimbra-archiving-with-compression-the-numbers/' class='excerpt-more'>[...]</a>]]></description>
		<wfw:commentRss>http://www.woitasen.com.ar/2011/10/zimbra-archiving-with-compression-the-numbers/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

