CentOS - Aug 2008 - Need to restart ypserv to update the nis maps

Hi

I use NIS om my network (CentOS4.6). When an update on a map occurs 
(home directory changed in /etc/passwd for instance), I run make -C 
/var/yp/ and check the result on a client. On the client I use "ypcat 
passwd" and find indeed that the update has propagated (the clients run 
ypbind service). On the client I have configured /etc/nsswitch.conf with :
passwd:     files nis
shadow:     files nis
group:      files nis

The problem is however that on the client, if I try to use the new data, 
it still uses the old one. For instance "cd ~john" still directs me to
the old path instead of to the updated path (as correctly reported by 
"ypcat passwd").
To solve it I need to restart the ypserv service on the nis server for 
every change.

Does anyone now what could be the problem or where I should look? 
Apparently the OS gets password and user info using another way than the 
ypcat tool.

(ypserv-2.13-18,ypbind-1.17.2-13)

Thanks,
Theo

Theo Band wrote:
> Hi
>
> I use NIS om my network (CentOS4.6). When an update on a map occurs 
> (home directory changed in /etc/passwd for instance), I run make -C 
> /var/yp/ and check the result on a client. On the client I use "ypcat 
> passwd" and find indeed that the update has propagated (the clients 
> run ypbind service). On the client I have configured 
> /etc/nsswitch.conf with :
> passwd:     files nis
> shadow:     files nis
> group:      files nis
>
> The problem is however that on the client, if I try to use the new 
> data, it still uses the old one. For instance "cd ~john" still
directs
> me to the old path instead of to the updated path (as correctly 
> reported by "ypcat passwd").
> To solve it I need to restart the ypserv service on the nis server for 
> every change.
>
> Does anyone now what could be the problem or where I should look? 
> Apparently the OS gets password and user info using another way than 
> the ypcat tool.
>
> (ypserv-2.13-18,ypbind-1.17.2-13)
>
> Thanks,
> Theo
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
Hi Theo,

As you are talking about the users homes I assume you are providing this 
via something like NFS?

If so it is your autofs information that controls what home gets mounted 
not the passwd information.

You can configure autofs to reference a NIS map.  Normally I would 
expect this to be something like auto_home.  An entry in this file might 
look like
<user>          <server>:<nfs exported dir>:&

And you would have an entry in /etc/auto.master
/home  auto.home

I hope this helps :)

Theo Band wrote:
...
> The problem is however that on the client, if I try to use the new data, 
> it still uses the old one. 
If you run authconfig-gtk on the client and look at the "Options" tab,
is "Cache user information" selected?

Mogens

-- 
Mogens Kjaer, Carlsberg A/S, Computer Department
Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark
Phone: +45 33 27 53 25, Fax: +45 33 27 47 08
Email: mk at crc.dk Homepage: http://www.crc.dk

Theo Band wrote:
> The problem is however that on the client, if I try to use the new data,  
> it still uses the old one. For instance "cd ~john" still directs
me to
> the old path instead of to the updated path (as correctly reported by  
> "ypcat passwd").
> To solve it I need to restart the ypserv service on the nis server for  
> every change.
Are you running nscd, the name service caching daemon?

Ralph
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://lists.centos.org/pipermail/centos/attachments/20080811/117a155c/attachment.sig>

Theo Band wrote:
> Hi
> 
> I use NIS om my network (CentOS4.6). When an update on a map occurs 
> (home directory changed in /etc/passwd for instance), I run make -C 
> /var/yp/ and check the result on a client. On the client I use "ypcat 
> passwd" and find indeed that the update has propagated (the clients
run
> ypbind service). On the client I have configured /etc/nsswitch.conf with :
> passwd:     files nis
> shadow:     files nis
> group:      files nis
> 
> The problem is however that on the client, if I try to use the new data, 
> it still uses the old one. For instance "cd ~john" still directs
me to
> the old path instead of to the updated path (as correctly reported by 
> "ypcat passwd").
> To solve it I need to restart the ypserv service on the nis server for 
> every change.
> 
> Does anyone now what could be the problem or where I should look? 
> Apparently the OS gets password and user info using another way than the 
> ypcat tool.
Are your running nscd on the clients?

If so, try disabling nscd and see if that make a difference.

James Pearson