by Not too sure what's going on here, but I just added a group to my system
with the groupadd command, and I noticed some odd behaviour. groupadd did
add the group as I expected, but it didn't properly increment the GID as it
should (as described in the manpage).
At first I figured that it must have been because I had a dash in the
groupname -- which generates the same error message -- but I tried a more
simplistic name and I got the same results (GID 100).
Further experiments on an friend's Ultra1 shows the "proper" behaviour.
System:
SPARCstation5 running Solaris9 12/02
Recommended and J2SE_Recommended patch clusters from late November installed
access via serial
Commands:
# groupadd drop-box
UX: groupadd: drop-box name should be all lower case or numeric.
# cat /etc/group
<snip type="default_groups" />
sshd::100:sshd
drop-box::100:
--------------------------------------------------------------------------- System: Commands: --------------------------------------------------------------------------- Manpage excerpt: -g gid -o Allows the gid to be duplicated (non-unique). --
Ultra 1 running Solaris9 08/03
no patches (at least that I can verify... box isn't mine)
access via SSH
# groupadd test ; groupadd test2 ; groupadd -g 110 test3 ; groupadd test4 ;
cat /etc/group
<snip type="default_groups" />
test::100:
test2::101:
test3::110:
test4::111:
OPTIONS
The following options are supported:
Assigns the group id gid for the new group. This group
id must be a non-negative decimal integer below MAXUID
as defined in /usr/include/sys/param.h. The group ID
defaults to the next available (unique) number above
the highest number currently assigned. For example, if
groups 100, 105, and 200 are assigned as groups, the
next default group number will be 201. (Group IDs
from 0-99 are reserved by SunOS for future applica-
tions.)
A steer is just a bull that's been...
Well, let's just say he doesn't make much time with the ladies.
-- Alton Brown