similar to: Problems with "locking" files with SAMBA 2.05a on Linux

Hi... I've been running samba 3.0 for quite some time now (Debian's stable version, currently 3.0.14) and I've had no problems. That's probably been because all my clients were Windows XP boxes. I've now moved several users to Linux (Ubuntu Breezy) as their desktop and I've noticed there seems to be a problem in accessing files across the platforms. If a Linux box

I have the same problem as described below for a while. samba 3.0.23c-2 under Fedora 6 clients Win XP and Fedora 6 app. OpenOffice 2.1 / 2.0.4 will there be any progress ? thanx -- Kristian Lauritsen Laser Product Manager PicoQuant GmbH phone: +49 30 6392 6563 http://www.picoquant.com On Mon, Oct 31, 2005 at 09:41:04AM +0000, Phill Gillespie wrote: > Hi... > > I've been

Hello! I've got into problems with simultaneous access to files on samba server. Two (or more) people from different computers may open the same file and may independently change it (with openoffice, for example). Certainly, this is not the expected behavior. If the file is shared on windows machine, when the first user opens it, he gots RW permission, while the next one(s) may open this

Hi! Is it possible to introduce an implicit server-side file locking mechanism in samba(3.2.5), so if one opens a shared file for writing, then a new user won't be able to open it for writing, but only read-only. Currently the following options are in the config file: # testparm -v |fgrep -i lock [...] kernel oplocks = Yes lock spin time = 200 oplock break wait

I've a situation where file locking does not seem to functioning. I have the following entries in my smb.conf file: *** /etc/samba/smb.conf *** linux # testparm -v | grep lock Load smb config files from /etc/samba/smb.conf <snip> Warning: Service printers defines a print command, but print command parameter is ignored when using CUPS libraries. Server role: ROLE_DOMAIN_PDC Press enter

Hi, I have a Solaris 10 server exporting UFS directories using built-in NFS. I've built Samba 3.0.20b from OpenPKG (www.openpkg.org). I have a Solaris 10 (x86) client mounting the NFS share and opening OpenDocument files using StarOffice 8 (SO8, aka OO2.0). I also have a Windows 2003 Terminal Server mounting the Samba share and opening documents with SO8. This is a temporary development

Hi folks, I have an issue at a weird confluence of macOS Mojave's "nsmb" client, Adobe Lightroom and Photoshop, and Samba 4.7.6-Ubuntu. Since I don't have much control over Apple or Adobe software, I'm hoping there's some smb.conf magic (or other sage advice) that might help me out of this jam. For reference, Samba is configured for SMB2-only access (i.e. durable file

hello, i have a question concerning the locking feature of samba (both 2.2.8 and 3.0.0) that i haven't found answered in the documentation. at this point i am not sure, whether it's a bug in samba, the client applications or simply a misunderstanding of the locking feature itself on my part - at any rate it's a pressing problem, as my clients are losing both their data as well as

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

We are having some problems in our company's test group that did not exist when our Clearcase 2003.06 server existed on a Solaris 8 machine. Now we are running on RHEL 5.2 with Clearcase 7.0.1.3 with Samba 3.0.28 (despite the fact that IBM has only blessed up to 3.0.24) and running into some file locking issues with some scripts our test group runs. I am hoping that someone might have some

> *phew*! At least it's not a regression by the patches for bug 12005. Hi Ralph, Looking back through the changelogs suggests to me that it's been around a long time.... I did however find it odd that even after disabling the 3rd host, stopping ctdb everywhere and removing *all* the db files (including persistent) I still could reproduce on 4.4.5. > > Can you try to reproduce

Hi, I'm having some trouble with locking between GNU/Linux and Microsoft Windows. I wrote some Clipper code that run's on GNU/Linux and Microsoft Windows (compiled to different binaries ofcourse) that tries to lock a file on a Samba share. Between Microsoft Windows clients there is no problem. The locking works as expected. If one client does an EXCLUSIVE lock, the other's can't

Hi there, I am facing some file locking problem with samba. Below are the environment : OS : Fedora Core 1 Samba version : 3.0.0-15 I have used security = share, oplocks =no, level2 oplocks=no, locking = yes, strict locking = yes. The detail of the smb.conf can be provided. The situation is like this : When I use openoffice (in a windows 2000 server machine) to access the file in the share

I am responding to your post, listed below. I am having the same problem with GoldMine which I believe is written in much the same way as most clipper based applications. Did you ever resolve the issue? I just posted to the newsgroup but did not hear back yet. I pormise to post a summary should an answer show up. I'm running 2.2.1a and will soon move to 2.2.2 to avoid oplock problem.

Hi all! I am using Debian Sarge with Samba version 3.0.14a-Debian and experience a locking problem: the program is a linux port of a Clipper program compiled with xHarbour (www.xharbour.org). It uses byte-range-locking to lock a record of a dbf database. If I mount the server directory over an smbmount and start 2 clients on the server accessing the server directory over the smbmount, the

Hello, I created the following samba share but for some reason samba is not locking the files open by other users. For example user dave open a file in the share and user slav does not get the notification that opened file is already being used by another user. I even added the locking options to the global but no luck. [share] comment = Main share path = /share guest ok = no writable = yes

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, at office, we have very strange problems with file locking. At first, I have to say that we have many different flavours of Windows running here as clients, it reaches from Windows 98 up to Windows XP Home Edition/Professional Edition. The following problem mainly exists with software like AutoCAD (LT 95/2000, 2000, 2003, 2005) and

Hello.. File server freebsd 6.2-STABLE + samba-3.0.25a + ldap + acls Problem: I've a situation where file locking does not seem to be functioning as expected, in that more than one user can open and write to a file without any notifications being displayed about the file already being opened by another user. I have two Windows XP clients accessing the same shared file, user1 has the file

Hi Lan with S4 and built-in file server for Windows clients. nfs for Linux clients. We are using LibreOffice to share documents and file locking works fine. The first guy to open the doc gets the lock and a message is displayed on other clients (windows or Linux) that the file is open. Fine Some users must however use Word 2010 to edit documents. Then file locking doesn't work: anyone

Hi. First of all, I will probably post this question several places, at least here, on the ubuntu forums, and perhaps OpenOffice forums. It is a problem that I'm not sure if really is samba related, Openoffice related or perhaps even OS related. As stated in the heading, it's about file locking, so many apps come into play. I work at a school where we teachers use mainly Ubuntu Hardy and