Has anyone else had a problem with Tripwire and NIS? Here is the scenario:

1. Tripwire is running without problems.
2. Get NIS running for NIS server and NIS clients; all is working except for netgroups. But Tripwire is still working.
3. Get NIS running using netgroups without any problems.
4. But, now Tripwire stops working. It gives the following error message: “Software interrupt forced exit: Segmentation Fault”
5. When I have a problem I always go back to the last change I made on the system. That would be getting NIS running with netgroups. So, I go back over every change I made and narrow it down to the following change in /etc/nsswitch.conf
Change from:
passwd: compat
shadow: compat
group: compat
passwd_compat: nis files
shadow_compat: nis files
group_compat: nis files
Change to:
passwd: nis files
shadow: nis files
group: nis files
6. Now Tripwire works, but NIS netgroups doesn’t work.

System Configuration:
RedHat Enterprise Linux AS release 3 (Taroon Update 3)
Kernel 2.4.21-20.EL
ypserv 2.8-7
ypbind 1.12.5
gcc 3.2.3-42
tripwire 2.3.1-17

When I do a web search on “tripwire segmentation fault” a lot of info is returned about gcc versions and tripwire segmentation faults.

I’m relatively new to Linux; can anyone give me any insight on the connection between tripwire and NIS? My software updates a through rpms from RedHat Network, but I they don’t have the newest versions of ypserv or ypbind will that make a difference?

Thanks,