Very Computer

> >We have setup some user groups, using /etc/group, and we're trying to
> >map those groups into a yp domain.

> >For the most part, this is working fine.  We have a synchronization
> >program that we use to extract the desired entries out of our
/etc/group
> >file and stick them in a new group file, located in our /var/yp
> >directory.

> >Then, we do a "make group" and voila, we have yp groups.  However,
there
> >are a couple of groups (our two biggest groups) which are not
working.
> >We get the following warning during the make:

> >Updating group.bygid...
> >makedbm: warning: data too long:

> >So, essentially, when we see this for a particular group, we know
that
> >the group in question is not being added to yp.  This is also
affecting
> >our yp slave server... the master will not push the maps when we do a
> >make and get these warnings.

> >Any advice?  Can we configure yp to use a different dbm scheme, which
> >doesn't have such a "weak" link?  I would think we should be able to
> >have really large groups.

> I think the NIS protocol has a 1024 byte limit on data for a given
key. For
> the group map, the data is the whole line from /etc/group.  I suppose
you
> could hit that with about 110 to 170 members in a single group. If
> this is the problem, you are not going to fix it with a dbm
replacement.
> Any chance of rethinking your group layouts? That is, are you using
groups
> just to identify organization boundaries (in which case you could just
> split them up more), or do you really use them for access control?