I download the Beta for TechTool Pro V 8.0.3 this morning. It includes Disk Permissions (both repair and verify) and I have used it on OS 10.11.1 and it works.
Lou
Lou
Last edited:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
How to repair permissions?
- Thread starter Benz63amg
- Start date
- Sort by reaction score
so, apple removes 'repair permissions' because it's no longer a necessary function. then people post "how do i repair permissions?" and then, finding it's no longer necessary, find a workaround to do this anyway. makes sense...
The Terminal utility pkgutil still has a function for verifying and repairing permissions of installed packages (App Store installs, apps installed using the Installer, some system updates). Only caveat is that it won’t help you with protected files and folders as long as SIP is active. But seriously, you will very unlikely ever need it.
Just stop repairing permissions. It has not been necessary for several years and in El Capitan permissions cannot change because of rootless.
No need for this voodoo.
Oh god, just when I thought with El Capitan we are finally done with the permission repair placebo, here it comes again...
How do you check the integrity of the permissions settings? Let's say if you (like I did), turned SIP off for some testing and then forgot about having done that.
I've turned it on now but it would be good to verify that the settings are what they are supposed to be.
And if not, how it fix?
I've turned it on now but it would be good to verify that the settings are what they are supposed to be.
And if not, how it fix?
Not that repairing permissions didn't used to fix some problems... but it has never been the panacea that people seem to believe it was. Repairing permissions every few months does not lead to a "smoother system."
The most frequent offenders to System permissions are application installers that like to shove stuff into the /System/Library folder. I would usually run "Fix permissions" after installing Adobe or Microsoft applications, which would often install all sorts of stuff in there.
With El Capitan rootless (which is really just an extended attribute given to the system folder), applications will have to stop installing weird stuff in there with the wrong permissions.
El Capitan isn't even released yet, so who knows. Maybe after it's released, there will be a handful of scripts or applications to address issues caused by people disabling SIP.
With El Capitan rootless (which is really just an extended attribute given to the system folder), applications will have to stop installing weird stuff in there with the wrong permissions.
El Capitan isn't even released yet, so who knows. Maybe after it's released, there will be a handful of scripts or applications to address issues caused by people disabling SIP.
A fix implies a problem. Even if the permissions are not set correctly, this doesn’t mean that there is a problem. Sometimes wrong permissions can lead to problems. The system checks and repairs the permissions upon installing a system update, which should give you periodic maintenance. A straightforward manual fix would be a system reinstall. You can just reinstall OS X from recovery without tainting your configuration or user files. It will make sure that the core system is correctly installed.
To add to KALLT's answer (which is IMO correct), you can also write a simple script that verifies the permission agains the permission database and sets them accordingly. If you disable SIP, then you know what you are doing, so writing a script like that is certainly not a problem, right?
you should be able to disable SIP, set up those apps, then re-enable SIP; works for bartender, and how i changed some default icons...
If repairing permissions hasn't been necessary for years, then why is it, when Safari gets bogged down or I have issues with iTunes, I repair permissions and it all works smoothly again???? I have to do this quite often, so often I wonder what the freaking deal is with OS X...I mean, it was designed to fix permissions just after installing an app, but, I have to use it very often...no new apps or anything installed.
Here is a typical example of the results:
"2015-09-28 18:37:19 -0400: Repairing permissions for “Benjamin's Fusion Drive”
2015-09-28 18:39:59 -0400: Group differs on “Library/Printers/InstalledPrinters.plist”; should be 80; group is 0.
2015-09-28 18:39:59 -0400: Permissions differ on “Library/Printers/InstalledPrinters.plist”; should be -rw-rw-rw- ; they are -rw-r--r-- .
2015-09-28 18:39:59 -0400: Repaired “Library/Printers/InstalledPrinters.plist”
2015-09-28 18:42:30 -0400: User differs on “private/var/db/displaypolicyd”; should be 0; user is 244.
2015-09-28 18:42:30 -0400: Group differs on “private/var/db/displaypolicyd”; should be 0; group is 244.
2015-09-28 18:42:30 -0400: Repaired “private/var/db/displaypolicyd”
2015-09-28 18:43:01 -0400:
2015-09-28 18:43:01 -0400: Permissions repair complete"
I almost always have the same permissions repaired, though, sometimes only the "printers" ones, or only the "displaypolicyd" ones.
I am concerned about this and also DiskWarrior, the one and only disk utility I can highly recommend (I've been using it for years), as they have not yet stated if it is compatible with El Capitan nor any updates.
a reboot should help with those things (safari, itunes). if apple is telling you that repairing permissions is irrelevant in 10.11...why do it? as for disk warrior (an amazing app, which has saved my life at least twice), am sure we'll see an update soon, since 10.11 is 'official' in 2 days...
If this is indeed the case, it means that you are using some software that repeatedly messes up your system files.
Those things are absolutely harmless. Its a bug in OS X, but it does not affect any functionality. This can't fix any issues with Safari or iTunes that you might be having. I am managing a department full of Macs and I routinely need to perform maintenance on them. I don't remember a single time when repairing permissions actually fixed the issue.
ugh, my first mac, 9.6? conflict catcher...you'd reboot, like, 30 times, to test all the extensions that loaded, to find the culprit (when u had an issue). OS X is a gift compared to classic.
If that is the case, then I do need "conflict catcher" ...that was a must-have app pre-OS X.
Those things may be harmless, but, for some unknown reason, repairing permissions DOES solve the issue, at least temporarily.
Quite a long while ago I used to have a "plug-in" for iTunes that caused problems in a later iTunes update. That should no longer be on my mac at all, but, I wonder if remnants of it still exist. In any case, I think it's going to be time for a clean install...I just hate having to install all my apps and set up everything from scratch.
Yeah, this is the reason why I have deep dislike for "plugin" programs like that (this includes things like XtraFinder and friends). They inject code into a running system, above undocumented behaviour and can therefore cause all kind of instabilities in subtle ways. I would prefer Apple opening up the plugin API for the stock apps. To give credit where it is due, Apple has been gradually introducing a very powerful base for a plugin API (that is much more then just that), and some of OS-wide plugins have been added with Yosemite. But we need more of those.