From owner-freebsd-bugs  Sun Jun 18 09:26:07 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id JAA18239
          for bugs-outgoing; Sun, 18 Jun 1995 09:26:07 -0700
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA18233
          ; Sun, 18 Jun 1995 09:26:03 -0700
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.11/8.6.9) id MAA03947; Sun, 18 Jun 1995 12:25:43 -0400
Date: Sun, 18 Jun 1995 12:25:43 -0400
From: "House of Debuggin'" <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199506181625.MAA03947@skynet.ctr.columbia.edu>
To: freebsd-bugs@freebsd.org, wilcox@math.psu.edu
Subject: Re: More on NIS problems
Cc: bugs@freebsd.org
Sender: bugs-owner@freebsd.org
Precedence: bulk


>	I've seen a lot of nis problems running around. Here is my input.
>have a FreeBSD 2.0.5R machine being the master server for what is going
>to be a ton of freebsd machines. I have this for my netgroup file

>staffhost1 (machine.xxx.yyy.zzz,-,) (machine2.xxx.yyy.zzz,-,)
>staffhost2 (machine3.xxx.yyy.zzz,-,) (machine4.xxx.yyy.zzz,-,)
>staffhosts staffhost1 staffhost2

>Then when I do ypmatch staffhosts netgroup I get
>staffhost1 staffhost2   staffhosts staffhost1 staffhost2

>If I try to expand this in any fashion, it gets real ugly real quick.

>Any reason this is doing this?

>-Ken Wilcox

Yeah: the reason is the 'netgroup' (and 'ethers.*' and 'bootparams')
targets in /var/yp/Makefile are a little goofy. (My fault I'm afraid:
I'm not terribly good with awk.) I just commited a fix to -current.
Here's a diff that should fix the problem. Apply this to a virgin copy
of /var/yp/Makefile, then remangle it to fit your system. The first
hunk will undoubtedly fail since the CVS id strings may not match
exactly. You can safely ignore the error.

4c4
< # $Id: Makefile.yp,v 1.7 1995/05/30 05:05:34 rgrimes Exp $
---
> # $Id: Makefile.yp,v 1.6 1995/04/02 01:53:47 wpaul Exp $
29c29
< #
---
> # 
121c121
< 		print $$0"\t"$$0 }' $^ | $(DBLOAD) -i $(ETHERS) \
---
> 		print $$2"\t"$$0 }' $^ | $(DBLOAD) -i $(ETHERS) \
132c132
< 		print $$0"\t"$$0 }' $^ | $(DBLOAD) -i $(ETHERS) \
---
> 		print $$1"\t"$$0 }' $^ | $(DBLOAD) -i $(ETHERS) \
143c143
< 		print $$0"\t"$$0 }' $^ | $(DBLOAD) -i $(BOOTPARAMS) \
---
> 		print $$0 }' $^ | $(DBLOAD) -i $(BOOTPARAMS) \
154c154
< 		print $$0"\t"$$0 }' $^ | $(DBLOAD) -i $(NETGROUP) \
---
> 		print $$0 }' $^ | $(DBLOAD) -i $(NETGROUP) \


Note that I'm currently working on closing out three NIS-related
problem reports (508, 509 and 510) which have to do libc's handling
of netgroups. I have preliminary fixes for 508 and 509, and I'm
still working with Bill Fenner to try and resolve 510 (he claims
that the +@netgroup host matching in /etc/hosts.equiv doesn't work,
but I haven't been able to duplicate the problem, so I'm kinda
stumped). PR #508 and #509 shouldn't affect you unless you have
certain errors in your netgroup database, but if you run into
problems I can send you a patch. On the other hand, if you *do*
have +@netgroup host matching working, I'd like to hear about
it so I'll know I'm not crazy.

If you uncover any other problems, don't hesitate to report them.

-Bill

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~T~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Bill Paul            (212) 854-6020 | System Manager
Work:         wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home:  wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Møøse Illuminati: ignore it and be confused, or join it and be confusing!
~~~~~~ "Welcome to All Things BSDish! If it's not BSDish, it's crap!" ~~~~~~~