Permission and ownership

I search the forum and find tons of info about people having trouble with permission and how to resolved. Can anyone share what is permission and ownership. I have use disk repair, but I don't know why it works as it relate to this topic.
Austin

At the risk of repeating what has already been offered:
What are permissions?
Every file and folder on a Mac OS X hard drive has a set of permissions—settings that determine which user(s) have access to each item, and exactly what that access is. For example, permissions dictate whether or not a particular user can open and edit a particular file. But permissions also determine which items the operating system—or specific parts of it—can access and modify, and which files are accessible by applications.
What does repairing permissions do?
The Repair Disk Permissions function—the process that actually performs the task of repairing permissions—examines certain files and folders on your Mac’s hard drive to see if their current permissions settings are what Mac OS X expects them to be; if discrepancies are found, the offending permissions are changed to match the expected settings.
(In Mac OS X 10.3 and later, repairing permissions also performs one other, unrelated, task: If the invisible /tmp symbolic link—which is linked to the /private/tmp directory—is missing, the link will be recreated.)
Why is it necessary to repair permissions?
If permissions on particular files are “incorrect”—i.e., not what Mac OS X expects them to be or not what they need to be for your Mac’s normal operation—you can experience problems when the operating system tries to access or modify those files. For example, you may have trouble logging in to your account, printing, launching applications, or even starting up your Mac. Similarly, if an application—from Apple or a third-party developer—needs access to a particular file or folder to function, and the permissions on that item have changed in a way that prevents such access, the application may not function properly (or at all). The Repair Disk Permissions function can fix such problems by ensuring that certain files have the correct permissions.
There’s also a security element here: Many system-level files have permissions set a particular way so that applications or users that shouldn’t be meddling with those files can’t. If the permissions on certain system-level files somehow get changed so that access to those files is no longer restricted, you’ve got the potential for a major security issue. Repairing permissions can resolve such issues by resetting permissions on those files to prevent unauthorized access.
How do I repair permissions?
The Repair Disk Permissions function is part of Apple’s Disk Utility (in /Applications/Utilities). After launching Disk Utility, select the desired disk—generally your startup disk—in the list to the left, then click the First Aid tab. At the bottom of the First Aid panel, click the Repair Disk Permissions button. (You could instead use the Verify Disk Permissions option to preview any potential repairs before performing them, but for most users there’s little benefit from this extra step.)
Permissions can also be repaired via the shell (Terminal) by using the command sudo diskutil repairPermissions /. However, it’s unlikely that the typical user will ever need to perform the task in this manner. It’s useful if for some reason Disk Utility itself won’t launch, or for repairing permissions on a remote Mac when connected via Remote Login (SSH), but otherwise you’re just as well served using Disk Utility.
How does the Repair Disk Permissions function know what the “correct” permissions are?
When you use Apple’s Installer utility to install software (such as Mac OS X itself or an OS X update), the installation package (the .pkg file you double-click to begin installation, or that Software Update downloads in the background for an automatic installation) generally leaves behind a receipt—a smaller Mac OS X package that includes information about every file installed, including the permissions each file should have. This receipt is placed in /Library/Receipts. When you run the Repair Disk Permissions function, it examines the receipts in the /Library/Receipts directory of the disk being repaired—which means the feature works only on volumes with Mac OS X installed—and compares the information in the receipt with the actual files on your drive. If the Repair Disk Permissions function finds a file with permissions that differ from what a receipt claims they should be, that file’s permissions are reset to their receipt-specified values. (If you’re curious about the information contained in a receipt, the easiest way to view it is to use the utility Pacifist; simply drag and drop the appropriate receipt into the Pacifist window and you’ll be presented with a list of all files installed by the similarly-named installation package, along with each file’s original permissions.)
It’s worth noting here that although the function is called “Repair Disk Permissions,” what is actually happening is that files’ permissions are being reset or restored to a particular state. It’s possible—though not common—for a particular file’s permissions to differ from what a receipt claims they should be without those permissions actually being “broken.”
Are all files affected by Repair Disk Permissions?
No. As you may have inferred from the above description, only those files installed using OS X’s Installer utility and whose installation packages leave behind a proper receipt in /Library/Receipts are affected by the Repair Disk Permissions function. This means that most of the files affected by the Repair Disk Permissions function are system-level files, application files, or system add-ons—not applications installed by drag-and-drop, and not your documents or other user-level files.
If repairing permissions is useful in general, why doesn’t Apple recommend it as routine maintenance?
Apple does, quite explicitly:
It’s a good idea to repair disk permissions as a regular maintenance task after upgrading or installing new software.
That’s taken from Mac Help—in both Panther and Tiger—right on your Mac. Similar statements can be found in other Support articles, one of which is:
http://docs.info.apple.com/article.html?artnum=25751

