On Jul 25, 2011, at 7:16 PM, Rodolfo Aramayo wrote: > David is right. This is a hard issue and believe me I have burn many, > many candles during Holidays and weekends trying to solve userIDs > conflicts in MacOSServers. > > It looks to me that MacPorts installer has these options: > > 1. Look if the machine is a server > 2. If NOT a server then: > 3. Either just create the 'user:macports group:macports' account picking: > a. the next available UUID account number (somewhere in the 500s) > b. using a pre-determined UUID and GUID, say 600... > c. giving the user the option to select which one or what > > =>I assume that if the machine is not a server but IS listening to a > server through OD it does not matter, as long as there are UUIDs in > the 500s available > > 4. If the machine is a server then: > 5. Check if the server is listening to an OD and if yes then either > quit and request a user 'macports' and a group 'macports' be created > on the master OD or proceed to create the user 'macports' and a group > 'macports' on the master OD. > 6. If however the server is running a 'local directory' then test if > all 500 numbers are taken and of they are proceed to create a user > 'macports' and a group 'macports' in the 1000s. Because the server is > running a local directory this should be OK, because all the users in > the 1000s should be accounted for. > > The problem is when you pick a user 'macports' and a group 'macports' > without testing the server/non-server/local/master OD configuration > > Am I missing something?
What if MacPorts were simply always to try to find an unused id in the range 500 - 1000, using whatever algorithm is convenient? James _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
