Bug 6446 - Can't enter additional groups that take up more than 200 characters
Summary: Can't enter additional groups that take up more than 200 characters
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: linuxconf
Version: 6.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-10-28 04:33 UTC by web
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-12-15 20:59:53 UTC

Attachments (Terms of Use)

Description web 1999-10-28 04:33:18 UTC
when editing/adding normal users, the additional groups
field takes only 200 characters and truncates the rest, but
doenot show this in the field (you may type many more
characters than this) After removing groups over the 200
character limit and quiting/saving - the group file must be
edited manually to include the missing additional group

Comment 1 Michael K. Johnson 1999-12-02 18:56:59 UTC
Jacques, I assume this was fixed along with the blank group
problem, correct?

Comment 2 Dale Lovelace 1999-12-02 20:14:59 UTC
This is (fixed?) in linuxconf-1.16r10. You can't type past 200 characters in the
"supplemental groups" field. This version of Linuxconf should be in the next
Rawhide release.

Comment 3 Michael K. Johnson 1999-12-02 21:31:59 UTC
Reopened until we actually release linuxconf-1.16r10-1 or later as an
errata update.

Comment 4 Michael K. Johnson 1999-12-03 01:37:59 UTC
Jacques says that the interface will change to be able to add more groups
in the future.  In linuxconf-1.16r10, the 200 character limit will be better
enforced so that typing won't be lost.  The short-term workaround is to use
groupmod until linuxconf has fuller support for editing group lists.

Note that NGROUP_MAX is set to 32 in Linux and is not likely to change in
the forseeable future, so a user can be in a maximum of 32 suplementary

Comment 5 Michael K. Johnson 1999-12-15 20:59:59 UTC
1.16r10-2 released

Note You need to log in before you can comment on or make changes to this bug.