This is a discussion on RE: SAMBA & ISAM Databases - Samba ; On Tue, 2004-09-14 at 18:23, 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 ...
On Tue, 2004-09-14 at 18:23, 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.
> shouldn't "posix locking =3D yes" in smb.conf give consistent locking =
> between SMB and posix (NFS or local) access?
Yes and no. 'posix locking =3D yes' will allow *some* coordination
between windows and POSIX locks, but it is far from a complete mapping.=20
I presume your linux-side applications are running under wine?=20
No. It is not running under wine. Is running in Linux.
Unfortunately, wine does not yet work with Samba (and Samba does not yet
work with wine) to jointly manage the windows locks, which are much
richer than can be expressed under posix.
Worse still, smbfs does not support locking at all, and NFS is
notoriously poor at locking.
So, if smbfs does not support any type of lock I am waisting my time
trying to get a solution under smbfs. Is that correct? So which way
should I go? Any suggestions, ideas??
Andrew Bartlett firstname.lastname@example.org
Authentication Developer, Samba Team http://samba.org
Student Network Administrator, Hawker College email@example.com