similar to: No subject

Our development team has been having the following issue for quite some time and I cannot isolate the problem. I saw a similar posting in the archives but there are no replies. We are running Samba 2.0.7 on a RedHat 6.2 server and we connect to the server from Windows 2000 desktops. We are editing files through a drive mapped to a share on the server. The problem is when we save the file in the

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 there, I have just installed wine (release 20010305) and it looks to work good. I can run notepad without trouble, winecheck.pl has one bad and one critical result: 023. Checking device needed for DGA (option "UseDGA"): /dev/BAD (/dev/mem is not writable for you). - ADVICE: Use chmod as root to fix it ("man chmod"). 025. Checking availability of windows registry

Futher to my last message regarding samba being confused when a Word97 file was being saved. I have been looking at the docs and log files again and now understand that the problem is related to opportunistic locking. I also found the part of the log file that details the start of the event. Here it is: 1998/06/19 15:51:19 ukswi1000 (175.12.50.218) connect to service its as user bramsons

phl@cyways.com wrote: > > >From the Samba 2.0 beta announcement: > > 5). Cross protocol data integrity > --------------------------------- > > An open function interface has been defined to allow > "opportunistic locks" (oplocks for short) granted by Samba > to be seen by other UNIX processes. This allows complete > cross protocol (NFS and SMB) data

Thanks to Dimitry's tip I'm getting closer to run Allair's Homesite4.5 but I reached a point where I don't know how to debug the remaining problem(s). I used to get a runtime error, but with getting native stdole32.tlb this doesn't appear any more. Now I have 2 scenarios: 1.) starting with native comctl32.dll (and commctrl.dll) - the small centeres window appears (with

You wrote: | The problem that I'm having is that once a file has been opened from the | share, changes made to that file via the WWW interface are not seen by | the Win95 client, they still get the old file's contents. This is an artefact of the so-called ``opportunistic lock'' algorithm, which allows client-side caching unless another pc client attempts to edit the file. You

jiva, in some ways this question, or at least the answer, is best seen on samba@samba.anu.edu.au not just on samba-technical. i don't recieve the samba digest, so don't know if you've posted it there. so. question. by "workstation" in paragraph 4, do you mean the "workstation smb client-side cacheing, which means opportunistic locking" or do you mean "the

Hi Can anyone advise me on "kernel oplocks" in a ctdb cluster. I have a ctdb (GPFS is the parallel file system) setup that uses samba (3.5.8) for cifs and IBM CNFS for NFS. Reading the documentation on kernel oplocks it seems to me that I can export the same area via samba and NFS with "kernel oplocks = Yes" . My logic is that IBM CNFS has shared NFS locking

Debian and Samba Teams: I'm having a really weird problem with Samba 3.0Beta2+RC4 on my Debian Sarge (testing) system with Quickbooks Pro 2002 multi-user version. The version of my question is: Does anybody know what the proper global, share, and permissions settings should be to support multi-user Quickbooks on a Samba share? The Long Version: The Quickbooks data-file resides on it's

Hi! I was hoping someone had seen this problem, and might be able to help me out with it; I've tried the suggestions I found in the mailing lists and on web sites, to no avail. I'm running samba 3.0.2 on RHEL 3, and XP clients seem to occasionally have problems saving the roaming profile, resulting in error messages and the use of the local profile. The problem is when renaming

Hello everybody! I need help with a curious problem referring to Word and Samba. I've installed a network with a Samba 3.0.2 PDC and fileserver and about 8 Windows Clients ranging from w2k prof (members of the domain) to XP home. The XP Home users have an account within the domain and so can "mount" the Samba share as a local drive on their computers. All of the users are members

hi all Subject: 1) Samba server 3.0.15 with one shared sesource Security is set to SHARE, all guest users have full read/write access to the share 2) Microsoft network clients is Windows 98, Windows 2000 and Windows XP (sp2) 3) Old-age DOS program, written on Clipper (xBase), what runs on Windows 98 and on Windows XP/2k (ntvdm) 4) Large multi-user database (dbf files) on samba server

The Samba Team is pleased to announce Samba 2.0.7. This is the latest stable release of Samba. This is the version that all production Samba servers should be running for all current bug-fixes. This version has been tested against Windows 2000 and has no *known* issues with that release of Windows. It may be fetched via ftp from : ftp://ftp.samba.org/pub/samba/samba-2.0.7.tar.gz Or just follow

Goldmine seems to a compiled database application compiled in something likeClipper. Clipper applications record lock through ISAM like files (DBF). However, in Windows NT/2000/XP, Opportunistic locking is turned on by default in order to accelerate file transfer from file services. [Windows 95/98 did not Opportunisticly lock] However, opportunistic locking corrupts ISAM and ISAM like

penso che ti/ci possainteressare, soprattuto il fatto che la versione html del libro sia disponibile con il prg GRATUITAMENTE Marco Frattola (???) - Cubecom S.p.A. Via de Marini,1 3 piano Torre WTC 16149 GENOVA tel. 010 6591184 > -----Messaggio originale----- > Da: samba@samba.org [mailto:samba@samba.org] > Inviato: Nessuna > Oggetto: > > > id

Dear Alexandre, this problem of data-corruption with file based databases is not a Dataflex issue, nor is it necessarily a Samba issue. The problem basically is that when an application tells windows to write data to a file, the data is normally not written directly to the file but placed in a cache. Windows then waits till it has some free time and then proceeds to write the data to the storage

Folks, I'm trying to share an NFS-mounted volume with Samba - and something's amiss. Accessing any of the .doc files from a Win95 PC (Office 97) says "The file is already in use - make a copy?". Samba's log says: [2000/04/19 10:52:34, 3] lib/util.c:fcntl_lock(2773) fcntl lock gave errno 11 (Resource temporarily unavailable) [2000/04/19 10:52:34, 3]

I am a little bit confused about the kernel support for oplocks. man page of smb.conf: ---------------- For UNIXs that support kernel based oplocks (currently only IRIX but hopefully also Linux and FreeBSD soon) this parameter allows the use of them to be turned on or off. This parameter defaults to "On" on systems that have the support, and "off" on systems that don't.

Giulio Orsero wrote: > I've used > oplocks = no > for a long time now, because of the famous "oplock_break" error, but I > decided to give 2.0.7 a try. > [ snip ..] > > - the server is linux 2.2.14/samba2.0.7; it's not the server where I > used to made oplock_break tests. It's another one on another lan. It's > used almost exclusively to store