Garrett D'Amore writes: > Reserved UIDs for this stuff is probably *not* the best solution. Some > kind of ephemeral IDs, or a separate numbering space that is guaranteed > not to be used with non-local services would be best. Since file > ownerships aren't at stake,
File ownerships are at stake, at least in the case that was originally under discussion. They were allocating yet another UID/GID combination, running the daemon with those values, and installing the database that way. If file ownership really isn't at stake, then everyone can use a single UID (such as the existing "noaccess" user), and the problem goes away. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
