bin/39419: default group range cannot be specified for groupadd

[Wolfgang.Stukenbrock%nagler-company.com@localhost]

>Number:         39419
>Category:       bin
>Synopsis:       default group range cannot be specified for groupadd
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Aug 27 10:55:00 +0000 2008
>Originator:     Wolfgang Stukenbrock
>Release:        NetBSD 4.0
>Organization:
Dr. Nagler & Company GmbH
        
>Environment:
        
        
System: NetBSD s401 4.0 NetBSD 4.0 (NSW-S401) #11: Wed Jul 30 21:13:34 CEST 
2008 
wgstuken@s012:/export/NetBSD-4.0/N+C-build/.OBJDIR_amd64/export/NetBSD-4.0/src/sys/arch/amd64/compile/NSW-S401
 amd64
Architecture: x86_64
Machine: amd64
>Description:
        Most default paramters of the user management functions can be 
configured
        in /etc/usermgmt.conf.
        So the administrator can setup a range for new user-id's.
        This is very usefull for environments where the "normal" users are
        included by e.g. NIS and only some techinal users are setup in the local
        configuration files.By setting up a range definition in usermgmt.conf 
and
        using a different range in the NIS database conflicts can be avoided.
        Accedently this is not possible for groups, because there
        is no range definition for group-id's in any configuration file.
        So during package installation new groups may be added using the
        next free group-id starting at 1000. This may lead to conflicts with
        the NIS-database, because the NIS-database cannot know what ID's are 
used
        by some clients and theese ID's may become active in NIS at a later
        time. This could be avoided by defining a default range to be used by
        groupadd as already done for useradd.

>How-To-Repeat:
        not relevant - enhancement-request
>Fix:
        Add a new keyword to usermgmt.conf to add a group range definition.
        The command groupadd should read the information from usermgmt.conf and
        use it if present.
        An other sollution may be a new file groupmgmt.conf, but I think it 
would
        be better (and more consistent) to expand usermgmt.conf.

>Unformatted: