"Custom" Permissions

Question

Level 1

37 points

"Custom" Permissions

Posting here because I only notice this on folders moved from networked users to my dropbox.

When I get folders placed in my dropbox and I then move them to a local folder they are marked as having "custom" permissions for my user and read only for everyone else. I cannot save any changes to these folders until I get info and change the "everyone" permission to read/write; I am not able to make a change to a permission labeled "custom."

With Tiger, when I moved a folder from dropbox to my local folder the permissions changed automatically to read/write.

I would like that same behavior in Leopard to save this permission change step everytime I get a folder. Suggestions?

Thanks -

Macbook 2.4, iMac 2.8, Mac OS X (10.5.2), Since 1984

Posted on May 16, 2008 5:49 AM

Reply

Answer 1

V.K.

Level 9

56,174 points

May 16, 2008 8:25 AM in response to Rik Tweed

it seems that your Drop Box doesn't have correct ACLs. run the following command in terminal and you should be fine from now on.

chmod +ai "`id -un` allow list,add file,search,delete,add_subdirectory,delete_child,readattr,writeattr,readextattr, writeextattr,readsecurity,writesecurity,chown,file_inherit,directoryinherit" ~/Public/Drop\ Box

Reply

Answer 2

Rik Tweed Author

Level 1

37 points

May 19, 2008 12:40 PM in response to V.K.

Didn't seem to help. Also tried boot from CD and repair permissions with no chnge.

My dropbox has these permissions:
*rik (me) Custom*
*rik (me) Custom*
*rik (me) Read & Write*
*staff Read only*
*everyone Read only*

Folders dropped into it from other network users have:
*rik (me) Custom*
*rik (me) Custom*
*nobody Read & Write*
*staff Read only*
*everyone Read only*

and I cannot save changes to the files or folders after moving them to my documents folder. I have to go in and add Read & Write to everybody because the "rik (me) custom" cannot be changed.

If I make a new folder in my documents folder there is no problem and the permissions are simply:
*rik (me) Read & Write*
*staff Read & Write*
*everyone Read & Write*

I don't get the whole "custom" permissions thing - anyone?
Thanks, Rik (me)

Reply

Answer 3

V.K.

Level 9

56,174 points

May 19, 2008 12:55 PM in response to Rik Tweed

repairing permissions does absolutely nothing to your home directory.

try this. First run

*chmod -N ~/Public/Drop\ Box*

this will remove all the ACLs from drop box so all the custom stuff should disappear.

Next run the command I gave you earlier

\\
*chmod +ai "`id -un` allow list,add file,search,delete,add_subdirectory,delete_child,readattr,writeattr,readextattr, writeextattr,readsecurity,writesecurity,chown,file_inherit,directoryinherit" ~/Public/Drop\ Box*

this should set things right.

Also, what you say about newly created folders in other places is very strange.

iF you create a folder in your Documents folder it should have Read not Read&Write for staff and everyone.
Could you check that?

Reply

Answer 4

Rik Tweed Author

Level 1

37 points

May 19, 2008 1:00 PM in response to V.K.

THIS IS THE RESPONSE:

-chmod: Failed to clear ACL on file ~/Public/Drop\: No such file or directory
-chmod: Failed to clear ACL on file Box: No such file or directory

[Process completed]

Reply

Answer 5

Rik Tweed Author

Level 1

37 points

May 19, 2008 1:02 PM in response to Rik Tweed

In Terminal, I am selecting "new command" pasting in your command and enter.

Am I doing this incorrectly?

Reply

Answer 6

Rik Tweed Author

Level 1

37 points

May 19, 2008 1:04 PM in response to V.K.

You are correct about the new folder in documents; it is as you indicated.

Reply

Answer 7

V.K.

Level 9

56,174 points

May 19, 2008 1:06 PM in response to Rik Tweed

you don't need to select "new command". Just paste the command into the terminal window and press enter.

Reply

Answer 8

Rik Tweed Author

Level 1

37 points

May 19, 2008 1:16 PM in response to V.K.

OK, thanks.
When I run the last command:
chmod -N ~/Public/Drop\ Box
it becomes normal: user RW, staff & everyone WO Dropbox

but then when I run the earlier command you provided I get an additional custom permission line again.

Reply

Answer 9

V.K.

Level 9

56,174 points

May 19, 2008 1:18 PM in response to Rik Tweed

that's how it should be. That command puts an ACL on your Drop box which will make it function as it should. You should be all set now.

Reply

Answer 10

Rik Tweed Author

Level 1

37 points

May 19, 2008 1:21 PM in response to V.K.

Well, thanks then. I will work with it and let you know. Your help is appreciated, VK.

Reply

Answer 11

V.K.

Level 9

56,174 points

May 19, 2008 1:24 PM in response to Rik Tweed

try it out. post back if you still have problems.

Reply

Answer 12

Rik Tweed Author

Level 1

37 points

May 27, 2008 9:28 AM in response to V.K.

Your suggestion has corrected my problem - I now get full ownership of items moved from my dropbox to my documents folder. This helps a lot, thanks!

Reply

Answer 13

V.K.

Level 9

56,174 points

May 27, 2008 9:33 AM in response to Rik Tweed

you are welcome!

Reply

Answer 14

Rik Tweed Author

Level 1

37 points

Aug 7, 2008 9:07 AM in response to V.K.

Well, I m back again. Still having this problem. Someone sends files in a folder to my dropbox; I drag the folder to a subfolder within user>documents folder; when I work on these files I cannot save changes because I have no permission; when I get info on the new folder it says the permissions are:
user(me): custom
nobody: Read & Write
staff: Read only
everyone: Read only

I cannot change the user permission level - it just won't change. I have to change "everyone" to Read & Write in order to save the file. This behavior is not always predictable, as well.

I have run the fixes posted here and it seems to help but then goes fubar again.

BTW, these files are being sent over ethernet from Macs running 10.4.x.

Is running these fixes periodically my only remedy? Does anyone know why this is happening? Shouldn't the permissions for my local folder be transferred to anything I place inside of it?

Thanks -

Reply

Answer 15

V.K.

Level 9

56,174 points

Aug 7, 2008 9:34 AM in response to Rik Tweed

hi Rick,
I don't know why this is happening. It shouldn't.

let's rerun the command on the drop box as follows:

chmod -N ~/Public/Drop\ Box

sudo chmod -R +a "`id -un` allow list,add file,search,delete,add_subdirectory,delete_child,readattr,writeattr,readextattr, writeextattr,readsecurity,writesecurity,chown,file_inherit,directoryinherit" ~/Public/Drop\ Box

you'll have to enter your admin password (which you won't see). that's normal.

Reply