This discussion is archived
1703 Views 7 Replies Latest reply: Feb 21, 2008 11:06 AM by jclark
Currently Being ModeratedFeb 19, 2008 3:46 PM (in response to jclark)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
Currently Being ModeratedFeb 19, 2008 4:20 PM (in response to jclark)Jeff,
No, there's no Netinfo Manager. The closest thing to it is Directory Utility.app, 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>.
Scott17" Macbook Pro, Mac OS X (10.5.1)
Currently Being ModeratedFeb 19, 2008 5:15 PM (in response to Scott Radloff)Thank you for the info ( and backround! ) - will give it a try on the morrow and report back.
jeffMac OS X (10.4.9)
Currently Being ModeratedFeb 19, 2008 6:05 PM (in response to jclark)Have you tried Workgroup Manager that comes bundled with Server Admin Tools 10.5. It is available as a separate d/l from Apple.
BainMac OS X (10.5.2)
Currently Being ModeratedFeb 19, 2008 9:34 PM (in response to Jeff Clark6)Jeff,
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.
Scott17" Macbook Pro, Mac OS X (10.5.1)
Currently Being ModeratedFeb 19, 2008 9:47 PM (in response to xnav)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)
Currently Being ModeratedFeb 21, 2008 11:06 AM (in response to Scott Radloff)Sorry for the delay - but Life® has this mysterious way letting you know that your plans are only your plans...got to it this morning..
Anyway, thank you Scott very much for the solution ( well I think it is... time will tell - so far so good! ) - things behaving MUCH bettah now... Looks like copying files over from 10.4.x to 10.5.x by hand are fraught with downside... hopefully using migration Assistant obviates all future Sturm und Drang...
Another reason to have good ( and many ) backups....
Thanks again and I'm off to start another thread on disappearing HD icons...
ps - Bain - I got the Server Admin Tools and they look like they will come in handy in the future - thanks!several, Mac OS X (10.5.1)