[Samba] Serving MS Access Databases, with ACL

jayendren anand maduray jayendren at hivsa.com
Thu Nov 1 07:47:14 GMT 2007

Hi Dale.

Thanks for this, would you guys be able to send me a complete example, 
that would allow read/write access for two users
(you can call them user1, and user2)

Alternatively, you can comment on this one:
Creating the directories, and set permissions:

#mkdir /srv/samba/file-server/studies/databases
#setfacl -R -m u:user1:rwx,u:user2:rwx 
#getfacl /srv/samba/file-server/studies/databases
# file:
# owner: root
# group: root

The share entry in smb.conf:

        path = /srv/samba/file-server/studies/databases
        create mode = 0777
        writeable = yes
        browseable = yes
        valid users = user1 user2 root
        writelist = user1 user2 root
        veto oplock files = /*.mdb/*.MDB
        nt acl support = yes
        nt pipe support = yes
        nt status support = yes
        inherit permissions = yes
        inherit acls = yes

#smbcontrol smbd reload-config
Global parameter acl compatibility found in service section!
Nick/Nico, we must look at moving access databases to SQL/MySQL 
backends, soon.
(See message from Dale/David below)

God bless.

Dale Schroeder wrote:
> jayendren anand maduray wrote:
>> Hi All.
>> Greetings from South Africa.
>> I have a Samba LDAP server (v 3.022) running on Ubuntu 6.10
>> Its serving about 200 users, with profiles, and domain logons.
>> I want to start serving MS Access Databases on it, with the  best 
>> speed performance as possible.
>> At the moment, the back ends for these databases, are about 200+ MB, 
>> and will grow over the next few years.
>> Basically, the share should serve about 4 users, with read/write access.
>> I am using the XFS file system, with ACL support.
>> Has anyone setup such shares in smb.conf?
>> I would really like to see an example.
>> Lastly, I do not think I want to use oplocks.
> That's a wise choice. In the share, use:
> veto oplock files = /*.mdb/*.MDB/
> David's suggestion about splitting the databases into Access frontend 
> and MySQL backend is also wise.  It has been my experience that large 
> Access databases corrupt quite easily.  That no longer happens in the 
> setup David mentioned.
> Dale
>> Any help, will be greatly appreciated.
>> God bless.
*Ellison, David* david.ellison at atkinsglobal.com 
/Wed Oct 31 15:03:52 GMT 2007/


This is a little off topic, but may be usefull to you. If the DB is
going to grow much more than that, I would use a real SQL backend to the
database. The MS Access DB backend is ok, however starts to suffer when
they become huge, by the sounds of things they may. I am sure there are
people with 700mb, 900mb etc Access databases, but its best to split the
front end from the database and use a SQL database like MySQl for the

Just food for thought :)


Jayendren Anand Maduray
Microsoft Certified Professional
Network Plus
Senior IT Administrator

Perinatal HIV Research Unit
Wits Health Consortium
University of the Witwatersrand

Alternate email address: jayendren at mweb.co.za
Fax Number: 0866857317

...There are 10 types of people, 
those who understand binary 
and those who do not...

More information about the samba mailing list