Similar Messages

  • File permission and ownership problem

    I am trying to resolve some file permission and ownership problems that are left over from using Migration Assistant to set up my iMac from an older iMac. In a terminal session when I use the ls -l command I'm getting a file/directory owner of 504. Sometimes the group is admin and sometimes the group is also 504. I think this is because the owner of the file on the old computer is not present in the new one but I want to be sure before I just change the owner and group.

    The following should give you an indication->
    id -un 504
    or you could try->
    dscl . list /Users UniqueID | grep 504  && echo "User exists" || echo "User does not exist"

  • Permission and ownership in Server 2003 and 2008 file server

    I have an issue but I am not sure if these are the designs of the file server permissions. I have one user who has the modify rights to modify/read and create folders in a share folder. In the share folder, she had created a subfolder; so she should
    be the owner of the subfolder and her security permission is modify. By right, modify does not have the rights to assign the permission to other users but as owner, she does. Does this mean that the folder owner supersede the security? And is this possible
    to avoid this? eg. folder owner but does not have the rights to assign permissions to other user to access. Thanks a lot.

    Hi Thim,
    >>Does this mean that the folder owner supersede the security?
    If the user is the Owner of the folder, he or she should have Full Control permissions to the folder,
    which means the user can do anything to the folder.
    >>And is this possible to avoid this? eg. folder owner but does not have the rights to assign permissions to other user to access.
    As far as I know, unless we deprive the user of the ownership, we can't achieve this.
    Regarding file and folder permissions, the following article can be referred to for more information.
    File and Folder Permissions
    http://technet.microsoft.com/en-us/library/cc732880.aspx
    Best regards,
    Frank Shen

  • HT2589 Someone is using itunes with my credit card without permission and I want my card number removed.  Ive been trying to get this fixed for months. Im at the end of my paitience.

    Someone is using iturnes with my credit card without my permission and I want my credit card number removed.  I've been trying to get this matter resolved for months.  I've lost all patients with this matter.  I want my credit card number removed from your business. 
    Virginia Mezger
    <Personal Information Edited by Host>

    Please be aware that you are not communicating with Apple when you post in these forums. The only people who will reply to your posts are we your fellow users.
    Since you don't say what resources and methods you've been attempting to get this matter resolved, it's difficult to offer suggestions. But if your credit card has been used without your permission, your primary recourse should be to your credit card company to report the unauthorized charges and have them issue you a new credit card. If your card has been compromised such as to make unauthorized charges on the iTunes Store, it's highly probably that it can be used elsewhere.
    As to removing the card number from your iTunes Store account,  see:
    http://support.apple.com/kb/HT1918
    You should be able to change or remove the card information there. If not, go here:
    iTunes Support
    and follow the instructions to report the issue to the iTunes Store, if you have not done so already. If you have, please post back with a summary of what they told you and perhaps someone can offer additional suggestions as to how to proceed.
    Regards.
    Regards.

  • Since installing Yosemite and Photos I can now no longer drag and drop a photo in an email, as I have always done. I repaired permission and restarted a number of times. still not working... Help?! Thanks, Michael

    Since installing Yosemite and Photos I can now no longer drag and drop a photo in an email, as I have always done. I repaired permission and restarted a number of times. still not working... Help?! Thanks, Michael

    What happens if you use the Share button and select Mail?
    What happens when you try? I had to hold there photo there for a short period before it would load.

  • I want to change my password but the system is not sending me message to reset my password. pls help someone is using my password without my permission and i want to change my password.

    i want to change my password but the system is not sending me message to reset my password. pls help someone is using my password without my permission and i want to change my password.

    If you are talking about your Apple ID password, make sure it IS your apple ID.
    In the past 24 hours, I have received two emails "How to reset your Apple ID password". I  had not requested any change and I finally realized someone else is trying to reset the password. I have had this Apple ID since 2009 so I am not using someone else's ID.
    Again, if you are not receiving the email to reset make sure you have the right ID - it might be going to the email linked to the account, and it might not be yours.

  • Trying to repair permission and I always get this: Permissions differ on "Applications/Safari.app/Contents/Resources/Safari.help/Contents/Resources/inde x.html"; should be lrwxr-xr-x ; they are -rwxr-xr-x .

    Trying to repair permission and I always get this:
    Permissions differ on “Applications/Safari.app/Contents/Resources/Safari.help/Contents/Resources/inde x.html”; should be lrwxr-xr-x ; they are -rwxr-xr-x .
    I even fresh install the system and every time I do repair the permission I always end up with this even though it said repaired.
    I figure this is the problem my laptop, sometime it wont save files or documents and it goes in limbo and had to force shutdown and have to restart on the
    booth drive to have it permission repair. I just updated to 10.9.3 and will see if this stop the crashing but repair permission notice is still the same.
    Any feedback please....Thanks
    Model Name:          MacBook Pro 13-inch, Mid 2010
      Model Identifier:          MacBookPro7,1
      Processor Name:          Intel Core 2 Duo
      Processor Speed:          2.4 GHz
      Number of Processors:          1
      Total Number of Cores:          2
      L2 Cache:          3 MB
      Memory:          4 GB
      Bus Speed:          1.07 GHz
      Boot ROM Version:          MBP71.0039.B0E
      SMC Version (system):          1.62f7
      Serial Number (system):          7302895ZATM
      Hardware UUID:          0B62E320-214C-5EE8-9EBC-106E01BE083D
      Sudden Motion Sensor:
      State:          Enabled

    AmanteDesign wrote:
    Trying to repair permission and I always get this:
    Permissions differ on “Applications/Safari.app/Contents/Resources/Safari.help/Contents/Resources/inde
    I see the same thing since the general release of 10.9.3. This did not occur in prior versions.

  • Permission and access of applications

    I have a principle question to permission and access, (in German Rechte und Zugriff)
    I have create a list of my Applications with there permission.
    I found 7 different groups of name of access, view to apps from admin window.
    There are alway 3 different permissions per application
    "My name" ( I ) = Admin.
    Read&Write or this is no shown
    Joachim = Standarduser.
    Read&Write or this is no shown
    staff
    Only Read or this is no shown
    System
    Read&Write or Only Read or this is no shown
    wheel
    Read&Write or this is no shown
    admin
    Read&Write or Only Read or this is no shown
    everyone
    Read&Write or Only Read or this is no shown
    All 40 Apple Application have:
    System = Read&Write
    admin = Read&Write
    everyone = Only Read
    Only by "System default" there is:
    System = Read&Write
    wheel = Read&Write
    admin is no shown
    everyone = Only Read
    Service Applications I have no checked.
    All Apple Applications the same systematics. The later buyed apps Aperture and iWork have the same permissions like the apps which are installation first of my Mac.
    By the other non-apple-applications there is a chaos.
    Have someone an idea what the systematic of permissions is.
    Sometime I have installed the apps as standard user with rights of admin, that is possible.
    My Mac works well but I would learn why is this chaos.
    Thanks for helps or have someone a link to help document.
    Jochen (.de)

    These different permissions may have been created by you making changes. For example, "everyone" should never be r/w, but should be read-only. The DevonThink was probably installed via Drag and Drop in which case it would take on these permissions:
    Owner=you with r/w privileges
    Group=you or staff with r/w or read-only privileges
    Everyone is read-only
    The key thing here is that for all users to be able to run an application, then the application must have the owner set to system with r/w privileges. The other users can be read-only. The admin group is usually provided r/w privileges.
    If an application has the owner set to a username, then only that user can access the application. For a single user machine where the user logs in either as admin or standard with the same username, then it doesn't really matter. It would only matter if a different user tried to use the application but did not have membership in the group.
    Everyone is set to read-only because you don't want 'everyone' to be able to access and change files without supervision.
    All 'admin' user accounts belong to the admin group. Only admin users who are also 'super users' have system-wide access.

  • I have an error in Verify disk permission and i can not fix it

    I have an error in Verify disk permission and i can not fix it ,is there any solutions ?

    I have 38 GB (other) in my storage ,I have 120 GB storage and this other part bothers me,is there any suggestions please ?

  • Pull forward Journals and Ownership via Rules

    Hi,
    Is it possible to pull forward the Journals for 1 scenario towards the other scenario? By rules? Same question for the ownership.
    I can full forward data from one scenario towards the other but the Journals and ownership is a different case.
    Thanks!
    Gr,
    Bob

    Hi Bob,
    We have done the pull forward of journals actually with metadata by setting the ZeroViewForAdjs property for Scenarios to Periodic. If you choose to do so, you of cause need to evaluate that it fits your application design as a whole.
    Ownership is a bit trickier, I don't think there's any good solution with rules, because it might change from period to another and you don't want the new values to be overwritten by the old ones. What you are looking for one would of course achieve nicely by changing the account type of [POWN] to BalanceRecurring, but it simply doesn't change even if you would load metadata with such a change into the application. At least this is the case until versions 11.1.2.1.
    Kind regards,
    Lauri

  • Disk Utility can't "Verify Disk Permission" and "Repair Disk Permission"

    I booted up the Leopard 10.5.5 server from the Install Disc, and tried to do disk checks on all drives using Disk Utility.
    When the system drive was selected all the "Verify Disk", "Repair Disk", "Verify Disk Permission" and "Repair Disk Permission" functions are able to perform, however, if the non-system drives are selected only "Verify Disk" and "Repair Disk" are able to perform, the "Verify Disk Permission" and "Repair Disk Permission" are GRAYED OUT ! and UNABLE TO perform the permission check and repair!! Any idea ?

    Hi, I'm having a problem could be related. I've a 3 years old Xserve (not intel) with 3 HD managed by the apple original RAID board, all that running Mac OS X 10.4.
    I remotely manage the server from my mac running OS 10.5.6 and Server Admin 10.5.3.
    Well, I simply cannot propagate permissions because when I do it, Server Admin freezes and i must force it to quit. Obviously, privileges are not propagated.
    All that di NOT happen 1 month ago when i was "happily" running Mac OS X 10.3.x and Server Admin 10.3.x. Upgrading has been a big boomerang.
    Any idea? Thanks

  • Can't boot into OS X.6 after changing permissions and ownership

    Hi,
    I'm in the process of migrating to OS X.7 - booted into Lion I changed permissions and ownership on the other disk that I use to startup into OS X.6. I set it to "ignore ownership on this disk" and granted read and write access to "everybody". Restarting my Mac into OS X.6 now doesn't work anymore - the grey spinning circle spins forever.
    Does anybody know how to fix this so that I can boot back into OS X.6? I'd be real thankful...
    Best
    Jurgen

    Thank you for your reply. I was able to repair permissions on the failing disk using the OS X.7 Lion recovery volume - quite amazing that one can do that.
    However the internal disk of the iMac that has OS X.6 on it still fails to boot.
    Any other suggestions? I'm a bit desperate to use OS X.6 because a few apps that are vital to me do not run under OS X.7 (they need Rosetta).

  • New Mac with major permission and disk-write problems

    Right, so I'm pretty new to Mac, after getting my first Mac computer (a 17-inch MacBook Pro) at the end of January this year. It's been great so far and I love the thing, but I've suddenly encountered some crazy problems which I'm pulling my hair out over because I have tried everything to fix them, and have had no luck.
    I'll try to include as many details as possible, and I'm prepared to bear with anyone who asks me about something I've alrady tried, just so I can get this sorted.
    Okay, so first of all, the main problem seems to be with permissions, mostly with disk-write permissions. Any apps that I want to install that required keychain access will no longer install. I enter my keychain password, hit Return, and the dialog box closes without continuing. So I hit "Install" again and it becomes a never-ending cycle of entering my password to no avail. Now, this happens with ANY application that requires keychain access to install. It is not limited to any particular application. I know my password is right because the box closes, and if I enter it wrong, the dialog box shakes because it is incorrect.
    Furthermore, it seems keychain access is problematic in other apps. If I want to authenticate something, it will do the same thing as I mentioned before, meaning I get nowhere with the application.
    From here, it gets worse. If I download something (anything), then restart my computer, it is still there. As it should be. However, if I delete an APPLICATION (not just any file) OR change preferences for some programs (one in particular that I specifically don't want starting up on.... startup), including through System Preferences>Users & Groups>Login Items, they will not save. This is driving me insane. For instance, I downloaded some free apps from the Mac App Store to try out, but decided I didn't want them. I tried to deleted them from the app folder and succeeded. Emptied trash. Gone. Restart, and.... they're back? So I tried to uninstall them via the Mac App Store, once I found you could do that. Again, it didn't work. Any Login Items preference changes don't stay after a restart.
    Originally, none of this was a problem and everything was working fine. The first sign that something was wrong would be Apple Mail often asking for passwords, usually for my Hotmail accounts, saying that they were rejected by the server (but are correct passwords, I get the emails from the accounts, and the passwords are always accepted once I type them in, only to be asked for them some time later on for no apparent reason). At the time, I tried to repair the keychain, tried deleting and recreating the mail account entries and what not, but nothing helped. It still happens, but at the time, it was more of a niggly thing than an outright problem.
    I should also mention that I did use BootCamp to install Windows 8 on a small partition, but after I couldn't boot back into Mac (I didn't realise you had to use the Option key whilst booting), I found out that you had to hold the Option key to get back into Mac, then used BootCamp to get rid of Windows. Everything was fine so far. Until I decided to reinstall Windows 8 with BootCamp. This is where things started going wrong. I decided to install a bootloader to make it easier for me to boot between the two systems. I was tossing up between rEFIt and Chameleon, and decided that rEFIt would be the best for my needs. So I downloaded and installed it, which seemed to go fine. Until I restarted. Mac would endlessly load (the spinning grey dots with the Apple logo).
    Now, I actually managed to fix this, but I should probably go into more detail. First of all, holding the option key and selecting my Mac partition would allow me back into Mac, and same with Windows 8. At this point, I decided to uninstall Windows 8 to try fix my problems, except now BootCamp was giving me errors. I believe it was something about being unable to unmount the disc, but it may have been a different error. I don't entirely remember. So then I decided to try getting rid of rEFIt. I followed the instructions on the official site but it didn't work. So then I tried deleting the files with root (sudo) access through terminal. Which also failed....
    So to the Recovery partition. Booting into Disk Utilities, I repaired permissions, which worked fine, and repaired the disk. I believe I had run the disk repair a few times before to try to fix BootCamp when it stopped working. Anywaym it had worked before, but this time, it said that it was corrupted and could not be repaired. Something about needing to reinstall Mac OS X. With all my files on this computer and currently nothing to back it up with (eventually I will have something to do backups with, but it'll have to wait a few months), I'm not going to do that.
    Finally, I managed to delete the rEFIt files through Terminal within the Recovery partition. I ran permission repair and disk repair again to clean anything up. Disk repair gave me the same error, but now I could get back into Mac without holding the option key on every **** boot.
    Now more problems had presented themselves. I decided that the lock under Login Items was probably preventing me form successfully changing my startup items. Trying to unlock it did the same thing as I previously mentioned. Type in my password, keychain accepts it, then nothing happens. The keychain settings were already defaulted so that keychain would stay unlocked after authenticated, and all stuff like that. Using "Get Info" on anything has permissions locked and again, I cannot unlock to change them, although looking at a PDF file just now, whilst still locked, it would allow me to add or remove users, so maybe that's not completely accurate. I believe I tended to look at the system folders though, and my name wasn't under ownership, although I don't believe it was meant to be, but I was hoping that maybe that would fix the problem. I guess not.
    At this time, I still had my Windows 8 partition sitting around and couldn't get rid of it. I heard of the manual way to do it through Disk Utility. I tried this in Mac OS X, and through the Recovery partition, but neither worked. An error about being unable to unmount the drive. I finally found a way to remove it. Honestly, I don't completely remember how I did it, but I believe it was through a command line, uh.... command. Now I had free space that I couldn't use to expand my Macintosh HD partition back to full size, again with the unable to unmount error. Finally, I fixed this by booting from a Mac OS X installation disc that I happened to have, and using Disk Utility off of that. After that, Disk Utility no longer gave me errors for disk repair.
    However, my other problems all still remained. I had written a little list of things I found on the internet for fixing my problems. One solution was to use "resetpassword" through terminal under the Recovery partition, then select Macintosh HD and select "Reset Home Directory Permissions and ACLs". That didn't work until I tried it through the Disk Utility on the Mac OS X installation disc. That worked, and once I was back into Mac, Spotlight started indexing again. However, nothing else had happened.
    I should also mention that keychain access isn't completely non-existent for me. Setting up a new WiFi connection worked for me (that is, connecting to a new network), but now every time I connect to the network, I have to authenticate it. However, it does accept my keychain password and eventually connect.
    Now, another thing on my list to try was single-user mode, and using "/sbin/fsck -fy" until everything was okay. Well, the first time, it found a bunch of errors, then fixed itself up. Then it was all okay. But nothing had changed. So trying again, I this time used ?/sbin/mount -uw /" which I believe is meant to allow writing access to the drive. Now when running "/sbin/fsck -fy", I had an error. Specifically, "Journal need to be replayed but volume is read-only".
    So that's pretty much where I am up to at the moment. It seems to be a poblem with write permissions, possibly among other things. If it was Windows, I might be able to work it out easier, but being new to Mac, I'm still finding my way around. I guess this is a good learning experience, but it's not fun to have to deal with it so early on.
    If anyone can help me, I'd greatly appreciate it. I have tried many things, so if you suggest something that I have tried and possibly forgot to mention, I'll let you know, but any help is still helpful, even if only eliminating possible problems/causes/solutions.

    Actually you first post is so long that most people just glance at it and move on. To say the least you are very verbose.
    Your problem stems from something going wrong with permissions, as you know. How and why that happen is usually a user error of some type.
    You can try to repair permissions and see if that corrects it. If not I will leave other options to someone that may know more about the permission system on a Mac.

  • Serious trouble with permissions and ownership

    My archive/install/Migration Assistant upgrade to Leopard has turned into a nightmare concerning 'ownership' of my files and hard drives.
    To make a long story short, after many many problems wherein files and drives were 'owned' by me but unaccessible to me (often with two ownership qualities attributed to me- one "Read & Write" and the other "Custom", a situation I could not edit or change) I restarted with the installer disc and repaired permissions on my Leopard startup partition. It took several hours and went through thousands of files identifying "ACL" problems.
    Now all my drive icons except for my startup disc have locks on them and I can't write to them even though I supposedly have permission. Carbon Copy Cloner fails to copy to the locked drives*.
    This situation now obtains EVEN WHEN I BOOT IN TIGER: my drives have little lock icons on them. I thought I could revert to Tiger to fix this, but apparently I'm stuck. I need to know how to "unlock" my drives (and eventually return to Tiger).
    Information on a drive with the lock icon, from Disk Utility (10.4.10):
    Name : Files
    Type : Volume
    Disk Identifier : disk0s3
    Mount Point : /Volumes/Files
    File System : Mac OS Extended (Journaled)
    Connection Bus : Serial ATA 2
    Partition Type : Apple_HFS
    Device Tree : /PCI0/SATA@1F,2/PRT0@0/PMP@0/@0:3
    Writable : Yes
    Universal Unique Identifier : 7975DD60-83DD-39BC-99BC-7C5DF1072F8B
    Capacity : 122.1 GB (131,088,871,424 Bytes)
    Free Space : 48.0 GB (51,527,860,224 Bytes)
    Used : 74.1 GB (79,561,011,200 Bytes)
    Number of Files : 70,994
    Number of Folders : 5,440
    Owners Enabled : Yes
    Can Turn Owners Off : Yes
    Can Repair Permissions : No
    Can Be Verified : Yes
    Can Be Repaired : Yes
    Can Be Formatted : Yes
    Bootable : Yes
    Supports Journaling : Yes
    Journaled : Yes
    S.M.A.R.T. Status : Verified
    Disk Number : 0
    Partition Number : 3
    * Typical CCC log entry after failing to copy:
    03:53:58 The target volume has ownership enabled.
    03:53:58 Enabling Access Control Lists on the target volume...
    03:53:58 The target volume has Access Control Lists enabled.
    03:53:58 Authenticating...
    03:53:58 Initiating synchronization engine...
    03:53:58 Preparing to copy, total items to consider: 8
    03:53:58 Build time: 0.013
    03:53:58 Copying files...
    03:53:58 rsync: recv_generator: mkdir "/Volumes/Files/Users" failed: Operation not permitted (1) (51)
    03:53:58 rsync: Some errors were encountered during the backup., Error code: 51

    Email sent. Many thanks.
    The Terminal output:
    Last login: Thu Nov 1 11:27:35 on console
    Macintosh:~ etnier$ cd /
    Macintosh:/ etnier$ ls -le
    total 40997
    drwxrwxr-x+ 121 root admin 4114 Oct 31 09:04 Applications
    0: user:etnier allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
    -rwxrwxrwx@ 1 root admin 10240 Oct 31 13:24 Desktop DB
    0: user:etnier allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity
    -rwxrwxrwx@ 1 root admin 10850 Oct 30 05:28 Desktop DF
    0: user:etnier allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxrwxr-t+ 58 root admin 1972 Oct 29 18:30 Library
    0: user:etnier allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxr-xr-x@ 2 root wheel 68 Oct 29 11:34 Network
    0: user:etnier allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxrwxrwx+ 4 root admin 136 Oct 29 11:03 System
    0: user:etnier allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
    lrwxrwxrwx+ 1 root admin 60 Oct 29 10:18 User Guides And Information -> /Library/Documentation/User Guides and Information.localized
    0: user:etnier allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxr-xr-x+ 6 root admin 204 Oct 29 15:44 Users
    0: user:etnier allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxrwxrwt@ 12 root admin 408 Nov 1 11:27 Volumes
    0: user:etnier allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxrwxrwx@ 4 root admin 136 Oct 29 10:17 automount
    0: user:etnier allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxr-xr-x@ 40 root wheel 1360 Oct 29 10:59 bin
    0: user:etnier allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxrwxr-t@ 2 root admin 68 Dec 7 2006 cores
    0: user:etnier allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
    dr-xr-xr-x 2 root wheel 512 Nov 1 08:49 dev
    lrwxr-xr-x@ 1 root admin 11 Oct 29 10:59 etc -> private/etc
    0: user:etnier allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity
    dr-xr-xr-x 2 root wheel 1 Nov 1 08:50 home
    lrwxrwxrwx@ 1 root admin 9 Oct 29 10:14 mach -> /mach.sym
    0: user:etnier allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity
    -rw-r--r--@ 1 root wheel 10243756 Oct 10 00:38 mach_kernel
    0: user:etnier allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity
    -rw-r--r--@ 1 root wheel 10696809 Oct 10 00:38 mach_kernel.ctfsys
    0: user:etnier allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity
    dr-xr-xr-x 2 root wheel 1 Nov 1 08:50 net
    drwxr-xr-x@ 6 root wheel 204 Oct 29 11:05 private
    0: user:etnier allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxr-xr-x@ 66 root wheel 2244 Oct 29 11:02 sbin
    0: user:etnier allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
    lrwxr-xr-x@ 1 root admin 11 Oct 29 10:59 tmp -> private/tmp
    0: user:etnier allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxr-xr-x@ 11 root wheel 374 Oct 29 12:23 usr
    0: user:etnier allow list,addfile,search,add_subdirectory,deletechild,readattr,writeattr,readextattr,writeextattr,readsecurity
    lrwxr-xr-x@ 1 root admin 11 Oct 29 10:59 var -> private/var
    0: user:etnier allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity
    Macintosh:/ etnier$
    Macintosh:/ etnier$ cd /Volumes
    Macintosh:Volumes etnier$ ls -le
    total 8
    drwxrwxrwx+ 14 root admin 544 Oct 31 08:45 BAKS
    0: user:etnier allow list,addfile,addsubdirectory,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxr-xr-x@ 38 etnier etnier 1360 Nov 1 03:39 Files
    0: user:etnier allow list,addfile,addsubdirectory,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxrwxrwx@ 58 etnier etnier 2040 Oct 29 18:30 Junk 1
    0: user:etnier allow list,addfile,addsubdirectory,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxrwxrwx@ 52 etnier etnier 1836 Oct 30 09:02 Junk 2
    0: user:etnier allow list,addfile,addsubdirectory,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxrwxrwx@ 31 etnier etnier 1122 Oct 31 09:31 Junk 3
    0: user:etnier allow list,addfile,addsubdirectory,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxrwxrwx@ 93 etnier etnier 3230 Oct 31 09:03 Junk 4
    0: user:etnier allow list,addfile,addsubdirectory,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxrwxrwx@ 20 etnier etnier 748 Oct 31 09:03 Junk 5
    0: user:etnier allow list,addfile,addsubdirectory,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxrwxrwx@ 83 etnier etnier 2890 Oct 31 09:03 Junk 6
    0: user:etnier allow list,addfile,addsubdirectory,readattr,writeattr,readextattr,writeextattr,readsecurity
    drwxrwxrwx@ 35 etnier etnier 1258 Oct 29 14:43 Junk 7
    0: user:etnier allow list,addfile,addsubdirectory,readattr,writeattr,readextattr,writeextattr,readsecurity
    lrwxr-xr-x 1 root admin 1 Nov 1 08:50 Macintosh HD -> /
    Macintosh:Volumes etnier$

  • File permissions and ownership questions

    Hi all,
    I'm a bit confused by the file permissions in Snow Leopard. In particular, whenever I create a folder, there is always a group permission assigned to "staff".
    1) how is "staff" different from "everyone"?
    2) how come if I remove the group permission for "staff", I can't add it back? It doesn't seem like the "staff" group actually exists (it doesn't show up in the user/group dialog)
    And finally, does anyone know why ownership is so weird on removable drives? It seems like the "owner" of a folder created an a removable drive is just whoever is logged in at the time. So, if I log in as UserA and do an ls, I see the owner as UserA. If I log in as UserB, I see the owner as UserB.

    bmm727 wrote:
    Hi all,
    I'm a bit confused by the file permissions in Snow Leopard. In particular, whenever I create a folder, there is always a group permission assigned to "staff".
    1) how is "staff" different from "everyone"?
    staff is the default group that includes all users with accounts on your computer. everyone means everyone including remote users connecting as guests if you have file sharing on who don't have user accounts on your computer.
    2) how come if I remove the group permission for "staff", I can't add it back?
    in short, because GUI for changing permissions is really messed up in snow leopard.
    It doesn't seem like the "staff" group actually exists (it doesn't show up in the user/group dialog)
    it does exist, it's just not offered as an option in that dialog. see my comment above about GUI being messed up.
    Furthermore, please never delete staff from permissions this way. on top of being messed up GUI for changing permissions is buggy in snow leopard and when you remove staff from permissions that way the group on the item in question changes from staff to wheel (which is why you have to unlock the lock with your admin password in order to do this). this is wrong in most instances as only root belongs to the group wheel.
    And finally, does anyone know why ownership is so weird on removable drives? It seems like the "owner" of a folder created an a removable drive is just whoever is logged in at the time. So, if I log in as UserA and do an ls, I see the owner as UserA. If I log in as UserB, I see the owner as UserB.
    it's not true for all removable drives. it's only true if a drive has ownership disabled (can be done in the get info popup) or if it's formatted FAT. all thumb drives are formatted FAT by default. FAT is an old windows file system which does not understand POSIX permissions and treats everything as read+write by everybody.

