search for: aapl_rsiz

...ormance problems on OS X clients. We do NOT user netatalk. Current vfs_fruit config: vfs objects = catia fruit streams_xattr fruit:resource = file fruit:metadata = netatalk fruit:locking = none fruit:encoding = private fruit:aapl = yes readdir_attr:aapl_rsize = true readdir_attr:aapl_finder_info = true readdir_attr:aapl_max_access = true fruit:nfs_aces = yes fruit:veto_appledouble = yes Problem -> OS X clients are unable to create new extended attributes (and ACLs) with exception of ResourceFork and FinderInfo which are...

...p = local mdns name = mdns log file = /var/log/samba/log.smb max log size = 1000 syslog = 0 server role = standalone server unix password sync = no min protocol = SMB2 ea support = yes vfs objects = catia fruit streams_xattr fruit:aapl = yes readdir_attr:aapl_rsize = yes readdir_attr:aapl_finder_info = yes readdir_attr:aapl_max_access = yes fruit:nfs_aces = yes fruit:copyfile = yes fruit:metadata = netatalk fruit:resource = file fruit:locking = none fruit:encoding = private unix extensions = yes spotlight = yes smb...

...etatalk. > > Current vfs_fruit config: > > vfs objects = catia fruit streams_xattr > fruit:resource = file > fruit:metadata = netatalk > fruit:locking = none > fruit:encoding = private > fruit:aapl = yes > readdir_attr:aapl_rsize = true > readdir_attr:aapl_finder_info = true > readdir_attr:aapl_max_access = true > fruit:nfs_aces = yes > fruit:veto_appledouble = yes fwiw, I'd remove anything that is the default. > Problem -> OS X clients are unable to create new extended a...

I have a problem regarding permissions of a SMB share. I created a share for my user ?steven? which has correct unix permissions (I have read/write access to this folder when I log in to the server via ?steven?) drwxr-xr-x steven root share When I export this share with no ?force user? entry in smb.conf I can access the share only read only. When I use ?force user = steven? it?s the same.

...[defaultsettings] access based share enum = Yes available = No browseable = No case sensitive = Yes create mask = 0666 directory mask = 0777 include = /etc/samba/smb-shares.conf.local read only = No strict locking = No use sendfile = Yes vfs objects = catia fruit acl_xattr aio_pthread readdir_attr:aapl_rsize = no fruit:veto_appledouble = no fruit:resource = file fruit:metadata = stream fruit:locking = none fruit:encoding = I've tested removing the "use mmap" line and the error disappears. The documentation on the samba wiki ( https://wiki.samba.org/index.php/Configuring_clustered_Samba...

...[global] workgroup = LOCAL log file = /var/log/samba/log.smb max log size = 1000 syslog = 0 server role = standalone server unix password sync = no min protocol = SMB2 ea support = yes vfs objects = catia fruit streams_xattr fruit:aapl = yes readdir_attr:aapl_rsize = yes readdir_attr:aapl_finder_info = yes readdir_attr:aapl_max_access = yes fruit:nfs_aces = yes fruit:copyfile = yes fruit:metadata = netatalk fruit:resource = file fruit:locking = none fruit:encoding = private unix extensions = yes spotlight = yes smb...

When you say “real symlinks on OSX” do you mean an “alias” that Finder would create? Or a Unix-type symlink using the “ ln -s file link” command in Terminal? A Finder alias is not the same as a Unix-type symlink. My NAS runs Debian Linux with version 4.3.11 of smbd; my clients are all OSX Mojave. If I create an alias using Finder on the NAS, it behaves like a normal alias in OSX UNLESS I move