paula185

Q: Warning: SUID file "System/Library/CoreServices" 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.

 

<Subject Edited by Host>

iMac, Mac OS X (10.6.8)

Posted on Jun 8, 2013 2:43 PM

Close

Q: Warning: SUID file "System/Library/CoreServices" has been modified and will not be repaired.

  • All replies
  • Helpful answers

first Previous Page 7 of 7
  • by allynfromsan luis obispo,

    allynfromsan luis obispo allynfromsan luis obispo Jun 26, 2015 2:17 PM in response to paula185
    Level 1 (1 points)
    Jun 26, 2015 2:17 PM in response to paula185
  • by antoniopedota,

    antoniopedota antoniopedota Jul 2, 2015 4:43 PM in response to varjak paw
    Level 1 (10 points)
    Jul 2, 2015 4:43 PM in response to varjak paw

    Thanks Varjak.

  • by indymac515,

    indymac515 indymac515 Aug 13, 2015 7:33 PM in response to antoniopedota
    Level 1 (5 points)
    Aug 13, 2015 7:33 PM in response to antoniopedota

    I haven't read all the posts regarding this issue but, here's a link to a MAC World article regarding this. I too have been getting the same warning when repairing permissions. Since my iMac is still under extended warranty, I called. No one could give me answers (to this as well as a PHOTOS problem). I followed the Mac World recommendation and the Warning is gone, along with so many other permissions that were always appearing.

  • by adestefMac,

    adestefMac adestefMac Dec 25, 2015 10:36 AM in response to Joseph Kriz
    Level 1 (0 points)
    Dec 25, 2015 10:36 AM in response to Joseph Kriz

    I see this is a relatively old thread, but as people start installing El Capitan (like me) this needs to be addressed.  It's important to understand what the L at the beginning of the permissions listing is.  It's just a marker to show what kind of file it is.  L = link.  D = Directory.  - = file. 

     

    To me, it would appear that if this designation were different, in one case, it is looking at a link, but expecting a file.  Of course, assuming the link actually resolves to an EXISTING file, then correct: this warning is not something to worry about. 

     

    I just wonder if it could be an indication that a file might have been moved, or a link broken?  It might NOT indicate a broken link, but until something tried to access the target of the link, would we even know? I don't think the permissions scan tells us that? 

first Previous Page 7 of 7