Repair permissions not repairing

I've been digging on this for a while and don't see a relevant answer, so here goes. My ichat stopped working earlier today. Clicking the icon in the menubar says "no account enabled." Now, normally when this happens, I just reboot to the recovery partition, run "repair disk permissions" in disk utility, boot up again and things are grand.
Only, this time, I've run repair permissions about a half-dozen times, and all of the items listed as a problem don't seem to go away. I saw a post somewhere that this was a known java issue that didn't affect anything. However, ichat still says "no account active" so I'm conviced that this is a problem in some regard.
So, how do I repair disk permissions that will not be repaired?

Michael Lunsford wrote:
I've been digging on this for a while and don't see a relevant answer, so here goes. My ichat stopped working earlier today. Clicking the icon in the menubar says "no account enabled." Now, normally when this happens, I just reboot to the recovery partition, run "repair disk permissions" in disk utility, boot up again and things are grand.
Only, this time, I've run repair permissions about a half-dozen times, and all of the items listed as a problem don't seem to go away. I saw a post somewhere that this was a known java issue that didn't affect anything. However, ichat still says "no account active" so I'm conviced that this is a problem in some regard.
So, how do I repair disk permissions that will not be repaired?
As long as it says 'Permissions Repaired' at the bottom, then they have been repaired. Ignor the continuing list. It really means nothing. I gaurentee you. As for iChat, never used it, sorry.
Good Luck
Pete

