Permission loss after migration.

Discussion in 'macOS' started by HippoMan, Jul 20, 2009.

  1. HippoMan macrumors newbie

    Joined:
    Jul 19, 2008
    #1
    I recently got a new MacBook Pro and migrated from my older MacBook Pro using the Migration Assistant. I'm running 10.5.7. Pretty much everything transferred OK, but now when I log in to my user account on the new machine and try to run launchctl load ..., I get the following error:

    launch_msg(): Socket is not connected

    These same launchctl commands didn't use to cause an error on my old machine before the migration. Also, launchctl works fine as the root user.

    The user ID, login name, and entire directory structure are the same for my user account on the new machine as they were on the old machine; nonetheless, something must be different about it on the new machine.

    I'm guessing that this is some sort of permission issue, because I'm noticing that I get asked for the root password more frequently during software installs, etc., than I used to get asked on the old machine.

    Can anyone suggest how I can diagnose this apparent permission problem and, of course, how I can fix it?

    Thanks in advance.
    .​
     
  2. iBookG4user macrumors 604

    iBookG4user

    Joined:
    Jun 27, 2006
    Location:
    Seattle, WA
  3. HippoMan thread starter macrumors newbie

    Joined:
    Jul 19, 2008
    #3
    Reinstalling what program? The launchctl utility is part of MacOSX. Are you suggesting that I reinstall the entire operating system?
    .​
     
  4. iBookG4user macrumors 604

    iBookG4user

    Joined:
    Jun 27, 2006
    Location:
    Seattle, WA
    #4
    Yes, you could try an archive and install. Perhaps some files were not installed correctly the first time.
     
  5. HippoMan thread starter macrumors newbie

    Joined:
    Jul 19, 2008
    #5
    Thank you, but that's a time-consuming, complicated procedure, and I'd rather save it as a last resort.

    I'm hoping that there's something I can do with file system permissions or user permissions that might fix this.

    Does anyone know what is the full pathname of the launchd communication socket? I might just need to do an appropriate chmod on that socket file or the directory it resides in.
    .​
     

Share This Page