<?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>Technicalities &#187; NIS</title>
	<atom:link href="http://www.sirena.org.uk/log/category/tech/the-network-information-system-aka-yellow-pages/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sirena.org.uk/log</link>
	<description>Just another random blog</description>
	<lastBuildDate>Fri, 27 Aug 2010 23:50:17 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>NIS and Network Manager in Debian etch</title>
		<link>http://www.sirena.org.uk/log/2007/03/27/nis-and-network-manager-in-debian-etch/</link>
		<comments>http://www.sirena.org.uk/log/2007/03/27/nis-and-network-manager-in-debian-etch/#comments</comments>
		<pubDate>Tue, 27 Mar 2007 21:57:30 +0000</pubDate>
		<dc:creator>Mark Brown</dc:creator>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[NIS]]></category>
		<category><![CDATA[Planet Debian]]></category>

		<guid isPermaLink="false">http://www.sirena.org.uk/log/?p=41</guid>
		<description><![CDATA[The version of NIS to be shipped with Debian 4.0 has support for Network Manager in ypbind, the program responsible for ensuring that NIS client systems can access a NIS server. Unfortunately Network Manager is targeted at client systems with dynamically assigned addresses and does not support some common network configurations, particularly static ones. When [...]]]></description>
			<content:encoded><![CDATA[<p>The version of <a href="http://www.linux-nis.org/nis/">NIS</a> to be shipped with Debian 4.0 has support for <a href="http://www.gnome.org/projects/NetworkManager/">Network Manager</a> in <a href="http://www.linux-nis.org/nis/ypbind-mt/index.html">ypbind,</a> the program responsible for ensuring that NIS client systems can access a NIS server. Unfortunately Network Manager is targeted at client systems with dynamically assigned addresses and does not support some common network configurations, particularly static ones. When Network Manager is run on a computer with such a configuration it presents misleading information to NIS, causing NIS to think that it is not connected to a network and fail to connect to a server.</p>
<p>In order to avoid these problems the version of NIS in etch disables Network Manager support by default but the configuration file with this change is not updated automatically on upgrade. To disable Network Manager support by hand edit the configuration file <tt>/etc/default/nis</tt> to add -no-dbus to YPBINDARGS:</p>
<p><code># Additional options to be given to ypbind when it is started.<br />
YPBINDARGS=-no-dbus<br />
</code></p>
<p>Uninstalling the network-manager package if it is not in use will also resolve the problem.</p>
<p>This also applies to the packages currently scheduled for release in the next version of Ubuntu (codenamed Feisty).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sirena.org.uk/log/2007/03/27/nis-and-network-manager-in-debian-etch/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
