UIDs and 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 Solaris features, so avoid using UIDs or GIDs over 60000.
The following table describes interoperability issues with Solaris products and previous Solaris releases.
Table 4–2 Interoperability Issues for UIDs/GIDs Over 60000
Category |
Product/Command |
Issues/Cautions |
---|---|---|
NFSTM Interoperability |
SunOSTM 4.0 NFS software and compatible versions |
NFS server and client code truncates large UIDs and GIDs to 16 bits. This can create security problems if SunOS 4.0 and compatible machines are used in an environment where large UIDs and GIDs are being used. SunOS 4.0 and compatible systems require a patch. |
Name Service Interoperability |
NIS name service and file-based name service |
Users with UIDs above 60000 can log in or use the su command on systems running the Solaris 2.5 and compatible versions, but their UIDs and GIDs will be set to 60001 (nobody). |
|
NIS+ name service |
Users with UIDs above 60000 are denied access on systems running Solaris 2.5 and compatible versions and the NIS+ name service. |
Table 4–3 Large UID/GID Limitation Summary