From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Description of problem:
I was switching over a ypserver from an SGI machine to one of our
RHEL3 linux servers. When I initially did the switch, I had problems
with netgroups. I could ypcat netgroups but doing a ypmatch on any key
in the netgroup didn't work. I then tested the same yp configuration
on an FC2T2 system and everything worked fine. The netgroups were fine
and everything worked as expected. I then went back to the RHEL3
machine and tried again and had the same result. You could ypcat the
netgroup file but ypmatches failed. This caused lots of problems with
exports, automounts, etc. I then pointed the RHEL3 system at my FC2T2
system (reconfig/restart ypbind) and the netgroup problem went away.
This lead me to believe it was a problem with ypserv.
As a test I rebuilt the rawhide ypserv-2.12.1-2 and tried it on the
RHEL3 system and everything worked as expected. I don't really have
more details as I needed to get this working quickly and didn't have
time for extensive debugging. I've got to believe that the problem is
related to our netgroup file as I've set up another ypserver on an
RHEL3 system with smaller maps and everything just worked.
I can provide copies of any files you need if you want to persue this.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. set up yp from previous existing src files
2. start ypserv
Actual Results: most everything works except the netgroup matching
Expected Results: everything works
I have a simillar problem with ypserv and yppasswd changing. I have
reported this as bug 129308.
I've had issues like this as well, specifically when migrating NIS masters from
Solaris to RHEL. The only problematic map being the netgroup map -- cleaning up
all stray spaces at the end of entries as well as making sure each continuation
of a list is properly formated with *tabs* rather than spaces fixes this for
me. Once I did this, netgroups started working fine.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.