kaynemo 13 Posted February 9, 2017 Posted February 9, 2017 (edited) Hi all, Before I've decided to write this post, I have tried a LARGE number of things, but still no cookie. The dream setup: * File server, running Netatalk (local network is mostly populated by Macs, smb doesn't do good), shares a folder off a harddrvive. * Another linux machine (linuxmint 18.1) on the same network runs emby-server and can see/mount the original share Cannot, no matter what I do, add this share to the library of the linuxmint machine, running emby. - I tried a straight path to the share - no love - I tried mounting the afp share to a local folder - no love, permission clash - even though the local folder is chown to emby and chmod to 777 (just for the hell of it), the minute the afp share is mounted to the local folder, permissions of the said folder change... At the end the library cannot access the share this or any other way. Is there ay workarounds to this ? I would greatly appreciate it. The linuxmint machine, running the emby-server, is scheduled to be replaced by a nanoBox (OPI+2) running dietPi with the same scheme in mind and if I cannot setup a full blown machine running a full blown ubuntu spinoff to do what I planned, it will be very very sad. Sorry for my English. Edited February 9, 2017 by kaynemo
mastrmind11 722 Posted February 9, 2017 Posted February 9, 2017 Hi all, Before I've decided to write this post, I have tried a LARGE number of things, but still no cookie. The dream setup: * File server, running Netatalk (local network is mostly populated by Macs, smb doesn't do good), shares a folder off a harddrvive. * Another linux machine (linuxmint 18.1) on the same network runs emby-server and can see/mount the original share Cannot, no matter what I do, add this share to the library of the linuxmint machine, running emby. - I tried a straight path to the share - no love - I tried mounting the afp share to a local folder - no love, permission clash - even though the local folder is chown to emby and chmod to 777 (just for the hell of it), the minute the afp share is mounted to the local folder, permissions of the said folder change... At the end the library cannot access the share this or any other way. Is there ay workarounds to this ? I would greatly appreciate it. The linuxmint machine, running the emby-server, is scheduled to be replaced by a nanoBox (OPI+2) running dietPi with the same scheme in mind and if I cannot setup a full blown machine running a full blown ubuntu spinoff to do what I planned, it will be very very sad. Sorry for my English. Have you tried setting up the share using NFS instead of AFP and either mounting it or addressing it from the server that way? I've had nothing but trouble w/ AFP on anything but other macs.
kaynemo 13 Posted February 9, 2017 Author Posted February 9, 2017 Actually, I just figured out !!!! This is what works: 1. On the machine running the emby-server: a. Stop emby b. Under superuser delete emby user instance c. Create a new emby user d. chown the folder to which afp share will be mounted to emby:emby 2. On the machine running afp file server a. Chown the mounted folder that is the share to emby:emby b. In the afp config file add @, emby in the allow section c. Restart the netatalk and avahi daemon 3. On the machine with emby server a. In terminal make a login with emby credentials b. Perform mount_afp to the folder you've chown[ed] in the part 1 c. Voila !!! The folder is now listed as emby emby d. Start emby server e. Library connects and scans !!! Two days did not go to waste !! Emby rules!!!! 1
kaynemo 13 Posted February 10, 2017 Author Posted February 10, 2017 (edited) No problem - glad to help. There is now a permissions hell issue. Since emby needs to have the folders and files read/write and assigned to emby on the share to scan the library, any other user having access to the share cannot add media - the server allows for it as the permissions are set very liberal, but the server assigns proper names to the files and folders, based on the username connected which is not later accessible by emby. Currently working on that. Edited February 10, 2017 by kaynemo
kaynemo 13 Posted February 13, 2017 Author Posted February 13, 2017 OK, I couldn't find an easy solution to the permission hell. Any attempt to force the system to automatically assign user owner:group and permissions to any file and folder created in the selected folder no matter what user failed (i am just not that savvy yet), at the moment ( and I need multiple route access to the share, including ftp access) I am sticking with using the user name:group accepted by embryo-server no matter what connection. It is not a very good solution, not an elegant one, but it will do for the moment. I wish there was a script or some config file that would allow me to do the user access the right way, but that will have to wait.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now