Repair Disk Permissions on multiple Macs via ARD

I manage a network of about 60 Macs running Mac OS X 10.5.7
I use the latest version of ARD 3.2.2.
Is there a way to send a unix command to have disk permissions repaired on all 60 stations from ARD.
This would be a huge time saver vs having to walk to each and every machine to do it.
Many thanks for all help in advance.

Yes, that's correct. You can, BTW, just choose that from the templates in the Send UNIX Command window. It's under the Miscellaneous category.

Similar Messages

I recently repaired disk permissions on my mac HD and now my on-board speakers wont work, the icon is greyed out and only works when my headphones are plugged in.

I recently repaired disk permissions on my mac HD and now my on-board speakers wont work, the icon is greyed out and only works when my headphones are plugged in

Try to put your headphones several times in and out from your connection, might be the switch is stuck. Normally it should work again while trying to plug the headphones in and out!

Can't repair disk permissions or run Mac Software update application

I tried repairing the disk permissions and received the following error message:
Error: The underlying task reported failure on exit
Got the same error message when verifying the disk permissions. The verify disk option also failed.
Whenever I run this application to check for updates, it just bounces in the dock and disappears. Then I get this error box that says "The application Software Update quit unexpectedly". It then gives me 3 options to "ignore, report, and relaunch".
Any ideas would be appreciated.

Thanks for the fast reply. I was able to run the disk utility using the disk. But I got the same errors when I booted back up and tried to run the "repair disk permissions". Plus the "Software Update" program still crashed.

Set up printers on Multiple Macs via ARD

Hi team,
We have 50+ Macs managed by ARD.
We would like to know if copying com.apple.print.PrintCenter.plist for all users's Library will be enough to set up the printers for all users or if there is a different approach to do that.
Of course, all needed drivers (same version) have been installed on all ARD controlled Macs.
Thanks!.

I keep getting this error whenever I try Dave's original link:
The connection has timed out
The server at itech.buffaloschools.org is taking too long to respond.
* The site could be temporarily unavailable or too busy. Try again in a few
moments.
* If you are unable to load any pages, check your computer's network
connection.
* If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.
Thus requested for the file.

Repair disk permissions help

Hello all,
im fairly new to the macbook and have been reading up on repairing disk permissions as the mac has started to slow down in time
the problem i have is i opened disk utility
and ran verrify disk permisions, it found problems, so i restarted and held comand and r and booted into the recovery console
from there, i chose disk utilities and ran verify disk again, again it found problems, so i ran repair disk permisons, that came back and repaired succefull,
so just to check i then vefried the permisons again, and once again it found the same problems, so i then re - repaired the permisions, and again it cam back succefull
again i double checked and once again it found the same problems , so im going round in a loop here the problems arnt actually properly fixing?
how can i sort this out?
any help would be appreciated!
regards

Those messages are in fact quite similar to the ones Apple mention in the KB.
All the examples you posted are instances of the same symptom: the BOM states a given path is supposed to be a directory but it actually is a symlink to a directory.
A possible cause of this is when something was installed that did not foresee upgrades that would leave multiple versions installed at the same time, then the development team eventually decided that a new version would be needed to co-exist with the old one and such a new version has been installed. The old BOM file still report the directories (or files) as not being symlinks but the new installation actually moved the old data to a directory specific for the old version, installed a new version and then changed the old directory (aka the "unversioned" or "current" path) to a symlink to the latest installation.
You can safely ignore these differences.
While in the past running permission repair used to be a very important periodic maintenance routine, nowadays it's rarely needed and even more rarely useful. It still is a good idea to run it right before and after an important operating system patch update, but it's not really necessary.
It's very common (and has been for a long time) for the tool to report differences, say they have been repaired, and then, if run again, to report the same differences. In those cases you can generally ignore those differences. Only if the repair tool says it failed to repair something you should be concerned.

Repairing Disk Permissions - Not Working with Lion

I simply am not able to repair disk permissions when my Mac is booted normally - the disk utility hangs and never stops - when I boot in recovery more I can run the utility just fine - and then boot as normal. I am wondering what might be causing this or if anyone else is having a similar problem?

With Lion, it is best to do any disk repairs via the recovery partition
And why do you say that? I have heard no such thing, and this was never the case with previous systems. It has always been recommended to repair permissions while booted from the system whose permissions need to be repaired. Do you have documentation that this recommendation has changed?
Joe, repairing permissions works fine for me without needing to boot into recovery mode. Are you giving it plenty of time to finish? Sometimes it may seem to be frozen... sticking on "less than a minute" for well more than a minute, for example. Have you repaired the hard drive (which you do need to boot from the recovery partition to do)?

Repair Disk Permissions disconnect

My G5 is used as a stand-alone video editing system. Whenever I attempt to Repair Disk Permissions on my MAC drive (whether in Normal or Safe mode) I get about a third way into the program and then get an alert message telling me that the disk utility has lost its connection with the Disk Manager. Disk Warrior software does not resolve this problem. Is this a hardware or software problem? What should be my next step? Please advise.

There is a fix for something similar at the link here
http://discussions.apple.com/thread.jspa?messageID=1747535&#1747535

Installing a trial version of the Illustrator and InDesign App in Creative Cloud on my Mac is impossible. Keep getting 'Installation failed' notices. More information gives 0 fatal error(s), 0 error(s). Already repaired disk permissions in Disk Utility bu

Installing a trial version of the Illustrator and InDesign App in Creative Cloud on my Mac is impossible. Keep getting 'Installation failed' notices. More information gives 0 fatal error(s), 0 error(s). Already repaired disk permissions in Disk Utility but nothing seems to work. Exit code: 7.

Hi Maarton,
Please follow the link to resolve the issue: Errors "Exit Code: 6," "Exit Code: 7" | CS5, CS5.5
-Ankit

Anyone clean their mac using the disk utility using the repair disk permissions??

anyone clean their mac using the disk utility using the repair disk permissions??

No. Threads don't hurt anything. If your computer is not functioning properly perhaps you need to try some basic maintenance. Let's start by having you do this:
Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
Next, try booting into Safe Mode then immediately restart normally. Safe mode is going to take a while so be patient. It's slow.
Next, create a new user account. Log out of your account then log into the new account. Try using iPhoto and the publishing button. Do they work now?
If you still have a problem, then do the following. If you don't want to go through the above then just start with the following and forget the others above.
Reinstall OS X without erasing the drive
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install Mac OS X 10.6.8 Update Combo v1.1.

How can I repair disk permissions

How can I repair disk permissions on a non boot drive? I have a SSD as my boot disk and a HD as a storage drive. The permissions are not correct on th HD and in disk util the option for fixing the permissions is ghosted out. I really would hate to do this one folder at a time.
Thanks

FYI, BB
Below is a quote from Apple describing what Disk Permissions deals with.
If you still need assistance, please describe what problem/issue you are trying to solve.
http://support.apple.com/kb/HT1452
"Many things you install in Mac OS X are installed from package files (whose filename extension is ".pkg"). Each time something is installed from a package file, a "Bill of Materials" file (whose filename extension is ".bom") is stored in the package's receipt file, which is kept in /Library/Receipts/ in Mac OS X v10.5 and earlier. These files don't take up much disk space and you shouldn't put them in the Trash. Each of those ".bom" files contains a list of the files installed by that package, and the proper permissions for each file.
Does Disk Utility check permissions on all files?
Files that aren't installed as part of an Apple-originated installer package are not listed in a receipt and therefore are not checked. For example, if you install an application using a non-Apple installer application, or by copying it from a disk image, network volume, or other disk instead of installing it via Installer, a receipt file isn't created."
Is this what you want to "fix"?

Problems with Repair Disk Permissions

I am running Mavericks 10.9.5 on a new (2013) Mac Pro. When I run disk permissions I get a LONG list of repaired files and then the message that the process is complete. But if I then run the repair routine again I get ANOTHER equally long list of DIFFERENT permissions that are supposedly being repaired. This goes on ad infinitum. If I run Repair Disk Permissions on my other computers multiple times no additional permissions show up after running the program once. Any idea why this might be occurring?

You can safely ignore those messages.
http://support.apple.com/en-us/HT203172
Best.

Repair Disk Permissions Issues

I'm not sure I am posting this in the correct community but here goes . . .
I have a 17" Macbook Pro running the latest version of Snow Leopard. It is almost 2 years old and I have 4 gb RAM.
Recently, it seems to be slowing down and I have to run repair disk permissions 2-3 times a week to recoup a little speed. I also delete my Firefox cache regularly to try to gain a little there. I do make a few videos in iMovie and initially I thought that was the problem but this week I have not really worked in iMovie much and it is still slow. There seems to be some issues in the log of the repair permissions. I hope they show in this image. I don't know what these mean or how to fix them. It is the "permissions differ" entries I am confused about.

You can ignore those permissions per support article
http://support.apple.com/kb/TA21090
Since you brought up iMove, I suspect your storage is nearly full as this most certainly causes the computer to slow down. video files are the biggest culprit.
Look in your Activity Monitor and reduce the drive space by copying to a external, Disk Utility HFS+ formatted external powered drive of unnecessary files so your boot drive is ideally below 50% filled (yea I know but the computer slows down after that) and not more than 75% filled.
Once you have done that. Get another newer external powered HFS drive and download the free Carbon Copy Cloner and clone the internal drive to the external.
Hold option and boot off the external clone, test it out then use Disk Utility to erase the internal and then reverse clone the external onto the internal, this will defragment and optimize your drive so the OS and programs are on the fast part of the drive, not the slow parts.
Reboot into the internal and run off of the free OnyX's maintainence and cleaning aspects and reboot.
http://www.titanium.free.fr/
Sir speedy machine here we come!
Now of course you may have other issues that could be causing your slow down, like not enough RAM or some sort of failed process or leftover program, tweaks or simply a slow Internet.
You can opt to simply reinstall OS X 10.6 ( by holding c and booting off the installer disk ) over your installed version (doesn't touch files or programs) then immediatly Software Updating until clear, that will clean anything hanging out in OS X.
If you still have slowdowns, then it's in what geeks call "User land" basically something installed outside of root, like a program or only runs in user, not in OS X.
For that you need to create a new user, transfer your files via the Shared Drop and wean yourself off the old user and finally delete it. Also install all new versions of your third party programs removing the originals first.
That should do it.

Repair Disk Permissions utility stalled - I have read the knowledge base

I have researched the knowledge base and search for posts on this and cannot find answer: Running 10.4 at the latest version. used the original install 1 disc I received with Tiger to repair disc permissions (like Apple support has told me to do in the past, but my current research said I do not need to do this unless certain parameters are met, and none of the parameters applied, but oh well, I am here anyway). Cold Boot from the original install disc 1 and slected the start up disk I use (I only have one start up disc/drive). Did a repair disc permissions and got a long running routine that reporting a lot of fixes, then the utility has stalled -- no progress on the progress bar. I "stopped" the process using the "stop repair" button (three times). The log reflected the utility stopped, but the progress bar still is blue and not moving (for a couple of hours). When I go to quity File >Disk Utility, it warns me that Disk Utility is running and this may make my system unstable/unsuable.
QUESTION: CAN I JUST QUIT DISK UTILITY AND NOT HAVE ANY ADVERSE AFFECT ON MY IMAC DRIVE?

Thanks for your advice, I still have an issue:
-after the first repair disk permission "stalled" process, I exited Disk Utility and cold booted the machine after I had disconnected all external devices other than the original iMac keyboard
-obtained the combo patch for 10.4.7 from the Apple download site (it had already been installed but I reinstalled per your advice)
-re-applied the combo patch and then did another cold boot
-ran Disk Utility from the original Tiger install #1 disk, and then selected "repair disk permissions" for my start up disk (I only have one)
- process ran for 10 minutes or so then gave the following error message: "Disk Utility Error: Disk Utility has lost its connection with disk utility management tool and cannot continue. Please quit disk utility and re-launch disk utility"
- I pushed the "stop disk permission repair" button, then quit disk utility, then cold booted the machine again.
-re-applied combo patch as above, then cold booted the machine
-ran disk utility from the original iMac install #1 disk, ran "repair disk permissions", and then received the same error message as above.
- I then just quit Disk Utility and cold booted the machine again and went about my business. There does not seem to be any problem with the machine (was not before, but I ran repair permissions thinkging this was a routine maintenance taks that should be run)
- in my prior search of the knowledge base, I found the following information about repair disk permissions:
Location: http://discussions.apple.com/thread.jspa?messageID=607495&#607495
How often should I Repair Permissions?
You do not need to Repair Permissions on a regular basis.
There are only three occasions you need to do this:
1. When you have just installed something that required you to run an Installer, rather than just copying some software to a folder. This should be done for both Apple and non-Apple software.
2. When you have been working on your OS X files or folders while booted from OS 9, or remotely connected via a non-OS X machine, since OS 9 and other systems do not handle OS X's permissions correctly.
3. The other case is if your system is behaving strangely, when you should run Disk Repair from your CD followed by Repair Permissions. This is just to eliminate these things before going on to further trouble-shooting.
Otherwise you can happily forget about Permissions!"
So, it would appear I do not need to do anything else; the machine seems to be working properly. Is there anything else I need to do? thanks for the help! Bob

Keep having to 'Repair Disk permissions'.

My MBP (2.53 GHZ Intel Core i5, running 10.6.8) keeps running slow, and only improves after Repairing Disk Permissions. I had to run this again this morning - and I'd only ran Permissions repair two days ago! This is what I got;
'Repairing permissions for “Macintosh HD”
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/dt.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/dt.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jce.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jce.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jconsole.jar ", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jconsole.jar ".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/management-a gent.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/management-a gent.jar".
User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib", should be 95, user is 0.
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/dt.jar", should be lrwxr-xr-x , they are -rw-r--r-- .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/dt.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/jce.jar", should be lrwxr-xr-x , they are -rw-r--r-- .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/jce.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/management- agent.jar", should be lrwxr-xr-x , they are -rw-r--r-- .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/management- agent.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/security/bl acklist", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/security/bl acklist".
User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Libraries", should be 95, user is 0.
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Libraries".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle", should be drwxr-xr-x , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/deploy.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/deploy.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/libdeploy.jnilib", should be -rwxr-xr-x , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/libdeploy.jnilib".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Home/lib/security/cacerts", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Home/lib/security/cacerts".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Resources/Java/deploy.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Resources/Java/deploy.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Resources/Java/libdeploy.jnilib", should be -rwxr-xr-x , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Resources/Java/libdeploy.jnilib".
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
Permissions repair complete'
The other day the list was probably 3 times this length, often ending with '...but they are 80'.
Any ideas?
Thanks

Have you run Repair Disk?
http://support.apple.com/kb/TS1417
Have you checked SMART status?
Check the S.M.A.R.T. status on your HD:Applications > Utilities > Disk Utility > in the panel at left, selectthe first item in the list/your HD mechanism>look at the bottom of the mainwindow next to S.M.A.R.T. status and see if it says “Verified” or somethingmore ominous like “Failing.”
Have you run background maintenance scripts?
http://docs.info.apple.com/article.html?artnum=107388
Have you checked in Activity Monitor to see if any processes are using a high ammount of CPU?
Sometimes a process can run amok and use more of the CPU than it should, potentially causing a slowdown and/or heat issues and/or other issues. To check on this, first use your Mac as you normally would, the longer the better (checking this right after starting up may not show you anything). After you’ve used your Mac for awhile (again, the longer the better), go to Applications > Utilities > open Activity Monitor > in the top menu at right, select All Processes in the drop downmenu > click on the column heading titled % CPU (this will update continuously, showing the percentage each process is using) > toward the bottom left of the window, click on CPU (this will show % Idle, which will also tell you how much of the CPU is being used).
Have you done an SMC Reset?
http://support.apple.com/kb/HT3964
And 4GB used, 2GB free btw...
By chance is it referring to RAM usage?

Repair Disk Permissions: is it a safe operation ?

Hello,
I'm preparing for the 101 course and, reading about the Verify/Repair disk permissions utility, I wanted to test it on my mac.
I launched the verification on it and I see "lot" of unexpected entries (see below):
Verifying permissions for “Macintosh HD”
Permissions differ on “System/Library/User Template/ar.lproj”; should be drwxr-xr-x ; they are drwx------ .
User differs on “usr/share/collabd/coreclient/public/locales/zh_CN.lproj”; should be 94; user is 0.
Group differs on “usr/share/collabd/coreclient/public/locales/zh_CN.lproj”; should be 94; group is 0.
User differs on “usr/share/collabd/webauthd”; should be 94; user is 221.
Group differs on “usr/share/collabd/webauthd”; should be 94; group is 221.
User differs on “usr/share/collabd/webauthd/locales”; should be 94; user is 221.
Group differs on “usr/share/collabd/webauthd/locales”; should be 94; group is 221.
User differs on “usr/share/collabd/webauthd/locales/zh_CN.lproj”; should be 221; user is 0.
Group differs on “usr/share/collabd/webauthd/locales/zh_CN.lproj”; should be 221; group is 0.
Group differs on “Library/Java”; should be 0; group is 80.
Permissions differ on “Library/Java”; should be drwxr-xr-x ; they are drwxrwxr-x .
Permissions differ on “System/Library/User Template/cs.lproj/Pictures/iChat Icons”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “System/Library/User Template/hu.lproj/Pictures/iChat Icons”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “System/Library/User Template/tr.lproj/Pictures/iChat Icons”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
User differs on “usr/share/collabd/coreclient/locales/zh_CN.lproj”; should be 94; user is 0.
Group differs on “usr/share/collabd/coreclient/locales/zh_CN.lproj”; should be 94; group is 0.
Permissions differ on “usr/share/devicemgr/frontend/admin/zh_TW.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/zh_CN.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/ru.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/ko.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/nl.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/it.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/es.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/fr.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/de.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/ja.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Group differs on “Library/Documentation/Applications/iTunes/Acknowledgements.rtf”; should be 0; group is 80.
Permissions differ on “Library/Documentation/Applications/iTunes/Acknowledgements.rtf”; should be -rw-r--r-- ; they are -rw-rw-r-- .
Group differs on “Library/Documentation/iPod/Acknowledgements.rtf”; should be 0; group is 80.
Permissions differ on “Library/Documentation/iPod/Acknowledgements.rtf”; should be -rw-r--r-- ; they are -rw-rw-r-- .
Group differs on “.DS_Store”; should be 80; group is 0.
Permissions differ on “.DS_Store”; should be -rw-rw-r-- ; they are -rw-r--r-- .
User differs on “Applications/.DS_Store”; should be 0; user is 501.
Permissions differ on “Applications/.DS_Store”; should be -rw-rw-r-- ; they are -rw-r--r-- .
Group differs on “Library/Preferences/com.apple.alf.plist”; should be 80; group is 0.
ACL found but not expected on “private/var/root”
ACL found but not expected on “private/var/root/Library”
ACL found but not expected on “private/var/root/Library/Preferences”
Permissions verification complete
It seems to me that these are all related to system files, things that weren't changed by third-party applications or by me.
The question are:
- why an untouched system would have errors in the permissions ?
- is it safe, since I haven't got until now problems with permissions on that os, to repair these errors or it's better to leave everything as it is now ?
Ciao,
Nicola

Hello Nicola,
You raise a touchy area for discussion...some users on here are very opposed to repairing permissions, others are strongly in favor of repairing permissions before and after software installation.
The permission statements you see do not generally adversely affect the system but they are not the permissions disk utility has been told to expect. Those may be artifacts from the installation process and why we have been told in the past to always repair permissions after installing/updating the operating system.
Since you ran verification, if you run repair you will end up cleaning up a lot of this "discrepancies" with what disk utility wants to see.
Repair permissions is safe, and I tend to use it every time I upgrade or install software.
Ralph

Repair Disk Permissions on multiple Macs via ARD

Similar Messages

Maybe you are looking for