Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #58234

Re: Repair Disk Permissions

Show all headers | View raw

On 2014-03-30, jgras1970@gmail.com <jgras1970@gmail.com> wrote:
> Are the following kind of messages normal, when repairing disk
> permissions?  Warning: the SUID file
> "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAgent"
> has been modified and it will not be repaired.
>
> This has stroke me because I don't use RemoteManagement.  I have not
> installed anything except an antivirus the last 2 years.
>
> Why file permissions get changed without doing anything for it?
>
> Thanks in advance for the given help. Bye

Disk Utility's Repair Permissions function isn't as magical a tool as a
lot of people seem to assume. It's a very simple tool that is meant to
reset the states of ownership and permissions of *specific sets of
files*, and *only* those files listed in the receipts of specific
software in the receipts folder. This receipts folder is located at
/Library/Receipts in Mac OS X versions prior to 10.6, and was moved to
/private/var/db/receipts starting with version 10.6.

Repair Permissions reads the contents of each receipt in the receipts
folder to find out which files and folders it should examine. Receipts
are typically created by software installers that use the Mac OS X
built-in /Applications/Utilities/Installer program to install a software
package, though they may be placed into the receipts folder by other
means as well. Receipts typically contain a "Bill of Materials" file
that lists of each important file and folder in the installed software
package, along with the expected ownership and permissions those files
and folders, according to the install package.

Repair Permissions examines only those files listed by these receipts.
This means the files in your home folder and the files in the local
domain (/Library for instance) are *not* examined. 

The Repair Permissions tool has a rather serious design flaw: it does
not know how to resolve cases where multiple receipts list the same file
or folder with differing ownership and permissions. This actually
happens fairly frequently, particularly when more than one software
package installs and uses a shared library or other system resource that
happens to be used by another software package. If there are multiple
receipts that list a given file or folder, and the expected ownership
and permissions differ between those two receipts, Repair Permissions
will encounter the first receipt, change the ownership and permissions
to honor that receipt, then encounter the second receipt and change the
ownership and permissions to honor the second receipt. This typically
manifests itself in Disk Utility's Repair Permissions log as a
file/folder that never seems to be actually repaired, flipping back and
forth between two states.

Once you understand how it works, you see Repair Permissions is not half
as useful or magical as a lot of people seem to believe. I wish more
people understood this - we probably wouldn't see so many Mac users
running Repair Permissions at the drop of the hat or on a regular
schedule as we see so often.  ; )

Bottom line: If you are not experiencing problems with a specific piece
of software listed in the receipts folder, there's no reason to run
Repair Permissions.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Back to comp.sys.mac.system | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Repair Disk Permissions jgras1970@gmail.com - 2014-03-30 11:07 -0700
  Re: Repair Disk Permissions Jolly Roger <jollyroger@pobox.com> - 2014-03-30 19:08 +0000
    Re: Repair Disk Permissions Howard.not@home.com (Howard) - 2014-03-31 17:38 +0100
      Re: Repair Disk Permissions nospam <nospam@nospam.invalid> - 2014-03-31 13:40 -0400
      Re: Repair Disk Permissions Jolly Roger <jollyroger@pobox.com> - 2014-03-31 17:41 +0000
        Re: Repair Disk Permissions Howard.not@home.com (Howard) - 2014-03-31 21:58 +0100
          Re: Repair Disk Permissions nospam <nospam@nospam.invalid> - 2014-03-31 17:36 -0400
          Re: Repair Disk Permissions Jolly Roger <jollyroger@pobox.com> - 2014-03-31 22:44 +0000
          Re: Repair Disk Permissions Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-03-31 23:21 +0000
  Re: Repair Disk Permissions Frank <gno52@windstream.net> - 2014-04-02 02:47 -0700
    Re: Repair Disk Permissions M-M <nospam@ny.more> - 2014-04-02 08:47 -0400
      Re: Repair Disk Permissions nospam <nospam@nospam.invalid> - 2014-04-02 09:17 -0400
    Re: Repair Disk Permissions nospam <nospam@nospam.invalid> - 2014-04-02 09:17 -0400
    Re: Repair Disk Permissions Michael Vilain <vilain@NOspamcop.net> - 2014-04-02 06:37 -0700
    Re: Repair Disk Permissions Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-02 14:16 +0000
    Re: Repair Disk Permissions Jolly Roger <jollyroger@pobox.com> - 2014-04-02 16:28 +0000

csiph-web