On Sat, 02 Nov 2002, Carlos A Silva wrote: > Hi, I have Linux Kernel 2.4.18 , Samba 2.2.3a and DosEmu 1.1.3. I am > running a Clipper aplication under DosEmu and when some users access the > same Clipper aplication via Samba, my db/ntx files are corrupted!!!!...The > locks & unlocks doesn´t work well. > Please, have you resolved this problem in your site ???
Clipper can use different lock semantic in each RDD Some of them use phantom locks (over the size of file) and over the 2GB limit (DOS has 32bit lock area, POSIX 31 when you use fcntl on 32bit machine). The newest Samba use fcntl64 (63 bit lock area) with kernel 2.4 I guess it is the problem. When I last time checked DOSEMU it used only normal fcntl and cleared the highest bit in lock address. It has to be changed to avoid such lock problems. BTW. OPLOCKS is other lock mechanism and should be disabled in samba or other smb file servers for DOS apps. Usually DOS programs cannot benefit form OPLOCKS but it's very easy way to corrupt shared data (OPLOCKS increase the time when new/modified data is stored on client side and not on the server). best regards, Przemek - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
