This is a discussion on Re: [Samba] Samba and Foxpro for Unix within the Samba forums, part of the Networking and Network Related category; --===============1136056491== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-AmxJZDeGzq77qMUQFyhH" --=-AmxJZDeGzq77qMUQFyhH Content-...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
--===============1136056491== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-AmxJZDeGzq77qMUQFyhH" --=-AmxJZDeGzq77qMUQFyhH Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2006-03-16 at 17:40 -0500, Carlos Prieto wrote: > Hi ! >=20 > I have an unique situation. >=20 > An SCO Unixware 7.1.3 with Samba 2.2.7a (yes, i know; it sucks !) >=20 > On the machine, is running MS Foxpro 2.6 for UNIX (it's running pretty we= ll > 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 t= he > DBF file from the FoxPro for UNIX, the changes are not being seeing in th= e > Visual application. And if the user from Visual writes data to the DBF, > there's a data corruption then; because of the concurrent connections fro= m > the FoxPro from Unix. >=20 > 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. Wh= en > everyone is running only the Visual application, there's no problem. If t= he > 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. >=20 > The problems araise when the users are running FoxPro and Visual for read > and write files simultaneosly. >=20 > Any idea to run this configuration smoothly? I would start by setting (I think) 'strict locking =3D 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 --=20 Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Student Network Administrator, Hawker College http://hawkerc.net --=-AmxJZDeGzq77qMUQFyhH Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQBEGgIBz4A8Wyi0NrsRAhyRAJ4z0DAPOenU7mAYGHqp9k PT/zBLiQCfZWGX 1W9TCJ94fVcvXy/NEw4oqPQ= =ABEW -----END PGP SIGNATURE----- --=-AmxJZDeGzq77qMUQFyhH-- --===============1136056491== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba --===============1136056491==-- |