Previous 1 2 3 4 5 6 7 Next 99 Replies Latest reply: Jul 17, 2011 2:43 PM by R C-R Go to original post Branched to a new discussion.
  • powerbook1701 Level 3 Level 3

    it sounds, then, that as long as we are not seeing high CPU usage and those files are NOT present on our machine (the MRT app), then all went like it was suppose to.

    I am wondering if those with issues restarted right after the update and interupted the process that was to take place.  Normally, after a security update, a restart would be usual.

    This time, I waited for some time after the update to restart my machine (noticing that Software Update didn't call for it as usual). I figured there had to be a reason why it didn't need one.


    In looking at my logs, I left 30 minutes between install and restart...

  • ikovacev Level 1 Level 1

    This stopped CPU hogging for me:


    sudo launchctl unload /System/Library/LaunchDaemons/

  • powerbook1701 Level 3 Level 3

    since the MRT process is suppose to happen, then delete itself, doesn't that mean you system didn't finish with the process of searching, if found remove, and then delete itself?

  • ds store Level 7 Level 7

    No MRT anywhere on my system, except the MRT.pdf

  • ds store Level 7 Level 7

    R C-R wrote:


    Linc Davis wrote:

    What's the point of installing files into several standard locations, only to delete them a few minutes later? Bizarre.

    It isn't bizarre; it is one of the ways clean up is done after restarts.


    Read what he says, "what's the point in installing files in several locations..."


    Surely to remove something you don't need to install files all over, just remove the offending files using the code in RAM and then quit.


    You install stuff on the drive because you want to use it again later. So to install on the drive and then remove it is exactly what he said: "Bizarre"


    EFi changes needs code installed on the drive as it's used upon reboot, yet this Security Update doesn't require a reboot.

  • R C-R Level 6 Level 6

    ds store wrote:

    Surely to remove something you don't need to install files all over, just remove the offending files using the code in RAM and then quit.

    What code in RAM are you talking about? When you restart a Mac RAM is in an indeterminate state. During the boot process, it is used as a staging ground for initialization, loading & linking files, & so on. The only thing that you can be sure will persist are files you have written to the drive in the normal areas (IOW, not to temp files that are purged as a normal part of the shutdown or startup process).


    EFi changes needs code installed on the drive as it's used upon reboot, yet this Security Update doesn't require a reboot.


    The latest Security Update does require a restart, as do all OS updates that are designed to be installed after all normal (non system) user accounts are logged out & their processes terminated. Since the advent of Leopard Apple has increasingly done that, since it prevents users or the processes they run from interfering with the update process.


    The EFI partition is not used for anything in OS X except as a staging area for certain firmware updates, & that is only when invoked by following the instructions in the updater application to complete the update process.


    You seem a bit mixed up on the facts here.

  • powerbook1701 Level 3 Level 3

    Reporting my experience, this particular security update, unlike every other one I have ever installed in Mac OS X, did not require a restart.  It didn't have the usual message after it installed saying to restart, it just simply checked for available updates again and said everything was up to date.


    I admit it is odd, but having installed on 2 of my own Mac's and checked with 4 other people with a similar setup, a restart was not needed immediately after installing, however, I did restart it manually about 30 minutes later.


    Even when I checked for updates via Software Update (to download and install SU 2011-003), the little message icon noting a restart required was not present.

  • R C-R Level 6 Level 6

    Odd. On every Mac I have installed it, I did get the little icon indicating a restart was required, & that is what happened.

  • thomas_r. Level 7 Level 7
    Apple Watch

    I've installed it through Software Update and through the manual download, and neither required a restart.

  • R C-R Level 6 Level 6

    Hmmm. Searching through my install logs, it looks like I installed the font update at the same time as the security one on this iMac. I think that would explain the restart I saw, if not the icon in Software Update. But that could just have been a "senior moment" for me -- my eyesight is not its best in the mornings, nor is the old wetware, & that's when I did the updates.

  • powerbook1701 Level 3 Level 3

    I am assuming from this thread that the software update version was fine, and no manual download and install is needed of Security Update 2011-003 (since we determined the MRT app was a shortlived thing).


    If I remember correctly the Font update did require a restart, which would explain why you saw that one was needed (for the font update).


    Thanks for confirming and researching what you saw.


    Intego is still reporting some kind of bug with the preference panel, however.

  • Greg Mihran Level 1 Level 1

    Thank you so much ikovacev ... your Terminal command works -

    "sudo launchctl unload /System/Library/LaunchDaemons/"


    I have no idea why, but since I installed the latest Apple security update on BOTH of my MacBook Pro and iMac (both running OS X 10.6.7), CPU utlization has been fluctuating with fan-on between 40% and 90% constantly - I have never seen this before.  This type of 'upgrade' reminds me so much of the ill-fated Windows security releases and why I switched over to Mac in the first place! I hope this isn't typcial.


    Until I read something official from Apple, I will continue to run ikovacev's Terminal command - thank you!



  • Greg Mihran Level 1 Level 1

    Also kudos to dahtah - once I appled ikovacev's sudo unload command, I removed this file, restarted and all is back to normal - /System/Library/LaunchDaemons/


    No MRT process is now running.  CPU usage is back to normal, 5-8% at rest on both my MacBook Pro and iMac.  Thank you both.



  • R C-R Level 6 Level 6

    If the mrt processes do disappear from Activity Monitor's list of processes, I think it is safe to assume that the update went smoothly. If not, it may well indicate a local problem with the file system or something similar on the affected Macs.


    Regarding my confirmation & research, I should have done that before posting inaccurate info in the first place. I'm thankful that others are around to goad me into rechecking things & not relying so heavily on my aging memory. Aging is no fun but it beats the alternative.


    Speaking of rechecking, I cannot (so far) reproduce the bug Intego mentions. Has anyone else been able to do so?

  • Topher Kessler Level 6 Level 6

    This is not a recommended approach to dealing with this problem. Instead, learn how to use the launchctl utility to either stop or unload the named launch process.