Subject: Re: Help with YP
To: None <firstname.lastname@example.org>
From: maximum entropy <email@example.com>
Date: 06/29/2001 16:11:33
>Date: Fri, 29 Jun 2001 12:56:42 -0700
>From: "Aaron J. Grier" <firstname.lastname@example.org>
>On Thu, Jun 28, 2001 at 05:50:29PM -0400, maximum entropy wrote:
>> I'm trying to add a Solaris 7 client, and I can't figure out how to
>> add the shadow map. I added "shadow" to the "all" lines in the yp
>> Makefiles on zippy, and did a "make" in /var/yp, which built the
>> shadow.byname.db file. But it complains:
>> yppush: error finding master for shadow.byname in grok: No such map in
>> server's domain
>> The slave server doesn't get the new map, and "ypcat shadow" doesn't
>> work. What do I need to do to add this map to the maps that the yp
>> servers know about?
>NetBSD normally uses master.passwd.byname instead of shadow.byname.
Yes I know; I was trying to get the NetBSD server to serve the shadow
file to a Solaris client.
>on zippy, can you ypcat shadow.byname?
I finally got it to serve the shadow file -- by reinitializing my
entire YP setup on both the master and slave servers from scratch.
It didn't really help my situation though, because evidently Solaris 7
doesn't use the shadow.byname map. Either the comments in NetBSD's
makefiles are wrong, or they apply to some other version of Solaris.
Solaris 7 actually seems to want the passwords in the passwd map.
I could hack up the makefiles to splice the shadow passwords back into
the passwd map, but at this point I think I'll just settle for local
/etc/passwd entries on the Solaris machine.
entropy -- it's not just a good idea, it's the second law.