| From your description, it sounds like your customer has enabled
Enhanced Security. XIsso and XSysAdmin are designed to only work with
Enhanced Security enabled. You can find further information on what
Enhanced Security is in the Security Manual.
The gui interface for Enhanced security (XIsso and XSysAdmin) was replaced
completely for V4.0 of Digital UNIX, so the corruption of the database that
your customer is seeing (following name appended to entry) is fixed
in V4.0. But, I looked at the interface for V4.0 (dxaccounts), and it looks
like in dxaccounts the length of a group name is restricted even further,
to 8 characters.
The security development group "owns" the /etc/group file. We have placed no
limits on the length of a group name in the /etc/group file, except that the
group name must fit in the internal buffer of the library routines created to
manipulate the /etc/group file entries (see man getgrent.3). This buffer is
8192 bytes, so at the lower level the length of a group name is essentially
unrestricted. But, we have no control over what limits are placed on group
name length by other commands and applications.
For example, if your customer is using vi to edit the /etc/group file the
maximum length of a line of the file (including the group name) is 2048 bytes,
the maximum length of a line allowed by vi. If your customer is using NIS to
distribute group entries, the maximum length of a group entry (including the
group name) that can be distributed over NIS is, I think, 1024 bytes. The
addgroup(1) command restricts the group name to 8 characters. I could go on
and on...
Since each of these commands and applications is "owned" by a different
development group, if you want the problem of group name length restrictions
fixed, you'll have to open a QAR or IPMT case against every command and/or
application that you want changed.
[Posted by WWW Notes gateway]
|