On Fri, Oct 23, 2009 at 11:27, Ben Scott <[email protected]> wrote: > On Fri, Oct 23, 2009 at 1:09 PM, Michael B. Smith > <[email protected]> wrote: >> The "blue screen" is certainly not true with >> any recent version of Windows Server. > > Well, that's good. :) > >> When it wants to update that chunk, it requests a write-lock >> on only the piece of that area it wants to update. SMB doesn't >> support a "partial row write-lock". > > Eh? Samba implements locking of arbitrary byte ranges. Or it did > back in 2002. QuickBooks used them, which is how I encountered it. > You did have to disable oplocks for it to work; I dunno if that's an > SMB thing or a Samba thing.
I could be wrong, but I believe that the issue isn't with SAMBA vs. Windows file locking, it's more along the lines of "Outlook lies to the OS about what it's locking in the PST file, which can cause corruption". ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
