Re: [Samba] incorrect shared access to the file - samba oplock bug?
This is a discussion on Re: [Samba] incorrect shared access to the file - samba oplock bug? within the Samba forums, part of the Networking and Network Related category; On Thu, Sep 15, 2005 at 03:31:49PM +0400, Jablonovsky Alexander wrote: > I have tried to read a ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
09-16-2005
|
|||
|
|||
Re: [Samba] incorrect shared access to the file - samba oplock bug?
On Thu, Sep 15, 2005 at 03:31:49PM +0400, Jablonovsky Alexander wrote:
> I have tried to read a file from a Windows machine, at time this file > being written from a Linux machine with Samba (constantly reading > constantly growing file) and got a strange behavior. After reading some > number of bytes ReadFile() starts to return 0 bytes read (EOF). Seeking > and even closing/reopening the file doesn't help - only the old snapshot > of the file can be read. Touching the file from other program like > Explorer has effect - Windows refreshes the file to it's current state. oplocks - either use kernel oplocks or turn off oplock support in Samba. Also to do this correctly you need byte range lock coordination between the reading and writing app. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba 
|
Linear Mode
