[Samba] Self-locking files...

[Joel Hammer]

Try getting rid of oplocks.
Joel

On Wed, Jan 22, 2003 at 12:14:55AM +0100, C. Cau wrote:
> Hi,
> 
> I've set up a samba server (2.2.7) on a Mandrake 9 (2.4.16xxx on X86); 
> everything works fine, except a little recurring problem:
> 
> *very* often, clients are forbidden to save the document(s) they've open 
> ("locked file"); it's enough to modify one char of the filename and the save 
> goes fine, of course with another name...
> 
> I verified the problem, and also verified that the "locked" file is definitely 
> *not* opened by somebody else. Self-locking? :-)
> 
> Thus it seems that samba identifies the document as locked, even though the 
> client trying to save is the one who opened that file (and the only one with 
> that document open).
> 
> Any suggestions about what to check next?
> 
> Thank you in advance
> 
> 
> Corrado
> 
> 
> PS: more info below:
> 
> - SERVER: samba server v 2.2.7 (non-A) on Mdk9, fully up-to-date.
> 
> - SHARE: security=user (fake Linux accounts; no security problems found); 
> browseable=no; oplocks set; wide links disabled; no guests.
> 
> - LAN: network et al (apparently) working fine
> 
> - CLIENTS: all XP pro SP1 (strange, but none of the XP problems in the FAQ's 
> surfaced)
> 
> - LAN: network et al (apparently) perfectly fine
> 
> - DOCS: the files showing the problems are WinWord or Excel documents, opened 
> by Office XP clients.
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba