UIDs and group IDs (GIDs) can be assigned up to the maximum value of a signed integer, or 2147483647.
However, UIDs and GIDs over 60000 do not have full functionality and are incompatible with many Oracle Solaris features. So, avoid using UIDs or GIDs over 60000.
The following table describes interoperability issues with Oracle Solaris products and previous releases.
Table 4–4 Interoperability Issues for UIDs or GIDs Over 60000
Category |
Product or Command |
Issue |
---|---|---|
NFS interoperability |
SunOS 4.0 NFS software and compatible releases |
NFS server and client code truncates large UIDs and GIDs to 16 bits. This situation can create security problems, if systems running SunOS 4.0 and compatible releases are used in an environment where large UIDs and GIDs are being used. Systems running SunOS 4.0 and compatible releases require a patch to avoid this problem. |
Name service interoperability |
NIS name service and file-based name service |
Users with UIDs greater than 60000 can log in or use the su command on systems running the Solaris 2.5 (and compatible releases). However, their UIDs and GIDs will be set to 60001 (nobody). |
NIS+ name service |
Users with UIDs greater than 60000 are denied access on systems running Solaris 2.5 (and compatible releases) and the NIS+ name service. |
The following table describes UID and GUI limitations.
Table 4–5 Large UID and GID Limitation Summary