Problems with NIS groups

[Steve Brown]

I seem to be having a problem getting the groups to work correctly with
NIS (yp)... It should be noted NIS seems to have no problems w/ any other
maps

My NIS server is a Sun 3/160 running SunOS 4.1, with eight slave servers
-- One 4/390, Two 3/260's, Five 3/160's all running SunOS 4.1

The following entry is in the NIS masters group file:

judge:*:1025:aldrin,judge-0,judge-1,judge-2,judge-3,judge-4,judge-5,judge-6,steve

Now, I go to any machine (except NIS master) and type groups and get:

staff daemon news tty source ocean operator account public sound

While on my NIS master I get:

staff daemon news tty source ocean operator account public sound judge

Now, from any machine if I use the ``groups'' command (``groups steve'') I
am listed as being in group judge... 

My group file on a client/slave is:

none:*:0:
daemon:*:1:
kmem:*:2:
mem:*:2:
staff:*:10:
operator:*:28:
+:

Now, if I edit my group file to make it:

none:*:0:
daemon:*:1:
kmem:*:2:
mem:*:2:
staff:*:10:
operator:*:28:
+judge:               <--- Note the addition
+:

and logout and log back in, I *am* listed as being in group judge with
just the group command ... and if I take ``+judge:'' out I am no longer
placed in group judge...

A few notes:

  o This happens to people who are in less than eight groups
  o This happens with any group, not just ``judge'' -- I know
    it has happened to group 11 (laser) and others.
  o Many of the other groups you see listed (tty,source,etc.) are working
    fine -- done the same as judge, a group in the NIS master file.
  o I have tried reinitializing NIS on the 4/490 (ypset -s master) and
    still was not listed in group
  o On the machine in question, ``ypmatch judge group'' shows groups judge
    just as it should be... with me in that group...

Please respond if you have any suggestions.

Steve Brown <steve at cs.odu.edu>