Re: Leopard Repairing Permissions?

On Fri, 14 Nov 2008 13:15:26 -0600, JZ wrote (in article
<JZ-627C5C.13152614112008@xxxxxxxxxxxxxxxxxxxxxxxxx>):

Do others find that it takes a lot longer under Leopard? I repaired them
last night and its still taking about 15 minutes just 12 hours later and
the computer was off all night. Many people say permissions don't even
matter under Tiger but I wonder if its more important for them to be
"right" under Leopard?

I asked a good friend to comment. This friend is one of the very few persons
outside of Apple that has been certified as a Leopard Server expert. Here is
what he had to say in regards to permission repair in Leopard....

====================

Repair permissions on a live running OS is very very tricky.  The entire OS
depends entirely on permissions to govern who can twiddle with what, and to
what extent. Any improper permissions can result in anything from quirky
behavior, unsaved preferences or documents, inability to read cache's or
toolboxes, or even your own documents.  Worse yet, it can make needed parts
of the OS unreachable -- often at the worst times -- rendering your machine
erratic -- or inoperable.

Under Tiger, the database was extensive but not exhaustive.  Under Leopard,
the database is very very complete for all System and User components.  For
instance on my MacBook Pro, I have 979886 files.   Every time I repair
permissions, the Disk Utility must inspect each one, how it relates to other
associated files, and  how the permissions are 'inherited' thru file
structure.

In Tiger this was simple.  POSIX permissions were the only ones used, and the
rules were quite simple.

Under Leopard, Apple began a transition to the more granular ACL (Access
Control List) permissions.  That often means having to deal with and
translate the interaction between the two.  It is also why you often see some
warnings about 'unexpected ACL found' for Network etc. at times.  Later Apple
OS's will forego POSIX in favor of the evolving ACLs which are far easier to
configure and maintain.

During this UGLY transition, Disk Utility is having to hum, chew gum, jump
rope, and recite poetry whilst conforming almost a million lookups.... it
just takes time.  And many users cancel the repairs as they are being done
--- NEVER EVER DO THAT. Or worse yet, they never repair them.

There is no better way to ensure a healthy machine than proper OS maintenance
-- and that includes repairing permissions while SAFE BOOTED, before and
after the installation of any OS patch, update, or application install or
patch.

I have had Apple Geniuses argue 'that for most users' that my suggestion is
overkill and a waste of time.   Point:  In five years -- on ANY of my three
machines -- I have never had an OS or application failure -- even on
Microsoft.  Coincidence?  Perhaps.  But as long as it works -- I'll keep
doing it.

====================

--
James Leo Ryan ..... Austin, Texas ..... taliesinsoft@xxxxxx

.

Relevant Pages

  • Re: Security Update 2006-003: What a disaster?
    ... Has anyone else had trouble with Security Update 2006-003 on their *Intel* ... Repair your hard drive. ... Boot off your Mac OS X installation CD/DVD and run Disk Utility ... permissions, but it segregates bad permission files, dumps your cache ...
    (comp.sys.mac.advocacy)
  • Re: 10.6 After Two Days - Just Excellent
    ... permission repair is at least TWICE and maybe three times as fast as ... When Apple tells me there is a permissions problem, ...
    (comp.sys.mac.advocacy)
  • Re: 10.6 After Two Days - Just Excellent
    ... permission repair is at least TWICE and maybe three times as fast as ... When Apple tells me there is a permissions problem, ...
    (comp.sys.mac.advocacy)
  • Re: 10.6 After Two Days - Just Excellent
    ... permission repair is at least TWICE and maybe three times as fast as ... When Apple tells me there is a permissions problem, ...
    (comp.sys.mac.advocacy)
  • Re: Leopard Repairing Permissions?
    ... outside of Apple that has been certified as a Leopard Server expert. ... Repair permissions on a live running OS is very very tricky. ... Apple began a transition to the more granular ACL (Access ...
    (comp.sys.mac.system)