UNIX for Advanced & Expert Users

hi all,

I have a NIS trouble on a server.
when I create a file on a server (server1), the group of this file is the number of the group and not its name.
when I create a file with this group on another server which depends of another NIS slave, the file is created with the group name.
when I create a new group in the group map on the master, on this server ( server1 ), the new group name is not recognize.
I modified the group map by creating a new group, I did a make and I forced the synchronization of the map on the slave with :

# ypxfr -h masterNIS -d domain_name group.bygid

the answer was the master version is not newer

I think it's a synchronisation pb with the group.bygid map...

need your help....

thx

The first step is to ypcat the NIS group file on all machines and make sure the NIS group file is seen everywhere. If it isn't, make sure ypbind is running and that each machine is bound to an NIS server using ypwhich. As for the ypxfer, assuming you haven't mucked around with the Makefile in /var/yp, the timestamps on the group source and the dbm group maps (i.e. group.bygid, etc.) determines if the map is pushed out or not. Try using the touch command to update the timestamp on the group source file and then use make in /var/yp to push it out. If it still doesn't push, please give the exact error message here and we will try to figure it out.

Thx for your reply

I modified passwd and group maps on NIS master and did a make which ended with no error. Replication is ok on all slaves, except on slave server1 where .byuid and .bygid are not updated. But ypcat on server1 gives all correct informations from the map.byname, i supposed...

sorry, the nis slave is not server1, server1 is the server which depend of the slave which has error...

Okay, I'm a little confused now. You have an NIS master and an NIS slave. Host server1 is an NIS client bound to the NIS slave?
If this is correct, I think you said that ypcat group on server1 shows the correct data. Is this true? If it is, what makes you think the group map is not getting updated. On which machine is ypcat failing to show the correct info?

hi, thx for your patience...

>>Okay, I'm a little confused now
*sorry, sorry for my bad english...

>>You have an NIS master and an NIS slave. Host server1 is an NIS client bound to the NIS slave?
*yes, server1 is bind to nisslave1( and every other slaves work fine )

>>I think you said that ypcat group on server1 shows the correct data. Is this true?
*yes, it is surprising, but i think correct data come from passwd.byname or group.byname, i think i have a synchronisation Pb with group.bygid and passwd.byuid.

>>what makes you think the group map is not getting updated. On which machine is ypcat failing to show the correct info?
* i have a user1 in group1(GID=100) (this group exists for a long time)
i have a user2 in group2(GID=200) (this group is a newly created group)

on the server1
when i create a file with user1, the file owner is user1 group1
when i create a file with user2, the file owner is user2 200

on a server2 which binds to an other nis slave ( nisslave2) the owner is
user1 group 1 & user2 group2
and on nisslave2 the synchronisation is ok...

that's why i think it could be a nis probleme.

It does indeed look like some type of sync problem with group.bygid. It looks like the UID is getting translated by the map. Only the GID is the problem. The file is probably corrupted. To make sure everything is clean, I would re-intialize nisslave1 as a yp slave. You could probably just get rid of the group.bygid file, touch group on the master, and push the maps out. But a total re-init would give you a completely clean slave.