Disk Utility Repair error

Discussion in 'macOS' started by tylermoney, Oct 31, 2010.

  1. tylermoney macrumors newbie

    Joined:
    May 6, 2008
    Location:
    Pittsburgh, PA
    #1
    I ran a fix permissions today, and got the following errors. I have no idea what they mean, and am a bit concerned. Anybody have any idea what this stuff means?... this is from log file:

    2010-10-31 21:00:24 -0400: ACL found but not expected on "Users/Shared/.localized".
    2010-10-31 21:01:16 -0400: Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad" has been modified and will not be repaired.
    2010-10-31 21:01:21 -0400: Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources/DiskManagementTool" has been modified and will not be repaired.
    2010-10-31 21:01:21 -0400: Warning: SUID file "sbin/umount" has been modified and will not be repaired.
    2010-10-31 21:01:22 -0400: Warning: SUID file "usr/bin/quota" has been modified and will not be repaired.
    2010-10-31 21:01:26 -0400: Warning: SUID file "usr/sbin/pppd" has been modified and will not be repaired.
    2010-10-31 21:01:26 -0400: Warning: SUID file "usr/sbin/vpnd" has been modified and will not be repaired.
    2010-10-31 21:01:38 -0400:
    2010-10-31 21:01:38 -0400: Permissions repair complete
    2010-10-31 21:01:38 -0400:
    2010-10-31 21:01:38 -0400:

    Any help appreciated. Thanks.
     
  2. Hal Itosis macrumors 6502a

    Hal Itosis

    Joined:
    Feb 20, 2010
    #3
    Neat! ;)

    Only problem is... these four SUID items from tylermoney's post do not appear on that list:
    :rolleyes:

    What action would be prudent with respect to those items then?


    --


    @tylermoney: here are some listings and digests (from my machine) which may help ease your mind (assuming yours look like mine that is):
    Code:
    $ [COLOR="Blue"]ls -la /sbin/umount /usr/bin/quota /usr/sbin/{pppd,vpnd}[/COLOR]
    -r-xr-xr-x  1 root  wheel   64192 Apr  7  2010 /sbin/umount
    -r-sr-xr-x  1 root  wheel   63936 Apr  7  2010 /usr/bin/quota
    -r-xr-xr-x  1 root  wheel  926032 Apr 23  2010 /usr/sbin/pppd
    -r-xr-xr-x  1 root  wheel  350752 Apr 23  2010 /usr/sbin/vpnd
    
    $ [COLOR="Blue"]md5 /sbin/umount /usr/bin/quota /usr/sbin/{pppd,vpnd}[/COLOR]
    MD5 (/sbin/umount) = c7c37ffc9a80ea1e7d2fe70f8cd5bb6f
    MD5 (/usr/bin/quota) = a15280dee40f99a7767486951f17d0a7
    MD5 (/usr/sbin/pppd) = 06277e7d82dc61eeaddbe56f45c34456
    MD5 (/usr/sbin/vpnd) = fe7e64d0e2ad6a876303863dc3ca1559
    

    [just run the blue commands in terminal and verify the stuff looks identical. if not, show us what's different.]



    --

    I'd like to take this opportunity to make readers aware that this is all the result of a bug which is about to celebrate its three year anniversary shortly. Please do not grow accustomed to ignoring SUID warnings... neither should we accept having to visit some web page (to identify bogus DURP reports) as "normal" procedure.

    Thanks.
     
  3. Hal Itosis macrumors 6502a

    Hal Itosis

    Joined:
    Feb 20, 2010
    #4
    On second thought, look closely at those three items from my machine there (i.e., all except quota). They're not even supposed to be SUID in the first place! :eek: And —despite that fact —DURP regards them as such... and subsequently refuses to disable any setuid/setgid high-order bit(s)!?!?! :eek: It's extraordinary the amount of fail going on here.

    Please fix this Apple. (i.e., all of it)
     
  4. tylermoney thread starter macrumors newbie

    Joined:
    May 6, 2008
    Location:
    Pittsburgh, PA
    #5
    Yea, I totally agree. I read many forums saying these were safe to ignore (aside from the ones that don't show up in the list), but the idea of ignoring any of those files as a legitimate answer is certainly concerning to me, and from readying other forum posts on the apple site, many others.

    I guess I just won't worry about it for now, aside from the fact that the reason I ran permissions repair in the first place was because my machine was acting goofy. It's better now, even w/ the strange errors, but it tends to get wonky over time like it hasn't in the past.

    Thanks for all the replies everyone. Maybe something will work out soon, hah.

     

Share This Page