Skip navigation
This discussion is archived

What is the 10.5 replacement app for NetInfo Manager in 10.4?

1703 Views 7 Replies Latest reply: Feb 21, 2008 11:06 AM by jclark RSS
jclark Level 1 Level 1 (5 points)
Currently Being Moderated
Feb 19, 2008 2:48 PM
Am reasonably sure I'm having user/permission issues ( apps blowing up when printing or saving a file ), (unknown user) populating many getinfo windows. Clean install of 10.5/1/2, then dragging over files from my old account ( 10.4.11, files rescued by Data RescueII ) ) to new drive. Much screwey-ness ensues...

Anyway, I'm thinkin' that a trip through NetInfo Manager would do the trick, ( realign User/Group ID's, etc. ) - but no can find. Is there a central place to this in 10.5? Or is 10.5 not quite fully baked yet...?

several, Mac OS X (10.5.2)
  • xnav Level 5 Level 5 (6,625 points)
    Leopard does not have a replacement for Tiger's NetInfo.
    Mac Pro 2x3GHz Dual, Mac OS X (10.5.2), BootCamp WinXP, LinkSys WRT54G, iPhone, AppleTV
  • Scott Radloff Level 6 Level 6 (14,490 points)

    No, there's no Netinfo Manager. The closest thing to it is Directory, but it doesn't handle users and groups like NM did.

    There is a command line application to manipulate users and groups, but it is not well documented at this time. A better, GUI alternative is to download and install the OS X Server Tools, and use the Workgroup Manager utility (yes, it works perfectly well on OS X client).

    However, your problem has nothing to do with "wonky" groups, but rather incorrect group ownership. You don't need to mess with the database, but rather you need to correct the ownership of the files. First, a bit about Leopard...

    In recent versions of OS X (as you probably know), a paradigm has been in place where users are given a unique group based on their short name and UID. For whatever reasons, Apple has backpedaled on this, and users have now been returned to the "staff" group, globally. Given the fact that we are now securely in the realm of ACLs, instead of traditional POSIX permissions, this makes a lot of sense.

    The problem, though, is that files and folders migrated from an earlier system will, in many cases, retain the old group ownership, and Leopard has no way to recognize such. Thus, the dreaded "unknown" group. Fortunately, this can easily be corrected with a simple, but carefully-applied command in Terminal:

    <pre style="overflow:auto; font-family: 'Monaco'; font-size: 10px">sudo chown -R username:staff /some_directory</pre>

    In the above command, you must replace "username" with your own short name (or that of the user to whom you wish to grant ownership). For the "/some_directory" variable, I would recommend just dragging the folder in question into the Terminal window from the Finder. Just make sure that you do not change the ownership of any system files, and everything should be fine.

    When you press <RETURN> after typing this command, you will be asked for your admin password. Enter it (it will not be echoed) and again press <RETURN>.

    17" Macbook Pro, Mac OS X (10.5.1)
  • Jeff Clark6 Calculating status...
    Thank you for the info ( and backround! ) - will give it a try on the morrow and report back.

    Mac OS X (10.4.9)
  • Bain Calculating status...
    Have you tried Workgroup Manager that comes bundled with Server Admin Tools 10.5. It is available as a separate d/l from Apple. tml

    Mac OS X (10.5.2)
  • Scott Radloff Level 6 Level 6 (14,490 points)

    I should mention, if you don't already know, that the command I gave will operate recursively, meaning that it is intended to be applied to a folder that contains files-to-be-changed. You wouldn't want to use this on any folder that might contain files that should be owned by someone else, especially system files (which, of course, should be owned by "system").

    For example, let's assume that all of your "problem files" have been dropped into your HOME folder. It is perfectly OK to apply the command to the entire HOME folder, and any files that have been placed within, regardless of the location or how "deep" they have been placed, will be corrected.

    It can also be applied to entire external or secondary volumes, AKA disks mounted on your Desktop, as long as there are no systems installed on those volumes. It would also be nice if all the files on such a volume should belong to you

    If the problem is with an application itself, and not the data associated with that application, you wouldn't want to use the command I have given. Instead, ownership should be changed to "system" or "root," with a group ownership of "admin." It might also be necessary in the case of an application to change the permissions (the "mode") for the application itself. If such is your case, please post back and I can give instructions specific to this.

    17" Macbook Pro, Mac OS X (10.5.1)
  • baltwo Level 9 Level 9 (59,150 points)
    Directory Services now does that. See Analysis: The end of Netinfo for details. The GUI replacements in Leopard are Get Info->Sharing and Permissions, Sharing prefPane, and Accounts prefPane, CONTROL-click on a user's name after unlocking the lock. Finally, dscl and it's derivatives are the CLI replacements.
    G4 450 MP Gigabit 1.5 GB RAM/17" Flat-panel 1GHz iMac, Mac OS X (10.5.2), (also 10.4.11/9.2.2)


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.