On the topic of Access databases:
All the Access databases we have are set to "compact on close". I've
noticed that since I moved the databases to a Samba server from a w2k
server, I get db1.mdb, db2.mdb, etc. every day instead of only
occasionally. mdb's are set in "veto oplock files". Permissions are
2770 for administrator/Domain Admins, and acl's are used to r/w to these
files. Inherit owner, permissions, and acls are all set to Yes. strict
locking is the default auto.
As someone earlier suggested, I tried "force security mode" as the fix
for MS Office files. It didn't seem to have an effect on the mdb
problem, and it stripped the acl's from excel spreadsheets. It seemed
to override the inherit "acls parameter".
Is the mdb problem something I'll have to live with, or can it be remedied?
Dale
Jeremy Allison wrote:
On Fri, Aug 01, 2008 at 10:21:54AM +0200, Hannes Gnad wrote:
Hi.
With samba 3.0.25b as part of Mac OS X 10.5.4 Server, I'm encountering
issues with .mdb files: Some Windows apps use client software on local
machines and one Microsoft Access database on the SMB share. Everything
works fine, as long as there's only one client using the .mdb file. As
soon as a second client tries to access (and write!) to the .mdb file,
the clients on the Windows machines report broken network connections
and crash.
In Server-Admin/File-Sharing, the shares are open for SMB only, oplock
and strict locking both off. No ACL, Posix permission admin r/w, group
r/w, other r.
Turn strict locking back on, or at least to Auto.
Jeremy.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
