Hi Lance,

Did you find a solution to this problem? We are running 6.1R1 and have the same issue. As of today there is no fix for this, the only workaround is to have the groups locally on the filer, but that defeats the whole purpose for NIS. The problem has to do with the way YP stores its maps using dbm format (I think NIS+ in yp compatibility mode emulates dbm for yp clients). As far as I know there is a limitation on a single entry in dbm file which can not exceed 1024. It would be nice if filers could read NIS+, but I don't think this will happen.

Can anyone else comment on that?

Roman.

Thanks to all for your help. As it turns out the problem is if a group line on your NIS+ server exceeds 1024 chars the filer will stop processing the NIS entry once it sees that line. So all groups after that are non-existant!

I understand this is fixed in 6.0 but don't know for sure. If not there should atleast be a warning in the log file that says you may have exceeded the 1024 char limit in a particular NIS map.

Hi Lance,

When the group cache is created, if there are duplicate entries, a message

will

be logged. Are there any such messages logged?

Thanks, -Devi

-----Original Message----- From: Lance R. Mehle [mailto:mehlel001@hawaii.rr.com] Sent: Saturday, October 14, 2000 3:13 PM To: Toasters (E-mail) Subject: NIS groups not showing up

Hi all,

I have a problem that I was wondering if any of you have seen.

We have a little over 2000 groups in our NIS+ environment. When I check the

nis_cache file on the filer about 399 are missing. A ypgroup also shows the

group(s) missing from the filer although a ypmatch can find the group(s). It also appears that the same groups are effected all the time.

The groups are fine on the UNIX side.

Help!

Lance