Hi ! I have an unique situation. An SCO Unixware 7.1.3 with Samba 2.2.7a (yes, i know; it sucks !) On the machine, is running MS Foxpro 2.6 for UNIX (it's running pretty well for several years) but due to new demands (like Crystal Reports, Visual view; etc) the directories with DBF files were shared using Samba. At the beginning, when everything was only about reading, there were no problems. But now, it's necessary to write to the DBF files from the Visual Application (Visual Basic) and now there are some problems. While a user may be reading data from the Visual application, and someone else writes to the DBF file from the FoxPro for UNIX, the changes are not being seeing in the Visual application. And if the user from Visual writes data to the DBF, there's a data corruption then; because of the concurrent connections from the FoxPro from Unix. I think it's a matter of oplock issue between Fox and Samba. Samba opens the DBF file, without concerns if FoxPro has the file open, and viceversa. When everyone is running only the Visual application, there's no problem. If the users are running only FoxPro for Unix, there's no problems. If the users run FoxPro for Unix for read/write and Visual for read only, there's no problem. The problems araise when the users are running FoxPro and Visual for read and write files simultaneosly. Any idea to run this configuration smoothly? Thanks in advance for the help. Kind regards.
On Thu, 2006-03-16 at 17:40 -0500, Carlos Prieto wrote:> Hi ! > > I have an unique situation. > > An SCO Unixware 7.1.3 with Samba 2.2.7a (yes, i know; it sucks !) > > On the machine, is running MS Foxpro 2.6 for UNIX (it's running pretty well > for several years) but due to new demands (like Crystal Reports, Visual > view; etc) the directories with DBF files were shared using Samba. At the > beginning, when everything was only about reading, there were no problems. > But now, it's necessary to write to the DBF files from the Visual > Application (Visual Basic) and now there are some problems. While a user may > be reading data from the Visual application, and someone else writes to the > DBF file from the FoxPro for UNIX, the changes are not being seeing in the > Visual application. And if the user from Visual writes data to the DBF, > there's a data corruption then; because of the concurrent connections from > the FoxPro from Unix. > > I think it's a matter of oplock issue between Fox and Samba. Samba opens the > DBF file, without concerns if FoxPro has the file open, and viceversa. When > everyone is running only the Visual application, there's no problem. If the > users are running only FoxPro for Unix, there's no problems. If the users > run FoxPro for Unix for read/write and Visual for read only, there's no > problem. > > The problems araise when the users are running FoxPro and Visual for read > and write files simultaneosly. > > Any idea to run this configuration smoothly?I would start by setting (I think) 'strict locking = yes', and disable oplocks for this file extension. I would also strongly suggest migration off SCO, to a platform compatible with current Samba 3.0. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Student Network Administrator, Hawker College http://hawkerc.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 191 bytes Desc: This is a digitally signed message part Url : http://lists.samba.org/archive/samba/attachments/20060317/f8504ee5/attachment.bin
Carlos Prieto wrote:> On the machine, is running MS Foxpro 2.6 for UNIX (it's running pretty well > for several years) but due to new demands (like Crystal Reports, Visual > view; etc) the directories with DBF files were shared using Samba. At the > beginning, when everything was only about reading, there were no problems. > But now, it's necessary to write to the DBF files from the Visual > Application (Visual Basic) and now there are some problems. While a user may > be reading data from the Visual application, and someone else writes to the > DBF file from the FoxPro for UNIX, the changes are not being seeing in the > Visual application. And if the user from Visual writes data to the DBF, > there's a data corruption then; because of the concurrent connections from > the FoxPro from Unix. > > I think it's a matter of oplock issue between Fox and Samba. Samba opens the > DBF file, without concerns if FoxPro has the file open, and viceversa. When > everyone is running only the Visual application, there's no problem. If the > users are running only FoxPro for Unix, there's no problems. If the users > run FoxPro for Unix for read/write and Visual for read only, there's no > problem. > > The problems araise when the users are running FoxPro and Visual for read > and write files simultaneosly. > > Any idea to run this configuration smoothly? > > Thanks in advance for the help. > > Kind regards. >Have a look at: http://drouillard.ca/Tips&Tricks/Samba/Oplocks.htm Regards Gerald Drouillard http://www.drouillard.ca