On 10/16/08 07:36, HUGE | Rob Terhaar wrote: > On 10/15/08 9:27 PM, "Alan M Wright" <[EMAIL PROTECTED]> wrote: >>> I still think that oplocks and solaris cifs needs to be documented better. >> I'm not sure how to interpret that statement. You think that oplocks >> are not documented well enough in general and neither is the Solaris >> CIFS service or you are looking for more information on oplocks within >> the Solaris CIFS documentation? > > Sorry, I'll explain better: > > I think that this information is extremely helpful and should be included in > release notes (or at least an informal wiki?) Information about why oplocks > are disabled, how to enable oplocks, and what are the > advantages/disadvantages of enabling oplocks is very helpful for testing and > using solaris cifs. > > If sun really wants more community involvement, then sun needs to involve > the community. ;) > > My original confusion about oplocks and solaris cifs began when I saw the > warning message "oplocks disabled" in my logs whenever the cifs server > starts. I initially thought that I had a mis-configuration, perhaps > something related to nbmand=off on my zvol? So I searched the solaris cifs > docs from sun for "oplocks" and found nothing. I then searched the genunix > wiki for oplocks, found nothing. Then I emailed the cifs list, and Janice > explained the situation to me.
Yes, that log message was really unfortunate. I had asked for it to be removed before putback, because I thought it would cause confusion, but somehow it slipped through. It has been removed. Alan [other points noted] > Solaris users should not need to email the friendly people on the cifs > mailing list in order to answer simple questions like this. _______________________________________________ cifs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
