similar to: How to Turn of oplocks in version 2?

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.

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

Greetings All, Does anyone know how to turn oplocks off? I have tried everything I can think of to disable this feature but each time the PC will cache the file. If anybody has turned this off please send me your configuration file. Here is the latest config file I have tried. Thanks for any help, David. [global] printing = sysv printcap name = /etc/printcap load printers = yes keepalive

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]

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.

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,

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

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]

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 =

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, 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 thought I had things figured out, but guess not. I have multi-user Quickbooks databases that functioned fine on a Novell server but are behaving badly on a Samba share. I have created a separate share for the Quickbook databases, users are running Win XP Pro, latest patches, and the Quickbooks application installed on the desktop. It is a multiuser version. Server is RedHat ES 3, Samba

---------- Forwarded message ---------- Date: Tue, 29 Jul 2003 19:40:48 -0400 (EDT) From: Rashkae <rashkae@tigershaunt.com> To: Marco De Vitis <starless@despammed.com> Subject: Re: [Samba] oplock problem on NTUSER.DAT Hi Marco Try to veto oplocks for that file. In the global section of your smb.conf, add the following veto oplock files = /NTUSER.DAT/ Let us know if that changes

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

Greetings All, I seem to be having a problem with files being cached, and I am 99% certain that it is not oplock related. I have set up my smb.conf file to have oplocks turned off and I think it is set up correctly. I believe this is correct because I then took that file and changed it to turn oplocks on and I did get different behaviour. With oplocks off an smbstat never shows any files being

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

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

Hi all, I had been running a Samba pdc using the standard tdbsam backend on CentOS 4.5 supporting 20+ WinXPsp2 workstations and a Win2k3 Terminal Server. This set up was running fine for arroung 18 months maybe more. The above system was built on ageing hardware that used to be a Win 2k server that died from OS corruption. Due to the expanding client needs there was good reason to replace

Hello everybody, I have 2 questions about Samba operation: First, hostnames don't work in my "hosts allow" directive, although smb.conf(5) explicitly says "You can specify the hosts by name or IP number". If I specify a client by its name, that client is not allowed access, even though the server can do reverse DNS on the client's IP. The message I get in the