Let's say I have a Solaris 8 box, nismaster, which is the nis master
server for my little network. A Solaris 9 box, nisslave is the slave
server. Then, I have a few U10s and Sunblade100s running Sol8 and a U1
running Solaris 9 being the nis clients. In each machine, the OS is
patched as of last month. All clients know both servers and the nis
domain both defined in their respective /etc/hosts and as nis servers.
In nismaster, the maps are stored in /var/yp/src; /var/yp/makefile is
aware of that.

I deleted some old users off the nis passwd and auto-home files and then
pushed the maps (as in running /var/yp/makefile). All the Sol8 clients
see the changes, but the U1 still clings to the old maps (ypcat passwd
in the U1 shows the old users still around). I even tried rebooting it
and had no luck. What should I check for next?
--
Mauricio raub-kudria-com
(if you need to email me, use this address =)

Mauricio wrote:

> Let's say I have a Solaris 8 box, nismaster, which is the nis
> master server for my little network. A Solaris 9 box, nisslave is the
> slave server. Then, I have a few U10s and Sunblade100s running Sol8
> and a U1 running Solaris 9 being the nis clients. In each machine, the
> OS is patched as of last month. All clients know both servers and the
> nis domain both defined in their respective /etc/hosts and as nis
> servers. In nismaster, the maps are stored in /var/yp/src;
> /var/yp/makefile is aware of that.
>
> I deleted some old users off the nis passwd and auto-home files and
> then pushed the maps (as in running /var/yp/makefile). All the Sol8
> clients see the changes, but the U1 still clings to the old maps
> (ypcat passwd in the U1 shows the old users still around). I even
> tried rebooting it and had no luck. What should I check for next?

Start by using ypwhich -m passwd to see whether the U1 is getting its
passwd map from the master server or from the slave. If it's the slave
server, the simplest fix may be to remove the old map from the slave and
push the new one again.