--umask behaving incorrectly

[zmike808]

The value of umask currently sets the base permissions for all the files/directories in the mount. The correct behavior should result in the specified umask being subtracted from the base permissions.

current behavior: --umask=0777 = rwx rwx rwx expected behavior --umask=0777 = no permissions (--- --- ---)

current behavior: --umask=0000 = is ignored / same as running plexdrive without this parameter expected behavior --umask=0000 = rwx rwx rwx

current behavior: --umask=0001 = --- --- --x expected behavior --umask=0001 = rwx rwx rw-

[koalaeagle]

I can confirm this behavior, it caused me quite a few permission headaches. I am using a combination of plexdrive and rclone. rclone treats the umask correctly but plexdrive does not which is why I was so confused. I am using v5.0.0. My intended permissions are rwx rwx --- and I was able to set 0770 instead of 0007 as a workaround for now but it would be nice to have this fixed going forward!

[drew7721]

I am having the same issue. But I'm getting a message that umask is not supported. So I'm not sure how you manage to get write access for group. 😞

Never-mind, I was using the -o flag to pass the umask.

[wiserain]

Not sure type of integer associated with the umask implementation, but prepending 0100 gets right permission, i.e.

--umask=0100775