topic Re: NIS bug? in Operating System - HP-UX

NIS bug?

E. Meng Tan — Fri, 19 Oct 2001 14:09:59 GMT

HELP!

make group returns with an error whenever I add more than 132 users to any NIS group.

Using SAM to add users to a group was very uninformative as it indicated it make the change and attempted to push the files out but there were hung yppush processes out there. Making manual changes to the group files and issuing make group return the error (just exit code 1).

I am running HP 10.20 on regular NIS (not NIS+) on a D310 system.
How do you find out what version of ypbind and ypserv you are running?
Still waiting for HP support to call back.

Any help is greatly apreciated.

Thanks

E.M.TAN

etan@transunion.com

Re: NIS bug?

Alex Glennie — Fri, 19 Oct 2001 14:24:13 GMT

Could your group lines be exceeding the LINE_MAX of 1024. As a result, your group
maps aren't getting pushed ?

Re: NIS bug?

Sachin Patel — Fri, 19 Oct 2001 14:26:19 GMT

Hi Meng,
#rpcinfo -p systemname
Will give you the version of ypbind and ypserv.

I don't know that 132 is limit on group or not. When did you have last install nis patch?

Sachin

Re: NIS bug?

A. Clay Stephenson — Fri, 19 Oct 2001 15:11:37 GMT

Hi:

You have a group entry that is too large. The solution is rather simple: Split your large group entry into smaller chunks: It is perfectly legal to have identical entries with the same groupname and group id. Only the FIRST will actually be mapped by NIS so that ypcat group will only list those members in the first entry for the large group. Since primary group membership is specified in the passwd map all should be well - unless you have large numbers of people who are members of multiple groups. In that case, those guys should be placed in the first group entry and trhose that are not members or multiple groups should be placed in the subsequent group entry. This is not really a bug but rather a size limitation for a single NIS map entry.

Clay