![]() I know there are some quite adamant users out there who insist that ACLs don't work or are broken and as first recourse tell other users to strip ACLs. # group: this point, if we didn't have the group:builtin_users:full_set entry, we would lose write access. A very serious " thank you" is due to you chmod 755 getfacl new_dir I was pretty much in despair at the start of this misadventure, so I want to thank you for taking this on, and your clear and steady navigation through the problem until it was fixed. I am actually immensely grateful to you Anodos. A very serious " thank you" is due to you sir. I have learnt a valuable lesson about how to use the builtin_user group, which I'm sure will be a get out of trouble free card going forward, and will allow me access to intractable share problems in the future. I'm delighted to tell you this hasn't been a complete wild goose chase however. This also confirms my earliest comment in this thread that "I have a funny feeling that this Samba share DID work at one point" - clearly it must have, since no other changes were necessary other than re-creating it. So my conclusion is that there was some glitch - what we may never know - with the execution of the samba share, since simply re-doing it fixed it. I rolled back all the changes I'd made, removing the "builtin_user" group from the ACL and making various entities members - and tried again. ![]() Guess what happened then? I immediately had access! And the weirdness doesn't stop there either. In a fit of what can only be described as superstition, I deleted the Syncthing share from my Windows desktop, and went to Truenas to re-create it. So - still the samba share to the syncthing folder was locked out. Aside from me and root, the only other user on the system is Sync - the name i gave to the Syncthing user, and that was already a member of the builtin_user group. I puzzled it a moment, then tried adding root to the builtin_users group too. Still - no access to the Syncthing samba share. Then I added my 'personal name' account to the group builtin_users: ![]() I added the ACL entry you suggested, complete with recursive applicability. I was initially thrilled - even I undersdtood the logic of what you were saying. However I have managed to get the results of the 2nd command you suggested too! Honestly I confess I don't understand the commands you asked for, nor their results. However I have managed to get the results of the 2nd command you suggested testparm -s ![]() Vfs objects = streams_xattr shadow_copy_zfs ixnas aio_fbsdĬomment = Share for Film, Music, TV & Photos. Nsupdate command = /usr/local/bin/samba-nsupdate -g Load smb config files from /usr/local/etc/nf Life is too short to spend days (and days and days and days) trying to do something that should be as simple as accessing my Syncthing folder.Ĭan anyone tell me how to fix this please? No pithy comments please, just a 'how to' to gain acess to the Samba share from anyone kind enough to share their insight I'd be so grateful at this point. Sometimes I think about packing it in and buying a Synology. It's so fiendishly complicated that it often feels like one step forward, four or five back. I came new to TrueNAS a few months ago and have invested many hundreds of hours trying to learn how to use it. I am quite desperate for help to fix this. I have a funny feeling that this Samba share DID work at one point, but no longer, for reasons unknown. As no one but me uses this system I set up an ACL which uses Basic permissions, Full Control, Inhereted to and And the whole thing is recursive. I have a couple of other Samba shares to other datasets that work fine, I just can't access this one. Then I set up a Samba share to windows 10, which when I try to open it, says Windows cannot access it. I have successfully set up the Syncthing plugin and verified that everything works as it should.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |