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
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
Clint Dilks wrote:
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
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
On Mon, Aug 11, 2008 at 11:05:58AM +0200, Theo Band wrote:
I actually have problems that passwords don't get updated. I noticed
that by changing the home directory in /etc/passwd. When I change that
from /home/user to /nobackup/home/user it does work with ypcat passwd (I
see the correct
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
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
Mogens Kjaer wrote:
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
I have not enabled this option.
8 matches
Mail list logo