similar to: oplocks and mixed unix/smb file access

aideen@persimmon.co.uk wrote: > > Hi, > > We've got some Java projects that are being developed on both Unix and > NT and we're struggling with JBuilder 2.0 and its "File has been > externally updated, reload buffers?" messages. Has anyone found a fix? > Is it a bug in JBuilder? i.e should I save my hair and not spend any > more time investigating/trying

All, Here is the output of smbstatus after I have opened up the file on the PC: /usr/local/samba/bin [184] ./smbstatus Samba version 1.9.18p10 Service uid gid pid machine ---------------------------------------------- dave dave staff 972 syscon2 (137.51.150.63) Tue Dec 15 15:43:27 1998 No locked files Share mode memory usage (bytes): 1048464(99%)

Greetings All, I have tried everything I can think of and can not seem to stop the PC from cacheing a local copy of a file retrieved over a samba share. I have tried oplocks = false and also setting veto oplocks = /*.txt/ Whatever I try the PC still shows me the old version of a file after I modify it on the unix side. If anyone can see anything wrong with my smb.conf file please let me know.

Greetings All, I am trying to turn off oplocks and can not seem to figure out which parameters to use. I have tried setting oplocks = False in both the global section and in my share section. I have also tried setting veto oplock files = /*.txt/ in my share section. Each time I try this and restart the smbd program I get the same behaviour on the PC side. The file is cached on the PC side (I

hello, until last week I had 2.2.1a in place, which, except some fox (dos) share which needed 'veto oplocks files', worked ok; upgraded to 2.2.3a with the same smb.conf (details below) and suddenly I started having oplocks problems (not on the dos share, that one is ok) with almost every other share (those hold windows files: programs, *doc, *xls): [2002/02/19 12:31:28, 0]

Hi, I have serious problems to manage oplocks on Samba Share. Some clients have been installed Office 2000 SP3 + Windows XP SP1; they aren't working because Word+ Excel save files only read-only when reopen the file and I try to save. If use Wordpad or something else, It'll works fine. on the smb.conf: level2 oplocks = yes oplocks = yes veto oplock files =

I noticed that the Release Notes for Samba 3.0.21 say that the oplock implementation has been rewritten. And we seem to be having problems with some .exe files we are sharing out as read-only shares. The shares now only allow the first person to open the executable and run it. Other users time out with a memory address error. Do I need to specify some new oplock option for these shares now? I

Dear all, We have samba-3.0.11 on freebsd 5.4 as file/print server it works perfect, but if two users open the same file together the second still can write to the file it cannot be allowed in you situation. But the other server with freebsd 4.11 doesn't have this problem perfectly do write lock on open file, so may be it's freebsd 5.x problem? I can't find what's wrong,

Hello all, I have a foxpro application that someone else wrote that I am trying to support to XP clients. I have done what I can to disable oplocks on my end and they are all service pack 2 XP Professional workstations. in my [global] section I have the following: # http://www.drouillard.ca/Tips&Tricks/Samba/Oplocks.htm lock spin time = 15 lock spin count = 30 kernel oplocks =

1) Does "strict locking = no" negate "kernel oplocks = yes" ? 2) What's the difference between the two? 3) What a good way to test if a file got a lock seen from the linux side and the windows side? 4) If a file has a lock, does that mean you can still open the file in linux or in windows, but can't write to it? Any clarification between the two would be helpful.

Here is Oplocks Usage Recommendations Whitepaper for Samba on HP-UX (originally was written for CIFS/9000 Server on HP-UX). Note that the intended audience is/are HP-UX customers who have questions and concerns about when to configure oplocks. This is intended as a rudimentry guide to help avoid the most obvious oplock pitfalls. Hopefully the plain text alignments hold up well for most editors.

Hi Volker Thanks for your quick answer. Now I upgraded samba to 3.0.32 but this didn't fix the problem. We have three other servers with freebsd and samba in our environment. I also compared the settings and the only difference I can find is that on this server with these problems is the acl support disabled because we had some problems with it. May this acl support have something to do

Hi guys I have that config in global section of smb.conf: kernel oplocks = No locking = Yes oplocks = No level2 oplocks = No strict locking = No veto oplock files = /*.pdf/*.PST/*.pst/*.doc/*.xls/*.docx/*.mdb/*.MDB/*.dbf/*.DBF/*.ppt/*.xlsx/ I restart the service and I am still getting that log: [2010/12/23 11:16:24.105806, 5]

Hi Everybody, I seem to still be having problems with the caching of files on the PC. I have tried to set the oplocks = false variable in the smb.conf file but that has not seemed to help. Here is what I do to see the problem Open a file on the PC, the close it. Go to a unix machine and modify the file. Go back to the PC and re-open the file. I will get the old copy of the file for a few

Hello, I am running a Samba 3.6.3 fileserver on Ubuntu 12.04. It is joined to a Samba 4 Active Directory domain for user authentication. I have shares configured as follows: [MyShare] path = /path/to/MyShare browseable = yes public = yes guest ok = yes writable = yes printable = no create mode = 0664 force create mode = 0660 directory mode = 0775 force directory mode

In my smb.conf file, I've got the following section: [homes] comment = Home Directories valid users = %S guest ok = no read only = No create mask = 0640 directory mask = 0750 browseable = No veto oplock files = /*.mdb/*.MDB/*.pst/*.PST/ And yet, in the syslog, I'm still getting these... Mar 10 10:22:34 riffraff

Hi We've here some problems with Samba on a freeBSD-Server. FreeBSD 6.2-RELEASE Samba Version 3.0.25a The problem is about locking of open files. For example when a user A opens a excel-sheet and a user B also opens the same file, user B won't only open this file as read-only. We moved from a Windows Server to a freebsd based one about 2 weeks ago and we also had some problems with dbs

Hi Folks First time poster here.. I have a Samba 3.4.7 ( will upgrade soon ) in a workgroup enviroment, This server has a share containing various Access DB backends.. Wondering about the .ldb lock files that the client front-ends produce.. and if the oplocks and veto options are still current ? as various combinations i have tried don't seem to work.. Would be keen to hear how others

On Tue, Jan 24, 2023 at 08:29:17PM +0300, Michael Tokarev via samba wrote: >24.01.2023 20:22, Ralph Boehme via samba wrote: >>What Samba version is this? This: >> >>>LEASE() >> >>... looks broken: the handle oplock/lease state claims to be a >>lease, which means the client didn't request an oplock but a lease >>which should not have happened in

Hello, Iam facing a problem in locking of files across samba shares. We have samba 3.0.10 running on Solaris 9 with the smb.conf as follows. # Global parameters [global] workgroup = NMUINT netbios name = NMUINTFS interfaces = <IP> bind interfaces only = Yes security = DOMAIN password server = XXX.XXX.XXX.XXX log level = 1 ldap