On Wed, Jul 16, 2003 at 11:30:30AM +0900, Joel Rees wrote:
> > Hmm. I would either think it a bug for Samba to be unable to tell
> > MSWindows that it had a file open for read, or a rather advanced
> > technique for Samba to be able to understand from simply mounting the
> > share as read-only that it could let MSWindows forego a lock on a
> > multiply opened file.
> > 
> > Mayb I'm just confused.
> Confused, yes, the man is confused! 
> I guess I should have visited 
>      http://www.samba.org  and
>      http://www.oreilly.com/catalog/samba/chapter/book/ch05_05.html
> and a few other places before I started dissing MSWindows. Now I know
> about oplocks, I can diss MSW with real meaning. What were they thinking?
> But that doesn't help anyone. 
> Stan, check your smb.conf and your samba logs. That should get you
> headed in the right direction.
> (Hopefully, your problem has nothing to do with opportunistic locking.)
Thanks for the pointers!

"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
                                                -- Benjamin Franklin
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to