Maybe you are looking for

  • Clustering across File systems

    Folks!           I have a question... Does Weblogic support a clustering env. across           filesystems. We are running into this problem. We are using the NES proxy           lib to switch between two weblogic app server. If both are started from

  • Outlook 2010 - Exchange 2013 - Meeting request "from" field

    We have a shared mailbox that the company uses, each user has full access to the mailbox, within this mailbox is a calendar. If person A creates a meeting in this calendar and invites person B, when person B accepts the acceptance goes to the inbox o

  • Edited Elements file doesn't render

    New LR4 user. After editing in Elements the edited file doesn't render in LR although I can see it as it was before editiing? Help please!

  • ITEM SETUP 및 ITEM에 관해 자주 하는 질문과 대답 - 2

    제품 : MFG_INV      작성날짜 : 2005-01-26      ITEM SETUP 및 ITEM에 관해 자주 하는 질문과 대답 - 2 ==================================================== PURPOSE Item Setup에 관한 내용과 고객이 자주 질문하는 Item 관련 내용을 정리하여 고객의 문의 사항을 해결할 수 있다. Explanation 1.Mater level에서 Organization

  • HT4528 What do I do if iTunes can't connect to my iPhone?

    Somebody help. I was using my phone and all of a sudden the Activate your iphone screen came on and now it doesn't let me to do anything BUT when I try to acitvate it, it says "Apple server is temporaily unavailable. Help anyone?