> Comand given to mount Samba share:
> mount -t smbfs -o username=3Dwhatever,password=3Dkey //pepe/testdata=20
> /testdata

Could you please give me the equivalent on CIFS?

I have never worked with it.

As regarding NFS any advice in what to look for "when testing heavily"?


Jos=E9 Guimar=E3es [ pg@moose-software.com ]
Moose Software

-----Mensaje original-----
De: Christopher R. Hertel [mailto:crh@ubiqx.mn.org]=20
Enviado el: martes, 14 de septiembre de 2004 17:43
Para: Pepe Guimar=E3es
CC: samba-technical@lists.samba.org
Asunto: Re: SAMBA & ISAM Databases

Have you tried using the CIFS vfs instead of smbfs?

Just a guess, but it may be worth trying. If the Windows clients are=20
seeing and respecting the locks then I have to assume that Samba is=20
handling them correctly. The different piece, then, is the client on
Linux side.

Another test worth trying would be to mount the directory on the Linux
clients using NFS instead of SMB. I'd test that configuration heavily=20
before going live with it, but it would provide some interesting=20

Chris -)-----

On Tue, Sep 14, 2004 at 10:23:09AM +0200, Pepe Guimar=E3es wrote:
> I have a heterogeneous network with a R.H. Linux server running Samba

> 3.0.5 and various Win clients (from Win 98 to Win XP Pro). On a Samba=20
> share I have an ISAM database (Access, FoxPro etc. like)
> that is being accessed by applications running on the Win clients and

> applications running in Linux.
> I have disabled "opplocks" in both Win9x clients and on the Samba

> I have "mounted" the Samba share on the Linux server so that Linux
> applications are "pathed"
> to the share and accessing the data there.
> The problem arises with locks. Files locked by the Win clients are=20
> seeing as locked by Win clients but not by Linux and viceversa.
> Any solution for this?
> I have "played" with options in Samba (level2 oplocks, veto oplocks,=20
> locking, kernel oplocks, etc.) without any improvements. One thing=20
> that I have clear is oplocks =3D no.
> Other parameters we have tried:
> =20
> To be more specific:
> Network name for Linux machine: pepe
> Name of Samba share (as seen by Win clients) : testdata Directory=20
> where data is on linux machine : /u/testdata
> Thus data can be accessed by: //pepe/testdata
> Mount point for Samba share in Linux: /
> Comand given to mount Samba share:
> mount -t smbfs -o username=3Dwhatever,password=3Dkey //pepe/testdata=20
> /testdata
> Checked mounting with:
> mount
> gives me : //pepe/testdata mounted on /testdata type smbfs (o) <---
> By the way: what means the (o)?
> Then I make the paths to access the data from Linux to be /testdata=20
> and fron win clients to be //pepe/testdata
> Can you see anything wrong?
> Tests I am going to make are:
> 1-Modify the name of the Samba share so that "share name <> name=20
> linux directory" 2-Mount the Samba share at another point rather than=20
> / 3-Try to access the data from Linux with the same full path as Win
> clients. In the above case //pepe/testdata rather than /testdata
> Finally:
> shouldn't "posix locking =3D yes" in smb.conf give consistent locking =

> between SMB and posix (NFS or local) access?
> =20
> =20
> =20
> Jos=E9 Guimar=E3es [ pg@moose-software.com ]
> Director
> Moose Software
> http://www.moose-software.com
> =20

"Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development,
ubiqx Team -- http://www.ubiqx.org/ -)----- crh@ubiqx.mn.org
OnLineBook -- http://ubiqx.org/cifs/ -)----- crh@ubiqx.org