<?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>Konrad Żak's web space &#187; Linux</title>
	<atom:link href="http://konradzak.com/category/it/linux/feed/" rel="self" type="application/rss+xml" />
	<link>http://konradzak.com</link>
	<description>both personal and work related informations</description>
	<lastBuildDate>Tue, 28 Oct 2008 10:41:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Squid on custom port and SELinux &#8211; &#8220;Cannot open HTTP Port&#8221; problem</title>
		<link>http://konradzak.com/it/linux/squid-on-custom-port-and-selinux-cannot-open-http-port-problem/</link>
		<comments>http://konradzak.com/it/linux/squid-on-custom-port-and-selinux-cannot-open-http-port-problem/#comments</comments>
		<pubDate>Thu, 08 May 2008 09:56:15 +0000</pubDate>
		<dc:creator>Konrad Żak</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://konradzak.com/?p=154</guid>
		<description><![CDATA[If you&#8217;d like to run squid on custom port i.e. 8080 with SELinux in enforcing state, be sure to set squid_disable_trans to on &#8211; it&#8217;s default set to off. Otherwise, squid will not be able to bind to port with &#8220;Cannot open HTTP Port&#8221; error.
[root@ulisses ~]# getsebool -a &#124; grep squid_disable_trans
squid_disable_trans --> off
[root@ulisses ~]# setsebool [...]]]></description>
		<wfw:commentRss>http://konradzak.com/it/linux/squid-on-custom-port-and-selinux-cannot-open-http-port-problem/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Simple service watchdog</title>
		<link>http://konradzak.com/it/linux/simple-service-watchdog/</link>
		<comments>http://konradzak.com/it/linux/simple-service-watchdog/#comments</comments>
		<pubDate>Tue, 15 Jan 2008 14:07:38 +0000</pubDate>
		<dc:creator>Konrad Żak</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://konradzak.com/uncategorized/simple-service-watchdog/</guid>
		<description><![CDATA[Recently I got some trouble with saslauthd unexpectly dying. Despite strong will to discover cause of problems I needed badly some kind of watchdog bringing dead service back to life. Yes, there is still inittab respawn at your disposal, but it has some major drawbacks.
Consider this simple shell script:
#!/bin/sh
# give the $4 service $1 seconds [...]]]></description>
		<wfw:commentRss>http://konradzak.com/it/linux/simple-service-watchdog/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>SQLgrey Postfix greylisting service little fix</title>
		<link>http://konradzak.com/it/postfix/sqlgrey-postfix-greylisting-service-little-fix/</link>
		<comments>http://konradzak.com/it/postfix/sqlgrey-postfix-greylisting-service-little-fix/#comments</comments>
		<pubDate>Mon, 29 Jan 2007 18:37:24 +0000</pubDate>
		<dc:creator>Konrad Żak</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Postfix]]></category>

		<guid isPermaLink="false">http://konradzak.com/uncategorized/sqlgrey-postfix-greylisting-service-little-fix/</guid>
		<description><![CDATA[As SQLgrey 1.6.7 init script is always reporting success neverthless of real status of starting/stoping service. You&#8217;ll find patch solving this behavior attached.
Patch of sqlgrey-1.6.7 init file (init/sqlgrey in source distro)
]]></description>
		<wfw:commentRss>http://konradzak.com/it/postfix/sqlgrey-postfix-greylisting-service-little-fix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
