2022-06-04, 11:12 PM
I'm trying to transition my NextPVR setup from my power-hungry Windows box to a docker instance in Unraid, and I'm learning as I go. I apologize in advance, because I'm a little outside of my depth here.
Setup went fine, thanks to those who have provided guidance in these forums. It can access the HDHomeRun on the network, has gathered guide data, and records to the correct directory. Honestly, it's working quite nicely. Except one problem.
The recording directory is shared to a non-root user account, which has r/w permissions to the share in Unraid. Let's call the account "bandit". When I access that share via Windows as bandit, I can view the file list and watch the recordings. But when I try to delete or edit a recording, a pop-up tells me, "You require permission from SERVER/root to make changes to this file". I can delete the same files from within the NextPVR WebUI.
I think I've found the cause of this problem. Inside the shared directory, I've created folders for sorting recordings (TV, Movies, Sports). Those are all 777 permissions, as seen here:
But whenever NextPVR creates a directory and/or records a show to a TS file, it writes those with 755 permissions. Here's an example inside the TV folder:
And the same for the files inside:
I'm not sure this is the source of the problem, but seems like it. I'd like to be able to access those files/directories as r/w using bandit, as well as any future account I give r/w share access to, including possibly just making the whole directory public r/w. If possible, I'd prefer to not manually chmod it after the recording completes.
In Windows on NTFS this was never a problem. Honestly, I don't know if this is related to NextPVR, docker, or Unraid, so I started here. Is this typical behavior? And is there a way to always have directories and files written as 777 when NextPVR records?
Setup went fine, thanks to those who have provided guidance in these forums. It can access the HDHomeRun on the network, has gathered guide data, and records to the correct directory. Honestly, it's working quite nicely. Except one problem.
The recording directory is shared to a non-root user account, which has r/w permissions to the share in Unraid. Let's call the account "bandit". When I access that share via Windows as bandit, I can view the file list and watch the recordings. But when I try to delete or edit a recording, a pop-up tells me, "You require permission from SERVER/root to make changes to this file". I can delete the same files from within the NextPVR WebUI.
I think I've found the cause of this problem. Inside the shared directory, I've created folders for sorting recordings (TV, Movies, Sports). Those are all 777 permissions, as seen here:
Code:
drwxrwxrwx 1 nobody users 60 May 30 19:17 ./
drwxrwxrwx 1 nobody users 134 Jun 4 10:55 ../
drwxrwxrwx 1 nobody users 10 May 30 19:17 Movies/
drwxrwxrwx 1 nobody users 10 Jun 4 12:59 Sports/
drwxrwxrwx 1 nobody users 10 Jun 4 15:26 TV/But whenever NextPVR creates a directory and/or records a show to a TS file, it writes those with 755 permissions. Here's an example inside the TV folder:
Code:
drwxrwxrwx 1 nobody users 10 Jun 4 15:26 ./
drwxrwxrwx 1 nobody users 60 May 30 19:17 ../
drwxr-xr-x 1 root root 139 Jun 4 14:31 WKRP\ in\ Cincinnati/And the same for the files inside:
Code:
drwxr-xr-x 1 root root 139 Jun 4 14:31 ./
drwxrwxrwx 1 nobody users 10 Jun 4 15:26 ../
-rw-r--r-- 1 root root 394689424 Jun 4 14:31 WKRP\ in\ Cincinnati.S01E15.Never\ Leave\ Me,\ Lucille.ts
-rw-r--r-- 1 root root 788 Jun 4 14:31 WKRP\ in\ Cincinnati.S01E15.Never\ Leave\ Me,\ Lucille.xmlI'm not sure this is the source of the problem, but seems like it. I'd like to be able to access those files/directories as r/w using bandit, as well as any future account I give r/w share access to, including possibly just making the whole directory public r/w. If possible, I'd prefer to not manually chmod it after the recording completes.
In Windows on NTFS this was never a problem. Honestly, I don't know if this is related to NextPVR, docker, or Unraid, so I started here. Is this typical behavior? And is there a way to always have directories and files written as 777 when NextPVR records?
