#859874 samba-vfs-modules: Error 13005 Accessing Share with OS X 10.5.8/iTunes 10.6.3 when enabling vfs_fruit #859874
- Package:
- samba-vfs-modules
- Source:
- samba
- Description:
- Samba Virtual FileSystem plugins
- Submitter:
- Patrik Schindler
- Date:
- 2024-10-26 08:27:02 UTC
- Severity:
- normal
- Tags:
I learned about vfs_fruit lately since it promises better integration with Macs.
Unfortunately, when Launching iTunes 10.6.3 within PPC Pac OS X 10.5.8, iTunes
complains about error 13005 while opening the iTunes Library. The only option
is to quit iTunes.
Remounting the same volume without vfs_fruit makes iTunes behave as expected.
Yes, these this is rather old software but I'm utilizing an old Mac as a
decent Music player for my living room.
Excerpt from smb.conf:
[global]
# Filesystem Settings
access based share enum = yes
acl map full control = no
client min protocol = NT1
default service = homes
delete readonly = yes
delete veto files = yes
guest ok = no
hide special files = yes
inherit permissions = yes
mangled names = no
map archive = no
map hidden = no
map system = no
read only = no
server signing = auto
unix charset = UTF8
use sendfile = yes
veto files = /.AppleDouble/.AppleDesktop/Network Trash Folder/
write cache size = 4096
[archiv]
comment = Archiv
path = /volumes/archiv
read only = no
valid users = @users
#vfs objects = fruit
#fruit:locking = netatalk
#fruit:copyfile = yes
Hi, vfs_fruit is more mature on stretch, can you update to this Debian version? Regards
Hello, thank you for your patience. Unfortunately I didn't record details to my test setup, so I created a new Tunes Library on Stretch and tested to access it. I get frequent messages that the iTunes Library could not be saved. No messages in log.smbd, though. What do you need me to do to provide further information? :wq! PoC PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc
This bug report has been filed in 2017, and last info was in 2019. I wonder if it is still relevant with samba 4.21. And I'm sorry for not being any more helpful than suggesting to check every new version of samba :) Thanks, /mjt