Opened 18 months ago
Last modified 7 months ago
#1046 accepted enhancement
Add option to veto Apple related files
| Reported by: | bms | Owned by: | william |
|---|---|---|---|
| Priority: | minor | Milestone: | 9.1.0-RELEASE |
| Component: | GUI | Version: | 8.0.1-RELEASE |
| Keywords: | afp smb | Cc: |
Description
It has been noted elsewhere that configuration changes to afpd alone cannot stop MacOS X clients from creating the necessary files and directories to support Finder activity.
To this end, it would be useful to 'veto' the files and directories thus created, to prevent them being seen from within the SMB view of the filesystem namespace. The visibility of these entries is completely benign, but may be confusing to users or filesystem backup tools.
This is possible with the current GUI, but the necessary directives and paths, have to be added (and vetted) manually.
I should like to see this added as an option in the GUI. I propose this as a new feature for the next release.
Change History (2)
comment:1 Changed 10 months ago by william
- Milestone set to 9.1.0-RELEASE
- Owner set to william
- Status changed from new to accepted
comment:2 Changed 7 months ago by fracai
Note: See
TracTickets for help on using
tickets.
This may be aided by moving to Netatalk v3 (presumably with FreeNAS 9?), which can store Mac metadata and resource forks as extended attributes. See the "New AppleDouble? backend" section of the upgrade documentation.
A veto option would still be necessary for .DS_Store files. While these can be disabled client side, that is a bit heavy handed for Mac clients that also connect to other Macs (where the .DS_Store creation is more likely to be desired).