I wasn't sure where else to post this, maybe someone else can find this useful.

 

The only thing that drives us up the wall with unraid is the permissions, they are always broken. If i create a folder in a directory, everyone else is denied access.

 

We have tried just about every setting under the sun possible to stop this from happening. But no matter, the files and folders are written with ___'s username and they are the only ones allowed to do anything with it. That is, until someone runs /usr/local/sbin/newperms

 

I'm not the only one with this issue, i have a few friends, and even a box at work with the same problem.

 

So i basically modified the Monthly Parity Check package to fit our needs of running the newperms script every few hours.

 

This package runs it every night at 2:30AM, but it's very easy to modify the time of the cronjob. There is an editable variable for the base location it runs the script from.

 

Nothing ground breaking, just something else i no longer have to manually do every night.

daily_newperms-unmenu-package.conf

Did you try upgrading SAMBA? I've just done it and with fingers crossed am hoping my issues are put to rest...

I wasn't sure where else to post this, maybe someone else can find this useful.

 

The only thing that drives us up the wall with unraid is the permissions, they are always broken. If i create a folder in a directory, everyone else is denied access.

 

We have tried just about every setting under the sun possible to stop this from happening. But no matter, the files and folders are written with ___'s username and they are the only ones allowed to do anything with it. That is, until someone runs /usr/local/sbin/newperms

 

I'm not the only one with this issue, i have a few friends, and even a box at work with the same problem.

 

So i basically modified the Monthly Parity Check package to fit our needs of running the newperms script every few hours.

 

This package runs it every night at 2:30AM, but it's very easy to modify the time of the cronjob. There is an editable variable for the base location it runs the script from.

 

Nothing ground breaking, just something else i no longer have to manually do every night.

 

Short of a few times I have screwed things up I have never had issues with permissions...

 

And if you are logged into the server as a certain person then yes the files are going to be written as that user.

if you are logged into the server as a certain person then yes the files are going to be written as that user.

So there is no way to set up the 5.x series like I have my 4.7 set up? I have users defined that are read only, and users that have full access, and folders created by the full access users can be read by the other users just fine.

if you are logged into the server as a certain person then yes the files are going to be written as that user.

So there is no way to set up the 5.x series like I have my 4.7 set up? I have users defined that are read only, and users that have full access, and folders created by the full access users can be read by the other users just fine.

Sure, you can still do that

I'm on my laptop right now, Windows 7, username "iarp".

 

I've navigated to \\storage\music\ and i created a new folder called "Iarps Test Folder".

 

I go to my fathers workstation, he logins to Windows with username "rob". I navigate to \\storage\music\ and try to enter the "Iarps Test Folder"

 

Access Is Denied. What i did above, was strictly using Windows, i didn't login to the server and create it directly with putty, just Windows.

 

Always, it's the same issue here at work, that cronjob i made above, runs every 15minutes because it happens so damn often.

 

Here is a print out of ls -la on the music share just after creating the folder.

root@storage:/mnt/user/music# ls -la
total 1
drwxrwx--- 1 nobody users 112 2012-11-13 11:03 .
drwxrwx--- 1 nobody users 160 2012-11-13 09:54 ..
drwxrwx--- 1 nobody users 552 2011-12-17 20:27 Audio Books
drwxrwx--- 1 nobody users  96 2012-09-12 22:44 Backup
drwxrwx--- 1 nobody users  80 2012-10-16 22:21 Full Albums
drwxrwx--- 1 iarp   users  48 2012-11-13 11:03 Iarps Test Folder
drwxrwx--- 1 nobody users  48 2012-10-16 22:21 Incoming
drwxrwx--- 1 nobody users  80 2012-09-22 15:08 Partial Albums
drwxrwx--- 1 nobody users  48 2012-08-11 03:56 Podcasts
drwxrwx--- 1 nobody users  72 2012-11-03 09:44 Single Tracks
drwxrwx--- 1 nobody users  96 2012-05-21 03:40 Soundtracks
drwxrwx--- 1 nobody users 128 2012-08-12 09:54 foobar2000

 

As well, the permissions on the music share are, IARP and ROOT have Read/Write while everyone else has Read-only access.

if you are logged into the server as a certain person then yes the files are going to be written as that user.

So there is no way to set up the 5.x series like I have my 4.7 set up? I have users defined that are read only, and users that have full access, and folders created by the full access users can be read by the other users just fine.

Sure, you can still do that

But it sounds like other users are being denied access?

I have the same problem.  Permissions are the bane of my existence. 

Did you try upgrading SAMBA? I've just done it and with fingers crossed am hoping my issues are put to rest...

 

^^ Once again???

All of you who have added users to unRAID should probably google 'Linux Groups'  and 'linux permissions' to begin to understand exactly what you have to do when you add users and the role that groups can pay when you want to restrict file access.  It is not real difficult to learn exactly what you have to do and how it has to be done-- often on the Command Line level --- to get things to work exactly as you want them to.  But each situation will be different and thus, each solution will be different. 

 

I would not be surprise to find that running a daily (or any other time period) execution of the 'new permissions script' is actually defeating what you are attempting to do with your use of restricted users.

All of you who have added users to unRAID should probably google 'Linux Groups'  and 'linux permissions' to begin to understand exactly what you have to do when you add users and the role that groups can pay when you want to restrict file access.  It is not real difficult to learn exactly what you have to do and how it has to be done-- often on the Command Line level --- to get things to work exactly as you want them to.  But each situation will be different and thus, each solution will be different. 

 

I would not be surprise to find that running a daily (or any other time period) execution of the 'new permissions script' is actually defeating what you are attempting to do with your use of restricted users.

 

The restriction of users from certain shares is managed through unraid's GUI. Running the newperms command simply fixes the permissions on all files and folders applying nobody/users and what looks like 770 to all files and folders.

 

If you look at my previous response you can see that the test folder i created was assigned the user owner of "iarp" and not "nobody". Running newperms simply sets that to "nobody" instead.

 

I'm not sure how unraid manages who can edit what..etc, otherwise i would expect to see other groups assigned to other shares depending on what i setup for my users.