Jump to content

Noface

Member
  • Posts

    2
  • Joined

  • Last visited

Everything posted by Noface

  1. I think MacOS doesn't seem to like the windows ACLs. There's no documentation on this for recent macOS (their docs have been getting worse or deleted) but they did introduce their own branch of samba that might have affected that. ACLs on mac and Windows are natively quite different. e.g. on a mac: [mac174:~] noface% ls -le total 0 drwx------+ 9 noface staff 288 18 Jan 00:45 Desktop 0: group:everyone deny delete on windows share: drwx------+ 1 noface staff 16384 5 Oct 2017 _SYNCAPP 0: AAAABBBB-CCCC-DDDD-EEEE-FFFF82000001 inherited allow list,add_file,search,delete,add_subdirectory,readattr,writeattr,readextattr,writeextattr,readsecurity,file_inherit,directory_inherit 1: group:groupname inherited allow list,add_file,search,delete,add_subdirectory,delete_child,readattr,writeattr,readextattr,writeextattr,readsecurity,writesecurity,chown,file_inherit,directory_inherit 2: AAAABBBB-CCCC-DDDD-EEEE-FFFF82000002 inherited allow list,search,readattr,readextattr,readsecurity,file_inherit,directory_inherit 3: AAAABBBB-CCCC-DDDD-EEEE-FFFF82000003 inherited allow list,add_file,search,delete,add_subdirectory,readattr,writeattr,readextattr,writeextattr,readsecurity,file_inherit,directory_inherit 4: user:noface inherited allow list,add_file,search,delete,add_subdirectory,delete_child,readattr,writeattr,readextattr,writeextattr,readsecurity,writesecurity,chown,file_inherit,directory_inherit 5: AAAABBBB-CCCC-DDDD-EEEE-FFFF82000004 inherited allow list,search,readattr,readextattr,readsecurity,file_inherit,directory_inherit 6: group:admin inherited allow list,add_file,search,delete,add_subdirectory,delete_child,readattr,writeattr,readextattr,writeextattr,readsecurity,writesecurity,chown,file_inherit,directory_inherit So you can physically see a difference in how they are handled. I think it just doesn't sync up and can cause issues even if you set up permissions correctly. I have an environment where all other apps do not have a problem though, only vectorworks which is frustrating. I think that also because POSIX permissions are simpler and I think are more supported on MacOS, I've had to go for a linux server (cos I don't like mac servers) but also why Doug has had a good time. There must be a way around this but doesn't seem like a common workflow in general with Vectorworks users. I've created a linux server and to make sure that sharing work is easier in general even if permissions have set, set the umask for all users to 002 Additionally, I think sharing via NFS has given me more customization on the type of mount I can do where I can retain the permissions through the mount rather than with Mac Samba which only allows me to log in as the user. I think what would work with a Samba set up though is if you have Domain Controller managed user accounts to sort out your permissions (which I haven't done yet). The linux nfs set up seems to be working well so far and I would recommend it for a storage server to everyone at the moment. (Using CentOS 7.6 server but whatever you prefer would probably be fine.) If anyone has any questions, let me know!
  2. I'm in a similar situation and have a windows server 2016 serving my data at the moment. I get the read only error from Windows Samba shares, windows nfs share, and I'm about to try a Linux nfs share to test these files. With the former, it opens but only in read only format. I know that Macs from like 10.10 (I think) have a different version of samba to windows. Is this strictly a samba issue? What makes me skeptical is that it was also a problem via NFS on the windows server. Then again... Windows NFS is terrible as well. @doug, with your mac server, are you serving purely over NFS?
×
×
  • Create New...