Volker, yes this "trick" worked for the current problems but agreed that it is not a long term solution to the "locking" problem. Thanks, Bob --bs
On Tue, 2010-08-24 at 07:04 +0200, Volker Lendecke wrote: > On Mon, Aug 23, 2010 at 11:34:21PM -0400, Robert W. Smith wrote: > > OK, so far I now understand that this is _NOT_ a general login issue > > _NOR_ is it a MS credentials file issue either. This appears to be a > > general locking issue in Samba and Linux. Here is a snippet of my > > workstation log with another application that now no longer runs. The > > SMB network transactions are the same as are the results for the user > > (me, Quicken will no longer start and I am about to be hit with a late > > charge $( > > > > Note the delay between the linux_set_kernel_oplock failure and the > > reporting of the SMB error NT_STATUS_FILE_LOCK_CONFLICT. > > To avoid the issue, try "kernel oplocks = no". This does not > really solve the issue, but might help you over the current > problems. > > Volker -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
