You are planning group names for a new system. You decide to use a numbering convention that
includes the year and month the project began, to form the group number and name for work
associated with that project.
So, for example, a project targeted to begin in January, 2013 would have the number (name):
201301(Pr20l301)
What are the two problems with your plan?
A.
Group names may not contain a numeric character
B.
Group names may be no longer than 7 characters.
C.
Group numbers should not be larger than 60000.
D.
Group names should be all lowercase.
Explanation:
C: The Group ID (GID) field contains the group’s numerical ID. GIDs can be
assigned whole numbers between 100 and 60000.
D: Group names contain only lowercase characters and numbers.
Reference: Setting Up Fields in the Group Database
BD
I go with BC option.
I hate these when the command works….
root@sol11:~# groupadd -g 2015101 Pr201501 && grep Pr /etc/group
Pr201501::2015101:
B & D
From the man page:
The following operands are supported:
group A string consisting of characters from the set of
lower case alphabetic characters and numeric char-
acters. A warning message is written if the string
exceeds MAXGLEN-1, which is usually eight charac-
ters. The group field must contain at least one
character; it accepts lower case or numeric charac-
ters or a combination of both, and must not contain
a colon (:) or NEWLINE.
[C]
https://docs.oracle.com/cd/E19683-01/806-4073/6jd67r94b/index.html
Using Large User IDs and Group IDs
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.
[D]
The Solaris-Groups should be agree with SMB-Groups.
http://docs.oracle.com/cd/E23824_01/html/821-1449/managingsmbgroupsuserstm.html
In order to provide proper identity mapping between SMB groups AND ORACLE SOLARIS GROUPS, an SMB group must have a corresponding Oracle Solaris group. This requirement has two consequences. First, the group name must conform to the intersection of the Windows and Oracle Solaris group name rules. Thus, an SMB group name can be up to eight (8) characters long and contain only lowercase characters and numbers. Second, an Oracle Solaris group has to be created before an SMB group can be created. The Oracle Solaris group is created by using the groupadd command. See the groupadd(1M) man page.
C,D…