<?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>Solutions Log &#187; snv</title>
	<atom:link href="http://solutions.unixsherpa.com/tag/snv/feed/" rel="self" type="application/rss+xml" />
	<link>http://solutions.unixsherpa.com</link>
	<description>by Dan Reiland</description>
	<lastBuildDate>Fri, 16 Apr 2010 20:28:57 +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>Enable opportunistic locking with Sun SMB service on Solaris Nevada</title>
		<link>http://solutions.unixsherpa.com/2009/07/08/enable-opportunistic-locking-with-sun-smb-service-on-solaris-nevada/</link>
		<comments>http://solutions.unixsherpa.com/2009/07/08/enable-opportunistic-locking-with-sun-smb-service-on-solaris-nevada/#comments</comments>
		<pubDate>Wed, 08 Jul 2009 23:13:01 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Solaris]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[cifs]]></category>
		<category><![CDATA[nevada]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[snv]]></category>

		<guid isPermaLink="false">http://solutions.unixsherpa.com/?p=80</guid>
		<description><![CDATA[The primary reason for implementing this is performance. From Microsoft: Opportunistic locking (oplock) is a mechanism that allows a server to tell a client process that a requested file is only being used by that process. The client can safely do read-ahead and write-behind as well as local caching, knowing that the file will not [...]]]></description>
			<content:encoded><![CDATA[<p>The primary reason for implementing this is performance.</p>
<p>From Microsoft:</p>
<blockquote><p>
Opportunistic locking (oplock) is a mechanism that allows a server to tell a client process that a requested file is only being used by that process. The client can safely do read-ahead and write-behind as well as local caching, knowing that the file will not be accessed or changed in any way by another process while the opportunistic lock is in effect. The server notifies the client when a second process attempts to open or modify the locked file.<br />
Reference: <a href="http://msdn.microsoft.com/en-us/library/dd327670.aspx">http://msdn.microsoft.com/en-us/library/dd327670.aspx</a>
</p></blockquote>
<p>The snippet:</p>
<pre>
svccfg -s smb/server setprop smbd/oplock_enable=boolean: true
</pre>
]]></content:encoded>
			<wfw:commentRss>http://solutions.unixsherpa.com/2009/07/08/enable-opportunistic-locking-with-sun-smb-service-on-solaris-nevada/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced)
Database Caching 1/13 queries in 0.028 seconds using disk
Object Caching 311/320 objects using disk

Served from: solutions.unixsherpa.com @ 2010-09-10 01:18:51 -->