Benches macOS

12

"You have custom access"??? (permissions …

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Apologies if this has been covered before but I have quite a few folders that say "You have custom access" in the Sharing & Permissions section of the "Get Info" Finder window, not "You can read and write" as I would expect. Some of these really do seem to have unusual permissions, such as an "(unknown user)" entry, but others appear to have identical permissions to those for which Get Info says "You can read and write."

I suspect this is somehow related to some (but not all) of these folders originally being created in OS 10.1 (!!) & now in my Leopard file system courtesy of various Migration Assistant & Setup Assistant transfers spanning several Macs & hard drives since I played around with that ancient OS version.

Can anyone help me understand why this is so & more importantly how I can set these folder's permissions to the default, non-custom ones, which I assume will say "You can read and write" in the Get Info window?

12 replies

Sign in or join Beachball Help to reply.

  1. 0

    R C-R

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Well, in partial answer to my own question, it looks like the "custom access" phrase applies because my original user account (created in OS 10.1) has a group ID (GID) of 20, which I think is the one for "staff" & the original default for that version of the OS. Newer user accounts created in OS 10.4 have GID's that match the UID, like UID = 503; GID = 503 & are (I think) not part of the staff group by default.

    Thanks to a tip in
    Support - Discussions - Finder crashes when attempting to add to user permissions, I have discovered there is a Finder-based way to change the GID (right click on the user account in the Sharing System Preference -- who knew?) but I'm leery of doing this because of the warning that appears at the head of the Advanced Options drop down.

    Does anybody know the consequences of changing my "501" admin account's GID from 20 to 501 so it will match the Tiger (& beyond?) way of setting default permissions?

  2. 0

    R C-R

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Francine Schwieder wrote:

    This whole issue is very convoluted and confusing, with new bewilderments (at least bewildering to me) turning up every day.

    I agree completely! I keep hoping Apple will post some kbase articles or update Mac Help to explain more about the defaults & options, but so far the only things I have found are
    Mac OS X 10.5 Help: Sharing files on your network,
    Mac OS X 10.5 Help: Setting file-sharing options, & similar "lightweight" instructions which really don't say much more than I can discover by just poking around on my own.

    For myself, I simply gave up, cloned my Leopard install to the disk I had been using for Time Machine, and did an erase and install, then let the migration assistant that pops up as the install finishes copy what it wished how it wished from the cloned system. At least things now look consistent: no more "unknown" files, no ACLs where none should be in my home folder, all new files are saved to the apparent new standard: user francine uid 501, group staff gid 20 (of course yesterday I found out even that isn't as straight-forward as one might think, I'll spare your the details).

    Ironically perhaps, my Leopard install was done the same way (using Setup Assistant to copy everything possible from my Tiger clone, which is what I think you mean you used here) & it *did not* cause Spotlight to start indexing the Leopard volume or resolve any of the "unknown user" issues for me. This may have been because I messed around with permissions settings on some of my document files on the Tiger volume long ago when it had an additional standard account (since deleted), so that account's UID or GID could have been attached to a few files.

    Just to muddy the waters even more, I've discovered a file (/Library/Preferences/com.apple.preferences.accounts.plist) that contains an array of four essential properties of every account I've ever deleted since installing Tiger: the "UniqueID" (which appears to be the UID), the short & long user names, & the date deleted. This file apparently is created anew each time an account is deleted (except curiously its creation date is exactly one day later than that of the last account deletion) but it clearly includes the info from previous versions.

    Annoyingly, the Sharing Only user that I added that (I think) caused Spotlight to start indexing did not have the UID (& thus GID) of the deleted account I mentioned above, so the theory that the old account had something to do with it now looks dubious at best.

    The more I study this, the less it makes any sense. 😟

  3. 0

    Sylense

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    The problem is that, under Unix, permissions are actually tied to a User ID (UID).

    Normally, a copy would overwrite the permissions on the local copy for your local user account. However, this isn't always the case and sometimes you get the permissions problems you're experiencing.

    The usual method of cleaning this up is to boot from the Leopard install disk, run disk utility, and do a permissions repair.

  4. 0

    R C-R

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Sylense wrote:

    The usual method of cleaning this up is to boot from the Leopard install disk, run disk utility, and do a permissions repair.

    Thank you for your response but permissions repairs only affect items installed by the OS, such as applications, & not user-created folders. So as expected, repairing permissions has not changed anything.

  5. 0

    Francine Schwieder

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I discovered one problem: Spotlight didn't index files that still had "unknown" as group. I used BatChmod to change everything in my home folder to group:staff, whereupon Spotlight came to life and indexed all the things (which was most of the content of my user folder, since it had almost all come from my Tiger installation) it had left out. What other consequences I will find, only time will tell. So far everything seems normal....

    And I always thought user:francine group:francine was terribly eccentric. Evidently Apple decided to stop thinking quite so Different and go back to the normal UNIX way of things. Too bad that they didn't provide some sort of sub-routine to fix the group ID of files for those of us who did an upgrade over Tiger.

    Francine

    User uploaded file

    Francine
    Schwieder

  6. 0

    R C-R

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Francine,

    Thank you very much for your reply. But I am a little confused by it, or at least by my own ignorance. Are you saying that the default for a new user account created in Leopard is to make it a member of the staff group, and/or not to create a new group (of one) with the same group ID as its UID? If so, is this for both standard & admin account types or just one or the other?

    FWIW, I observed something related to the Spotlight behavior you mentioned. Upon creating my Leopard install on a freshly erased partition on an external FW drive (I haven't committed to installing it on the internal yet) & using Migration Assistant to copy everything possible from the internal to it, I did
    not notice Spotlight doing any reindexing, although it seemed to work for the few searches I did. I thought that odd but didn't investigate -- too many new things to check out in Leopard. 🙂

    But today I started checking out the new (or at least now GUI-friendly) account sharing options in Leopard. I created my first shared account in the Sharing System Preferences while creating a shared folder, not directly in the Accounts one. I chose the user from my Address Book entries, should that make a difference. Within a a minute the G5's fans spooled up, scaring the wits out of me until I realized it was because Spotlight reindexing had started up.

    The shared account has the same name (& is the same person) as the second user account created & subsequently deleted (in Tiger) & may have been the origin of the "unknown user" group label for some of my files -- I had fiddled around with giving that user account group access to some files in the early days of using Tiger. So I surmise I've seen the same or very similar Spotlight behavior once the "unknown" group was no longer needed: as it turns out, the new shared account has the same UID (502) as the old deleted standard user account, that being the first available 500 series UID in the Leopard install.

    For me this was unplanned, but it suggests that anybody can resolve the "unknown user" group issue by creating a shared user with the same UID as the unknown user, assuming they can figure out what that UID is.

    What do you think? Does this seem plausible?

  7. 0

    Francine Schwieder

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    You aren't the only one confused, so am I! Like you I was very involved in trying out this and that, and reading about Leopard. I came across the thread discussing the Unknown Group, checked, discovered it applied to me, and started dinking around to make my group membership staff. It was only AFTER this that I discovered my files in the Leopard home folder weren't showing up in Spotlight. I hadn't realized anything was amiss since I installed Leopard over a clone of my Tiger install, thus I was happily pulling up files by name in Spotlight, with occasional puzzlement about why they kept getting saved somewhere other than the new model home. I think now it was because what Spotlight was finding was the original version, not the version in my Leopard home folder.

    There are two ID issues involved: first is the User ID, in my case it is always 501. Second is the Group ID. In Tiger, and I think Panther (I believe this is where the change was done), the Group was the same name. Thus, you were user:yourname and group:yourname, and I don't know what the GID number was for that. Leopard has no idea what in the world it is, so it assigns the group ID name of "unknown" with a GID of 99 (anyway, that is what this file "/private/etc/group" says the number is). When I was trying to sort this out I gave MYSELF the staff group, GID 20. But most of my FILES were still showing as group "unknown" with a GID of 99. Whether Spotlight then dumped the data for all those files, or had never indexed them to start with I just don't know.

    For me, simply running a batch change of the group on my entire user folder, so that the group I am in and the group for the files is now the same, sorted the problem. I'm afraid my grasp of all this is pretty shaky, and my knowledge pretty sketchy. Let's hope someone who actually understands all this will join in!

    Francine

    User uploaded file

    Francine
    Schwieder

  8. 0

    R C-R

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    From what I can tell, GID's for new accounts created in the "middle" OS versions default to a GID equal to the UID & group names are as you described, so normally you should have GID's of 501, 502, etc., each with a user name as the group name & one user per group. (I've verified this behavior in Tiger & assume Panther works the same way.) But if you have migrated user account(s) from early versions of OS X, you may not have unique GID's for them:

    My original "501" account was created in OS 10.1 & has a GID of 20, & that has persisted through migrations first to Tiger & now to Leopard. I have recently verified that this is the same as for a new 'managed,' standard, or admin account created in Leopard. Interestingly, a "Sharing Only" account I created in Leopard has a GID of 61 -- which corresponds to the "localaccounts" group in the Group Database file "/private/etc/group."

  9. 0

    Francine Schwieder

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    This whole issue is very convoluted and confusing, with new bewilderments (at least bewildering to me) turning up every day. I've been participating in several discussions in several different places, and reading everything I could find, and it still isn't clear to me what one ought to do, let alone what the consequences of the various things are. It is clear the situation is causing not only mass confusion, but at least a few operational problems.

    For myself, I simply gave up, cloned my Leopard install to the disk I had been using for Time Machine, and did an erase and install, then let the migration assistant that pops up as the install finishes copy what it wished how it wished from the cloned system. At least things now look consistent: no more "unknown" files, no ACLs where none should be in my home folder, all new files are saved to the apparent new standard: user francine uid 501, group staff gid 20 (of course yesterday I found out even that isn't as straight-forward as one might think, I'll spare your the details).

    Francine

    User uploaded file

    Francine
    Schwieder

  10. 0

    SteveDjokes

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    There's an app called Tinkertool System.

    In this app you can access and remove any ACL (Access Control List) permissions and propagate those. This will remove all these custom permissions you are dealing with.... 501 is the first owner created - if you have created a total number of 4 accounts you will have 501,502,503,504. You can go ahead and change the group ID if you wish - it wont harm your system - I did on my G-Friends CPU - and all that got reset was the Dock and it's contents... Strange - but that is all that happened...

    You can also use the terminal

    type

    man acl

    and read it thru'

    Good Luck

  11. 0

    R C-R

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    SteveDjokes wrote:

    501 is the first owner created - if you have created a total number of 4 accounts you will have 501,502,503,504.

    It isn't quite that simple for me: I have over the years created at least half a dozen user accounts, but deleted all of them except the first 501 admin account at one time or other, since most were created for troubleshooting Tiger issues. They weren't deleted in the order created. Currently, I have the original 501 (admin) & a new 502 (sharing only) accounts, but at one point had 501 (admin), 504 (admin), 505 (standard), & 506 (standard) accounts. The current 502 (sharing only) account user was once (by name) owner of a 503 (standard) account created in Tiger & thus there was once a 503 group. The weird thing is the higher numbered standard accounts were created (last) in Leopard while the 502 & 503 UID's were available, but the 'shared only' account was the only one assigned a UID in that range.

    You can go ahead and change the group ID if you wish - it wont harm your system - I did on my G-Friends CPU - and all that got reset was the Dock and it's contents... Strange - but that is all that happened...

    Well, my 501 account has always had a GID of 20, so I don't want to change it, just to figure out why some files said "You have custom access" in Finder Get Info windows ... & now that Francine has brought it up, why Spotlight kicked in only after the new 502 sharing only account was created.

    You can also use the terminal

    type

    man acl

    and read it thru'

    I will do that. Thank you for the tip.

  12. 0

    SteveDjokes

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Well for instance if you create a whole new account - then log in to it... Go to some folder and set some permissions. Copy some folders to an external firewire drive... etc.. Now log into your "Home" account and check the permissions on some of the folder/files you set while being logged in to the "new" account... This should display custum (ACL) rights...

    Also - if you go to the /LIbrary folder and has three users (System,Admin,Everyone) if you add a user to the permissions - by hitting the "+" icon the you have officially set (ACL) custom permissions. This aint a bad thing...

    If you are bothered by it - get TinkerTool System and delete those ACL (Access Control List) permissions... With Tinkertool you can even "Disable" ACL support for drives of your choice.

    I guess it is a feature that has quite many people confused - incl - me... But I took a week off to get down and dirty with Leopard - I have not figured it out 100% but I am trying....