Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Triage] Wrong file permission mask in Unraid #558

Open
Deses opened this issue Jan 10, 2025 · 1 comment
Open

[Triage] Wrong file permission mask in Unraid #558

Deses opened this issue Jan 10, 2025 · 1 comment
Assignees
Labels

Comments

@Deses
Copy link

Deses commented Jan 10, 2025

Describe the bug
Folders and files are created with file perms 755 / 644, when in unraid all files in the user shares should have the perms 777 and user:group 99:100 (nobody:users). User/Group are OK.

With 777, Share users (which aren't the user nobody) can edit the files.

To Reproduce
Steps to reproduce the behavior:

  1. Install the Pinchflat CA App
  2. Download stuff
  3. Try to edit / move / delete from a SMB share
  4. Permission error

Expected behavior
I can manage the files just fine from a SMB client.

Screenshots
image
image

Diagnostic info

  • App Version: 2025.1.3
  • yt-dlp Version: 2024.12.23
  • Apprise Version: v1.9.1
  • System Architecture: x86_64-pc-linux-gnu
  • Timezone: Europe/Madrid
@Deses
Copy link
Author

Deses commented Jan 10, 2025

I tried defining an UMASK variable but Pinchflat is ignoring it.

<Config Name="Umask" Target="UMASK" Default="0000" Mode="" Description="Mask that controls how file permissions are set for newly created files.  The value of the mask is in octal notation." Type="Variable" Display="advanced" Required="true" Mask="false">0000</Config>

Tried redownloading files with that and it's keeps creating files with a 022 umask.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants