Skip navigation

why are Java files listed as needing repair in Disk Utility?

394 Views 7 Replies Latest reply: Jan 20, 2012 5:09 PM by baltwo RSS
NikonAnn Calculating status...
Currently Being Moderated
Jan 13, 2012 5:30 PM

Why are Java files always listed as needing repair in Disk Utility?

Mac Pro, Mac OS X (10.7)
  • X423424X Level 6 Level 6 (14,190 points)

    You will always see a bunch:

     

    Disk Utility's Repair Disk Permissions messages that you can safely ignore

     

    Just trust the repair did it's job.

     

    Of course this begs the question why are you doing a repair permissions in the first place?  Generally you rearly ever need to do repair permissions.

  • baltwo Level 9 Level 9 (59,150 points)

    Because the engineers failed to make the appropriate items symbolic links and DU can't fix those, even though it says it can.

    27" i7 iMac 10.6.8 , Mac OS X (10.7.2), G4 450 MP 1.5 GB RAM w/(10.5.8/10.4.11/9.2.2)
  • FrenchToast Level 3 Level 3 (570 points)

    Baltwo, bull's eye, as always!

     

    X423424X's question is pertinent too: you usually need to repair permissions after some major upgrade or update, not on a regular basis. Is there a particular reason why you'd often try to repair permissions? Here's more on the subject.

  • WZZZ Level 6 Level 6 (11,875 points)

    FrenchToast wrote:

     

    Baltwo, bull's eye, as always!

     

    X423424X's question is pertinent too: you usually need to repair permissions after some major upgrade or update, not on a regular basis. Is there a particular reason why you'd often try to repair permissions? Here's more on the subject.

    Repairing permissions after an update or upgrade is harmless, but I would question the need to do it even there. The Apple update itself should set the correct Permissions. I still do this, really as a hangover from Tiger days -- not certain it was really ever needed there either -- and because it's a habit that's hard to kick, but it's never found anything to repair...but for one buggy exception, which was the 10.5.8 Combo update. Running it once and then repairing Permissions created a real error. It was discovered the Combo needed to be run twice back to back and then Permissions repair. In fact, one would have been better off not running Permissions for that update to begin with. There it wasn't harnless.

     

    https://discussions.apple.com/message/9968141#9968141

     

    BTW, even Flash updates, which always used to set incorrect Permissions, are coming in clean these days.

     

    Exercises in Futility: Permissions Repair

  • Boyd Porter Level 2 Level 2 (435 points)

    One more suggestion.  Uncheck show details when you run Disk Utitilty.  The only thing you need to know is that it finished successfully.  If there is an error that needs your attention, it will let you know by showing that it was not successful.  Unless you understand how the permissions work or have an inordinate interest, the details will make you worry unnecessarily.

     

    Again, the only important thing is the last line showing that it finished successully.

     

    Have a nice day.

    Two MacBook Air, Mac OS X (10.7.2), Mid 2011, 11", 64GB, 2GB Ram
  • baltwo Level 9 Level 9 (59,150 points)

    FWIW, I always beta-test on a clone of my main installation. Then, you do that all you want and when finished, blow it away and make another bootable clone. I never do it on my main installation unless I'm installing Apple's updates, just to check it didn't muck anything up.

    27" i7 iMac 10.6.8 , Mac OS X (10.7.2), G4 450 MP 1.5 GB RAM w/(10.5.8/10.4.11/9.2.2)

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.