> > OpLocks were indeed causing corruption; we only turned > > them off, made no other changes, and have no more > > corruption, as I reported yesterday. Wouldn't that be > > a priority 1, "drop everything" bug? Other experience > > was confirmed by doing a Google, by 2 Samba authors, > > and by the results of our one simple change. > the oplock problem with access databases is well known...
> I don't think samba alone can fix it. > (somebody prove me wrong :) Just curious....If it is not a problem with "samba alone," what is causing it? Is it a problem with the kernel, the filesystem? Where does the other work (besides Samba) need to be done? Trey Nolen -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
