Date: Wed, 16 Jul 2003 11:30:30 +0900 From: Joel Rees <joel@alpsgiken.gr.jp> To: freebsd-questions@freebsd.org Cc: stan <stanb@panix.com> Subject: Re: Problems with Samba shared files Message-ID: <20030716112109.19F7.JOEL@alpsgiken.gr.jp> In-Reply-To: <20030715105147.87DF.JOEL@alpsgiken.gr.jp> References: <20030715001127.GB29352@teddy.fas.com> <20030715105147.87DF.JOEL@alpsgiken.gr.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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.)
--
Joel Rees, programmer, Kansai Systems Group
Altech Corporation (Alpsgiken), Osaka, Japan
http://www.alpsgiken.co.jp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030716112109.19F7.JOEL>