<?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>Running UNIX &#187; mount point</title>
	<atom:link href="http://www.runningunix.com/tag/mount-point/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.runningunix.com</link>
	<description>UNIX/Solaris tips, tricks, and advice</description>
	<lastBuildDate>Mon, 01 Aug 2011 17:37:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Solaris 10 mount point permissions are important</title>
		<link>http://www.runningunix.com/2008/05/solaris-10-mount-point-permissions-are-important/</link>
		<comments>http://www.runningunix.com/2008/05/solaris-10-mount-point-permissions-are-important/#comments</comments>
		<pubDate>Tue, 13 May 2008 22:44:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Solaris]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[mount point]]></category>
		<category><![CDATA[permissions]]></category>
		<category><![CDATA[solaris 10]]></category>

		<guid isPermaLink="false">http://www.cybersand.com/blog/?p=9</guid>
		<description><![CDATA[rm: cannot determine if this is an ancestor of the current working directory This is caused by an underlying mount point permission that is too strict (700). You can change the permissions on the mount point without unmounting the volume by using lofs creatively: #create temp directory server1&#62; mkdir -m 755 /fix-mnt  # mount the [...]]]></description>
			<content:encoded><![CDATA[<p>rm: cannot determine if this is an ancestor of the current working directory</p>
<p>This is caused by an underlying mount point permission that is too strict (700). You can change the permissions on the mount point without unmounting the volume by using lofs creatively:</p>
<p>#create temp directory</p>
<blockquote><p>server1&gt; mkdir -m 755 /fix-mnt </p></blockquote>
<p># mount the directory which <strong>contains</strong> the mount point, not the mount point itself, but its parent directory.</p>
<blockquote><p>server1&gt; mount -F lofs -o nosub /users/zones/server1-z3/root/users/  /fix-mnt<br />
server1&gt; ls -ld /fix-mnt/mountpoint        #confirms the permssions are not 775<br />
server1&gt; chmod 775 /fix-mnt/mountpoint<br />
server1&gt; umount /fix-mnt<br />
server1&gt; rmdir /fix-mnt</p></blockquote>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.runningunix.com%2F2008%2F05%2Fsolaris-10-mount-point-permissions-are-important%2F&amp;title=Solaris%2010%20mount%20point%20permissions%20are%20important" id="wpa2a_2"><img src="http://www.runningunix.com/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.runningunix.com/2008/05/solaris-10-mount-point-permissions-are-important/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

