<?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>Blog O Stu &#187; vsftpd</title>
	<atom:link href="http://bovitron.com/blogostu/tag/vsftpd/feed/" rel="self" type="application/rss+xml" />
	<link>http://bovitron.com/blogostu</link>
	<description>STUpidity and other STUff</description>
	<lastBuildDate>Wed, 01 Feb 2012 10:43:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>vsftpd and the dreaded &#8220;500 OOPS: could not bind listening IPv4 socket&#8221;</title>
		<link>http://bovitron.com/blogostu/2010/01/18/vsftpd-and-the-dreaded-500-oops-could-not-bind-listening-ipv4-socket/</link>
		<comments>http://bovitron.com/blogostu/2010/01/18/vsftpd-and-the-dreaded-500-oops-could-not-bind-listening-ipv4-socket/#comments</comments>
		<pubDate>Mon, 18 Jan 2010 15:52:56 +0000</pubDate>
		<dc:creator>Stu</dc:creator>
				<category><![CDATA[computer stuff]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Slackware]]></category>
		<category><![CDATA[500]]></category>
		<category><![CDATA[ipv4]]></category>
		<category><![CDATA[oops]]></category>
		<category><![CDATA[socket]]></category>
		<category><![CDATA[vsftpd]]></category>

		<guid isPermaLink="false">http://bovitron.com/blogostu/?p=7</guid>
		<description><![CDATA[During a server move from Slackware 13.0 to Slackware 64 13.0, I encountered the dreaded &#8220;500 OOPS: could not bind listening IPv4 socket&#8221; error from vsftpd. As you may know, Slackware runs vsftpd (and some other services) from inetd: the internet &#8220;super-server.&#8221; After a bit of searching and some piddling around, I found a very [...]]]></description>
			<content:encoded><![CDATA[<p>During a server move from Slackware 13.0 to Slackware 64 13.0, I encountered the dreaded &#8220;500 OOPS: could not bind listening IPv4 socket&#8221; error from vsftpd.</p>
<p>As you may know, Slackware runs vsftpd (and some other services) from inetd: the internet &#8220;super-server.&#8221; After a bit of searching and some piddling around, I found a very simple solution: add the following to <strong>/etc/vsftpd.conf</strong></p>
<p><strong>listen=NO</strong></p>
<p>FYI, I actually just uncommented the line <strong>listen=YES</strong> and changed <strong>YES</strong> to <strong>NO</strong>.</p>
<p>I post this in hopes that next time I encounter this issue, I&#8217;ll have the answer <em>stored</em>!</p>
<p>Happy &#8216;putering!<br />
Stu&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://bovitron.com/blogostu/2010/01/18/vsftpd-and-the-dreaded-500-oops-could-not-bind-listening-ipv4-socket/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

