Hi there, I've had SABnzbd running well on my Synology NAS for a few years. Recently I changed the download paths for SAB, now downloaded folders get 777 perms like they should, but subfolders and files are on 666 which requires I manuallgy change permissions before Plex can see the files. The incomplete and download directories are owned by SAB, and set to 777. The permissions setting is 777 also.
I think the issue may be that SAB applies the perms, then unpacks the files? I just need to get things back how they were, but with the new directories.
EDIT: Dump of logs from a test http://pastebin.com/syp6yKqV
Wrong permissions on unpacked files
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Wrong permissions on unpacked files
You did set permissions in Config->Folders?
Re: Wrong permissions on unpacked files
Yup, they're set to 777.
The folder of the unpacked file has drwxrwxrwx permissions, but the contents are -rw-rw-rw-
The folder of the unpacked file has drwxrwxrwx permissions, but the contents are -rw-rw-rw-
Re: Wrong permissions on unpacked files
The files have the right permission.
They don't need "x", since they're not executable.
They don't need "x", since they're not executable.
Re: Wrong permissions on unpacked files
If they don't have x, my Plex Media Server can't see them. Why can't SAB just set the permissions as I've specified? It was working in the past.
Re: Wrong permissions on unpacked files
SABnzbd has done it like this forever.
A work-around is to make your own user script.
Something like this:
cd "%1"
find . -type f -exec chmod +x {} \;
A work-around is to make your own user script.
Something like this:
cd "%1"
find . -type f -exec chmod +x {} \;

