I'm looking for best practices on setting permissions for partitions (non-boot) containing databases and backups for FMS7 running under 10.4.8, non-server.

Listed first are the permission defaults, on the boot drive, in /Library/, for point of reference:

----------

drwxrwxr-x 11 fmserver fmsadmin 374 Dec 27 15:32 FileMaker Server 7

drwxrwxr-x 7 fmserver fmsadmin 238 Dec 29 16:20 Data

drwxrwxr-x 2 fmserver fmsadmin 68 Jul 14 2003 Backups

drwxrwxr-x 4 fmserver fmsadmin 136 Dec 8 16:07 Databases

drwxrwxr-x 3 fmserver fmsadmin 102 Dec 8 16:46 Sample_Configuration

-rwxrw-r-- 1 fmserver fmsadmin 524288 Jan 6 2005 FMServer_Sample_Config.fp7

----------

Next are the permissions created when creating partitions (and folders on them), and copying a database via (temporarily activated) File Sharing. Logged in as admin (locally when creating the partitions, and also via File Sharing when moving databases to the FMServer)

----------

[bACKUP VOLUME (PARTITION)]

drwxr-xr-x 8 admin staff 374 Dec 12 16:10 Backups

----------

[DATABASES VOLUME (PARTITION)]

drwxr-xr-x 8 admin staff 374 Dec 12 16:10 Databases

-rwxrwxr-x 1 admin staff 1171456 Dec 29 11:13 TestDatabase.fp7

----------

1) Should I simply change the permissions to exactly the way they are in /Library/?

2) I see the execute bit for fmsadmin is removed, compared to the enclosing folder, of FMI's FMServer_Sample_Config.fp7 -- is that how I should set permissions on the databases that get moved to the server?

Note that when I copied "TestDatabase.fp7" to the databases partition, with admin and staff having full control, but no fmserver or fmsadmin explicit access, it works. I'm not suggesting it's fine to leave it this way, just curious about why it works.

Ken

The Group "fmsadmin" must have "Read & Write" permission for your database files and the folders they reside in. You'll need to check this each time you move files or folders into your hosted folder.