Similar Messages

  • 11g Catalog Permissions not taking effect

    I am having an issue with the selected permissions not taking effect as they should. The major issue with this is that users that have been assigned to application roles that are assigned the 'Open' permission type are able to delete that same folder. Basically users that are only supposed to view objects in a folder now have access to delete that entire folder, despite inheriting application roles that have been set to only open that folder. This is only occurring at the Shared Folders level of the catalog, so as you can tell this could be a major issue if a user was to accidentally delete the entire shared folder structure. Further down in the catalog tree the permissions are acting properly. We have a folder with all of our GL reports that is secured in the same fashion, and the permissions work as intended there.
    Is it possible that there is some kind of root level permission that is overriding what we have set up at the Shared Folders' permission level?

    How are you packaging the files? If you use a .zip archive, the copies created when they unzip the archive should have the correct permissions.
    And by the way, repairing permissions won't do anything with items in a user account.

  • Permissions not fixing in disc utility

    i know there is something with a update that is making one of the permissions not fixing but i am getting a lot of them that are not fixing. its not that big of deal i dont think it really seems to be having that big of a affect on my mac but im still kind of worried this computer is all of my work and school. here is what im getting.
    Repairing permissions for “Dustin's HD”
    Warning: SUID file "usr/libexec/load_hdi" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Reso urces/Locum" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner " has been modified and will not be repaired.
    Permissions differ on "private/var/log/secure.log", should be -rw------- , they are -rw-r----- .
    Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconf ig" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writecon fig" has been modified and will not be repaired.
    Warning: SUID file "usr/libexec/authopen" has been modified and will not be repaired.
    Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.
    Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.

    Griff,
    I believe you have just made a mistake. The message Disk Utility was putting out about ARDAgent is totally innocuous. But by replacing the file with the original from the Leopard install disk you have, I believe, just undone the Remote Management update, which was one of the first updates Apple released after Leopard launched.
    Folks,
    These SUID warnings are simply Disk Utility's way of telling you that it has detected a file which has been UPDATED without also updating Disk Utility's records as to what's correct regarding that file. So Disk Utility is letting you know that it isn't going to second guess things here and perhaps undo an important change -- and that if there is something wrong with the permissions for that file you will need to correct it manually instead of relying on Disk Utility to do it for you.
    Which is why Griff's ARDAgent message went away when he (mistakenly) replaced the updated file with the original from the Leopard install DVD. Now he's got the older version of the file (and its various permissions) that Disk Utility knows about (thus no message) instead of the newer version installed (quite possibly with intentional permission changes) by the Remote Management update.
    Eventually Apple will put out another update that also brings Disk Utility's records up to date and these messages will go away. If you download the standalone version of the 10.5.1 update and apply it, then that correction to Disk Utility's records is added for all but the ARDAgent file. They'll get around to telling Disk Utility about that ARDAgent change down the road I suppose.
    Again, these SUID warning messages can be safely ignored except to remember that if there IS something wrong with the permissions of one of these listed files then you will have to correct it yourself. That's all the message is telling you.
    --Bob

  • Project Server 2010 / Sharepoint 2010 Permissions not syncing to Project Site

    Project Permissions not syncing to Project Site
    Project Manager Group
    New project is created and published project server sends permissions to Sharepoint which puts users into the following groups:
    <dir><dir></dir></dir><dir><dir>
    Web Administrator (Microsoft Project Server)
    Project Managers (Microsoft Project Server)
    Team members (Microsoft Project Server)
    Readers (Microsoft Project Server)
    At this time the creator/owner, owner’s management, portfolio managers, and executives should all have Project Manager rights on the sharepoint site, and Admins will have Web Admin permissions.
    Issue #1: Only the Web Admin permissions and creator/owner permissions are being added to the Sharepoint permission groups
    Workaround #1: Going into the project site permissions and adding the
    Project Managers (Microsoft Project Server) group manually and the sync will keep the permissions
    Workaround #2: Going into the Server Settings, Manager Groups then removing or add all users to the No Permission Group, which forces an sync to all workspaces. Con: This workaround can only be down at night when users are not active since it will
    block the queue for at least an hour.
    Project Owner Transfer
    Previously created project has owner change, once saved and published project server sends permissions to update user’s permission to
    Project Managers (Microsoft Project Server) on Sharepoint project site.
    Issue #2: When Project owner is changed and project is published the owner is not getting permissions to the Sharepoint project site. However, if owner is also added to the team using the Build Team Feature the sync will give the owner Project
    Manager permissions on the Project Site.
    Workaround #1: Going into Server Settings, Project Sites, select project and Synchronize. Once this is done, the owner will have Project Manager Permissions without being added to the team.
    Users who have been added to this project in Project Server 2010, but not assigned to tasks. Users who have assignments in this project in Project Server 2010 and are contributors to the project workspace site,
    meaning that they can create and edit documents, issues, and risks. Users who have published this project or who have
    Save Project permission in Project Web App and are contributors to the project workspace site, meaning that they can create and edit documents, issues, and risks. Users who have
    Manage SharePoint Foundation permission in Project Web App and are contributors to the project workspace site, meaning that they can create and edit documents, issues, and risks.</dir></dir>

    By default when you create project build team add users in the task and publish the project plan then All the User which are available in the project plan including Project owner will go to below mentioned group in project site:
    1. creator/owner, owner’s management, portfolio managers, and executives should all have Project Manager will get access to Project Managers (Microsoft Project Server)
    2. User who are having team member access to PWA will get Team members (Microsoft Project Server) access if they are assigned to the project task.
    3. User who are having team member access to PWA will get Readers (Microsoft Project Server) access if they are not assigned to the project task.
    4. Only PWA Administrator will get the access to Web Administrator (Microsoft Project Server)
    Sharepoint permission you have to use when you want to give permission manually to users on project site  
    In the Project Site provisioning setting under Server setting if you have Check to automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions change in Project
    Server.
    Then all the user get access as per describe above and if you will give access manually to any of the user either in project server group or in Sharepoint group once you will publish the project next time all the manually given permission will go away.
    IF you want to give permission to user manually to sharepoint group or project server group then uncheck automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions
    change in Project Server.
    You check PWA site setting --> Site permission then member of Sharepoint group user who will have access to sharepoint group in PWA site setting site permission will have access to all the project site sharepoint group as Project site inherit permission
    from PWA root site.
    Both the issue which you have described is behavior of project site.
    For issue 2 when first time project owner create and publish the project and projectsite is getting created then porject owner name gets access  in the porject manager (project server group) nect time if you will change the owner and publish the project
    until he will not present in the project plan will not get the permission.
    If you want to give sharepoint permission to users then uncheck automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions change in Project Server and give
    the permission manually. 
    Project site in 2010 has some issue and not full filling customer need some time ,Ms has came up with 2013 which is having tight integration with project sites .
    Project workspace security groups are equal to the SharePoint Server 2010 security groups.
    Web Administrator equals Full Control
    Project Managers equals Design
    Team members equals Contribute
    Readers equals Read
    Users who have Manage
    SharePoint Foundation permission in Project Web App and are contributors to the project workspace site, meaning that they can
    create and edit documents, issues, and risks will get access to Web Administrator (Microsoft Project Server)
    http://technet.microsoft.com/en-us/library/cc197668(v=office.14).aspx
    kirtesh

  • In the context of restoring a drive from a backup, i copied /etc/sudoers from my backup. Now it does not work due to the permissions not being correct (even though it was copied via sudo cp -rp)

    In the context of restoring a drive from a backup, i copied /etc/sudoers from my backup. Now it does not work due to the permissions not being correct (even though it was copied via sudo cp -rp)

    Most likely you have Office 2004 which are PPC-only applications and will not work in Lion. Upgrade to Office 2011. Other alternatives are:
    Apple's iWork suite (Pages, Numbers, and Keynote.)
    Open Office (Office 2007-like suite compatible with OS X.)
    NeoOffice (similar to Open Office.)
    LibreOffice (a new direction for the Open Office suite.)

  • Permit not assigned for Actual cost

    Hi Dears,
    Permit not assigned for actual cost in maint order
    Actual cost in maintenance order is 3000
    In IPMD, cost1 is assigned with class ACTUAL COST and value 3000 is defined.
    In OIPG,  Permit class ACTUALCOST is assigned.
    Goods issue done to order for value 3000.
    Again cost determination executed, but still cost1 is not assinged to the work order.
    Am i missing anything ?
    Regards,
    Alagesan M

    Hi
    In charac CT04 i maintained one value 3000 and table maintained CSEVPERMIT and IKOSTEN
    In class CL01, assigned the charac for 049 class type
    In OIPG, permit class is maintained with class
    In IPMD, new permit created and assigned class in classification and maintained 3000
    Now order created and component assigned the planned value is 3000.
    through MIGO goods issue done and found the actual value is 3000.
    But still opened the permit found nothing assigned.
    For Estimated cost and planned costs it is working good only for actual cost permit is not assigning.
    Actual cost we need to anything more other than this ?
    Alagesan

  • Permissions not enabled on disk.

    Hello,
    I previoiusly had linux installed in parallel to Leopard on my macbook 4,1.  I'm trying to merge all my partitions so I can reinstall Leopard in as large a space as possible, but the partition that was used as the swap returns error 9973 (Permissions not enabled) whenever I try to do anything with diskutil.  The partition mounts, but doesn't show up in my Volumes directory, so I can't use vsdbutil or chmod.  Here's a layout of my drive:
    #:         TYPE                               NAME                   SIZE       IDENTIFIER
       0:      GUID_partition_scheme                                *149.1 Gi   disk0
       1:      EFI                                                               200.0 Mi   disk0s1
       2:      Apple_HFS                       Macintosh HD        123.6 Gi   disk0s2
       3:      Apple_HFS                       Linux HD                 23.3 Gi    disk0s4
       4:      Linux Swap  <---- Problem!                                 1.9 Gi     disk0s3
    Any suggestions for fixing this? 
    Thanks,
    Jeremy

    Hi BDAqua,
    Thanks for the suggestion, it wasn't my final solution, but it did something very interesting.
    chown root /dev/disk0s3 seemed to execute but I couldn't run chmod on it.  I tried erasing the partition to FAT32 after running chown and instead of displaying error 9973 (Permissions not enabled) it appeared to perform the erase without being able to mount the volume afterwards.  I checked things over with diskutil list and it still listed the partition as being the linux swap.  Only now do I realize that I should have tried running vsdbutil after chown to see if that would have worked.
    My fix was to boot from the Ubuntu install cd and select "Try Ubuntu without installing" from the menu that came up.  Once it was up and running I used the GParted Partition Manager to modify my drive.  Much to my surprise, GParted didn't list the linux swap partition, but rather the name and format I applied after running chown root /dev/disk0s3.  I'm still not sure why diskutil didn't list the change after I erased but I suspect it had something to do with the volume failing to mount after the erase.  From here it was a simple matter to delete all unwanted partitions and resize the one for Mac OS X.
    I should add that I tried GParted Partition Manager because I read a post that it could easily deal with Linux Swap partitions.  Here's the post: https://discussions.apple.com/thread/1748051?start=0&tstart=0
    Thanks for the help,
    Jeremy

  • Disk utility repair permissions not working in leopard

    any ideas why my premissions repair are not working in my new leapoard is there a free phone to apple
    because i bought my os x 10.5 from them

    Tony, if you think it isn't working because all you see is the blue & white "barber pole" display instead of the all blue progress bar during the repair, rest assured that this is just a display bug & the repair actually is being done. It can take a long time for the repair -- much longer than in Tiger, so be patient -- give it as much as 10 minutes or more to complete & you should see the 'permissions repair complete' message eventually.
    If you are seeing something else, my apologies for assuming otherwise. Please describe more about why it isn't working & perhaps we can help you.

  • Disk Permissions not repaired

    I run Disk Utility>First Aid>Repair Disk Permission every couple of weeks. Until recently running this utility has cleared all repairs. But now I am getting a list of repairs that doesn't "clear" (meaning that the next time I run Repair Disk Permissions, the same list appears again. This has been associated with iTunes and iPhoto running slower than they have in the past. The list (see below) seems to refer mostly to Front Row, iTunes and iPhoto. Please advise if you know what's going on and how to fix it. Here is the list:
    Repairing permissions for “Apple 400”
    Reading permissions database.
    Reading the permissions database can take several minutes.
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "Applications/iTunes.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
    Permissions differ on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/ CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
    Permissions differ on "Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeResou rces", should be -rw-rw-r-- , they are lrw-rw-r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iLifeMediaBrowser.framework/Versions/A/CodeRe sources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/CodeResourc es", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/BlackAndWhiteEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/CubeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DissolveTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DropletTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FadeThroughBlackTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransitionSmall.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PageFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PushTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/RevealTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/SepiaEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/TwirlTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/WipeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions repair complete

    I have exactly the same issue. I have 100 plus of those same errors showing up all involving iPhoto, iTunes & Front Row. No matter what I do, I cannot get rid of the errors. Doing an archive & install is a last resort for me. I have not yet tried the 10.5.6 combo reinstall yet either.
    What I have done so far:
    1.Soft boot repair permissions & restarting.
    2.Regular boot or restart, repaired permissions and restarting.
    3.Ran the install disc verify disk and repair permissions settings. Disk results are always green - no problems. The exact same errors show up on the disc when repairing permissions & remain there without disappearing
    4.Ran Diskwarrior. All green. Graph 0% out of order.
    5.Ran Techtool Deluxe. All clear.
    I never get the permissions has been repaired. It's always, permissions repair completed. Well, what exactly did it complete? Sure isn't repairing.
    I am going to give Apple Care a call. I paid for it, might as well get my monies worth!! Will post their solution here _*IF IT WORKS.*_
    Message was edited by: CMCSK

  • Why is repair of file permissions not automatic if it is so important?

    Over an over I have seen advice to use Disk Utility to verify and repair permissions to prevent or to try to repair OS problems. Some say repair weekly, some monthly, other say after updates, others when there are problems and on and on and on. If this is something that should be done periodically, why hasn't Apple made the system software do this for us automatically? What are permissions? Why can't repair be automatic????? How do they get screwed up?

    Permissions tell the system who the file belongs to, and who is allowed to do what with a file or folder. Thus the system folder is owned by root, belongs to group wheel, the owner has read and write permissions, the group can read and execute (that is, look at things inside and open the folder), and so can others (users on the computer). When the system is installed this information is saved, and when you repair permissions the list of what permissions "ought" to be is consulted and applied. The list ONLY refers to files that are installed by Apple, so your own home folder and its contents are not fixed or changed in any way.
    Occasionally a program needs access to files or folders where you don't have write permission in order to be installed. When that is the case the installer will ask you for your admin password, and change some permissions so it can do its thing. If the installer is badly written it leaves the permissions in the altered state. Personally I don't believe in giving an installer my password. I don't think a normal program should be mucking about with the System folder, and have discovered several that can be installed perfectly well without adding anything to the system--they didn't really need the password to start with.
    At any rate, if an installer goofs the permissions, or if you yourself monkey around with something and goof the permissions, or if a stray cosmic ray hits, the permissions can differ from what the system file says they ought to be. On very rare occasions this can cause a problem. In the course of many years of reading these forums I have seen about half a dozen problems that are fixed by repairing permissions.
    As routine maintenance Repair Permissions is not necessary. If you never install anything that asks for your password, never mess around with system files, Apple never sends out a software update that messes up something, and no cosmic accident happens, then there is no need to repair permissions. I know a number of people who have never repaired permissions at any time, and their computer runs just fine. Indeed, permissions can be "incorrect"--that is Disk Utility will report the file or folder has a "wrong" set of permissions, but things will still work. For instance, if the incorrectness is that the item allows EVERYONE read, write, and execute permission it will work, it may be wrong (perhaps only the owner should have write permission), but it will work just fine. It's probably a security risk, but it works.
    Francine
    Francine
    Schwieder

  • Permissions not repairing with Disk Utility

    I booted off my internal backup drive to run Disk Utilities on my main drive as I've been having some display problems and wanted to check for viruses and check the integrity of my drive. No viruses, disc verifies OK, but I had a lot of permissions needing repair, which I did.
    I then cleared history and ran Verify Permissions again and even though the repair said all permissions were repaired except the last SUID file, these 7 came back. I ran repair again. Disk Utility said all except SUID were repaired like before. Ran verify again and they same 7 plus SUID showed up needing the same repairs Disk Utility said it fixed twice before.
    Is this indicative of a serious problem? Any ideas how to fix them? Do I even need to?
    Have MacPro1,1 - Running OSX 10.6.7, 8 GB RAM
    Thanks,
    Steven
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jconsole.jar ", should be -rw-r--r-- , they are lrw-r--r-- .
    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 lrw-r--r-- .
    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 lrw-r--r-- .
    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 .
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Resources/JavaPluginCocoa.bundle/Contents/Resources/Java/deploy.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
    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 lrw-r--r-- .
    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 .
    Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.

    Thanks re permissions. I was going to try DiskWarior, to see if it could repair them, but won't now.
    For viruses I ran MacScan. Only found some tracking cookies and removed them.
    (PS: with the new Discussions points, is it better to click Correct Answer or Helpful Answer? I wanted to click both, but after clicking Helpful, Correct disappeared. Guess I should have clicked Correct for you. I assume this is how we acrue points?)
    Thx,
    S

  • Frequently repairing same permissions (not"We are using special permission"

    I'm running into some frequent weirdnesses on my G4 (slow response, hangups, various things crashing that didn't used to crash) which I don't believe are related to this permissions issue (I think I have a drive or a partition flipping out); however, part of what I've been doing is repairing permissions when I do run into these problems. After a handful of times of this over the last, say, month, I've noticed that the same permissions keep repairing. Here's the Log:
    Determining correct file permissions.
    Group differs on ./Applications/Utilities/Activity Monitor.app/Contents/Resources/pmTool, should be 80, group is 0
    Owner and group corrected on ./Applications/Utilities/Activity Monitor.app/Contents/Resources/pmTool
    Permissions corrected on ./Applications/Utilities/Activity Monitor.app/Contents/Resources/pmTool
    Group differs on ./Applications/Utilities/Keychain Access.app/Contents/Resources/kcproxy, should be 80, group is 0
    Owner and group corrected on ./Applications/Utilities/Keychain Access.app/Contents/Resources/kcproxy
    Permissions corrected on ./Applications/Utilities/Keychain Access.app/Contents/Resources/kcproxy
    Group differs on ./Applications/Utilities/ODBC Administrator.app/Contents/Resources/iodbcadmintool, should be 80, group is 0
    Owner and group corrected on ./Applications/Utilities/ODBC Administrator.app/Contents/Resources/iodbcadmintool
    Permissions corrected on ./Applications/Utilities/ODBC Administrator.app/Contents/Resources/iodbcadmintool
    Permissions repair complete
    Any idea what's going on with this? My impression is that these are all invisible files, or, at least, part of the app packages. What should I do about it if anything?

    Well, right now, the ratio of free space to total space is way out of whack. The capacity of the partition is 260GB with free space at 3.5GB. Yes, slap me on the back of the hands, I deserve it! This may well be the cause of my current problems as I didn't realize the ratio was so bad 'til now.
    As for your other questions, there haven't been Unexpected Quits. Some programs will simply hang up ("not responding" in the Force Quit menu)--programs such as Final Cut 4.5 (the work disc, however, is a different partition which currently has 5GB on it) I can't remember the others offhand, sorry, except System Prefs just did that to me today when I clicked on the Spotlight Pane. I did have a kernal panic a handful of days ago after the whole computer froze and I rebooted. Rebooting after the panic, the desktop came up ok.
    I've installed many things over the last month or two, though they haven't been major programs. Shareware & Freeware type of things. As for enhancers, I have Sizzlin Keys, WindowShadeX, APE, Zooom, DivX, & Flip4Mac free player.
    At the very least, sounds like I need to clear up some space.

  • Permissions not repairing

    Hi,
    Setting up my wife's new mac mini today. used setup assistant to transfer users and settings from my mbp running 10.4.11 which was updated and permissions repaired before doing anything. i did transfer everything, applications, users, files, etc. (maybe i shouldn't have done the apps) anyway, things seemed to go smoothly.
    then...
    repaired permissions on mini before taking software updates--ok
    took software updates, restarted--ok
    repaired permissions again and there was a ton to fix.
    did followup repair to see if all were caught. but they weren't.
    repaired again. but now keep getting the same results over and over.
    three are related to system/library/frameworks/java...
    comes back saying those three are repaired.
    also get five "Warning SUID file ....... has been modified and will not be repaired.
    after repeated attempts i keep getting the same results, whether i do restarts in between or not. i figure sooner or later these bad permissions will come back to bite me if i don't get it fixed. suggestions? should i start over, erase and install but this time without the apps.

    BB623 wrote:
    What causes these to be issues in the first place?
    The short answer is the cause is differences in the permissions database the process compares to the item's actual metadata. Permissions can be "repaired" only in the sense that they can be reset to what is in the database when the two differ.
    So for instance, if an OS or application update doesn't update the database as well as the item itself, you get a message telling you about that. It isn't an error in the item, just in the database, & the process is smart enough not to "fix" the item … which actually would be an error!

  • Repair permissions not really working...

    Hi guys so I'm performing some periodic maintenance on my mac and discovered that even when I run disk utility to repair permissions and it reports to have done so, when I run it again right after it repairs the exact same permissions it said I had just repaired...
    Whats going on here? Do I need to repair permissions while not booted into the drive?TIA

    i understand that it is not causing me trouble now, but I would like to fix what I can fix (if I should) to prevent bigger problems in the future... thats all.
    the link you shared with me does not directly apply to my situation. Im not getting the exact same reports that that article is talking about. unless you're telling me to just assume my situation falls in the same class as the situations in that article.

  • Repairing permissions,not clean

    I have had a dual 2 g5 for about a year, mostly used for video editing and such, lateley (the last 2 weeks or so) it has been slowing down during less than average tasks (safari opening) rendering small pictures in photoshop cs. I have safe booted/repaired permisions every month with sucess. now no matter how many times i repair them thier is always the same permission repair. So my question is, is there another something I can do or find out how to get a clean bill of health from the permissions window. Thanks in advance for any help with this matter. P.S. Is DiskWarrior a good option?

    I have written a few performance tips here
    http://homepage.mac.com/hogfish
    It could be a combination of things.
    1: Not enough RAM - get enough to cover all open apps requirements
    2: The internet or other networks - take yourself offline with a blank location in network
    3: A large almost filled boot drive - reduce and keep it to ideally less than 50% filled, don't go over 80% filled.
    4: OS unoptimized - clone your boot drive to a external and back again
    5: Slow hard drive - have a boot drive just for boot/apps/itunes/ and a bare bone "home" and keep space hogging user files (especially movies) in new folders on another drive.
    6: Caches overloaded, System Prebinding is off - Get OnyX (search Apple) and run all the Automation with a reboot once a month.
    7: Daisychaining hard drives - keep each drive on it's port off the G5, don't use hubs your just bottlenecking your interfaces.
    8: Video requires hard drive speed and redundancy - Video eats drives fast, consider a X-RAID in a RAID 5 configuration with a lot of drives for fast speed and redundacy of your data.
    9: Photoshop -Tiger over rides CS2's RAM limit, but not the previous versions of Photoshop, you'll do good upgrading and having plenty of RAM.
    10: Run X-Bench once in awhile to get a grip of the performance of your machine, especially the boot drive. I would try to your uncached 4k block writes to over 100 MB p/s
    With the latest update the Permission Repair "We are using special...." is pretty long. It's just informing you of changes and not neccessarily means they were thrown off.
    DiskWarrior only repairs your directory, it's optimizations in tests are pretty limited. It's expensive and it's name is a misnomer. If your directory needs repair, it's the program to get. I bought it once and have gone for a year without it just fine as directories rarely foul up.
    I would clone your boot drive to a external and back again, you can read how by visiting my link and downloading the file.
    (.Mac may be offline tommorow so check back)

Maybe you are looking for