In order to deal with bizarre MS Office junk, it looks like I may have to disable oplocks on my samba server. What kinds of problems, if any could arise from my having disabled the oplocks? Alex Laslavic Havertys Tech Services
> In order to deal with bizarre MS Office junk, it looks like I may have > to disable oplocks on my samba server.I feel your pain. You *CAN* just oplock veto all M$ Office files instead.> What kinds of problems, if any could arise from my having disabled > the oplocks?Just lower performance. Oplocks are "OPportunistic LOCKS", which provide for client-side caching to be performed safely. No oplocks, no caching. What I always wonder though is whether or not these oplock problems plague Windows NT/2000 file servers as well, or if it's just an achilles heel within Samba. =MB=
> -----Original Message----- > From: Jeremy Allison [mailto:jra@samba.org]> Yes they plague Windows fileservers as well. Search in MSDN for > knowledge base articles relating to turning off oplocks in > data-critical situations (ie. when you care about files not > being corrupted :-).I ended up doing this on one of our NT 4.0 servers to keep Peachtree Accounting happy. The real bummer is that you can't veto oplocks for specific files or shares under NT like you can with Samba -- they're either all on, or all off.