144743Smarkm@(#) README.IRIX 1.2 94/12/28 18:45:58 244743Smarkm 344743SmarkmIn the past few months I received several messages with questions from 444743Smarkmpeople that tried to use my tcp wrapper on IRIX 5.x. Some mysteries 544743Smarkmcould be solved via email, and then some remained. 644743Smarkm 744743SmarkmToday I finally had a chance to do some tests on someones IRIX 5.2 844743Smarkmsystem. Here is my first-hand experience with wrapper release 6.3. 944743Smarkm 1044743Smarkm(1) Inetd is broken. Normally one edits inetd.conf, sends a HUP signal 1144743Smarkm to inetd and that's it. With IRIX evil things happen: inetd is too 1244743Smarkm stupid to remember that it is already listening on a port. 1344743Smarkm 1444743Smarkm In order to modify an entry in inetd.conf, first comment it out 1544743Smarkm with a # at the beginning of the line, kill -HUP the inetd, then 1644743Smarkm uncomment the inetd.conf entry and kill -HUP again. 1744743Smarkm 1844743Smarkm Even with this amount of care I have seen inetd messing up, like 1944743Smarkm calling rusersd when I make a talk connection. Even killing and 2044743Smarkm restarting inetd does not solve all problems. 2144743Smarkm 2244743Smarkm I find it hard to believe, it but the best thing to do with IRIX is 2344743Smarkm to reboot after changing inetd.conf. 2444743Smarkm 2544743Smarkm(2) When tcpd is built according to the irix4 Makefile rules, it 2644743Smarkm appears to work as expected with TCP-based services such as 2744743Smarkm fingerd, and with UDP-based services such as ntalk and tftp. 2844743Smarkm 2944743Smarkm(3) It does NOT work with RPC over UDP services such as rusersd and 3044743Smarkm rstatd: the wrapper hangs in the recvfrom() system call, and I 3144743Smarkm have spent several hours looking for ways to work around it. No 3244743Smarkm way. After finding that none of the applicable socket primitives 3344743Smarkm can be made to work (recvfrom recvmsg) I give up. So, the IRIX RPC 3444743Smarkm services cannot be wrapped until SGI fixes their system so that it 3544743Smarkm works like everyone elses code (HP Sun Dec AIX and so on). 3644743Smarkm 3744743Smarkm(4) I didn't even bother to try the RPC over TCP services. 3844743Smarkm 3944743Smarkm(5) When an IRIX 5.2 system is a NIS client, it can have problems with 4044743Smarkm hosts that have more than one address: the wrapper will see only 4144743Smarkm one address, and may complain when PARANOID mode is on. The fix is 4244743Smarkm to change the name service lookup order in /etc/resolv.conf so that 4344743Smarkm your system tries DNS before NIS (hostresorder bind nis local). 4444743Smarkm 4544743Smarkm(6) IRIX 5.2 is not System V.4, and it shows. Do not link with the 4644743Smarkm -lsocket and -lnsl libraries. They are completely broken, and the 4744743Smarkm wrapper will be unable to figure out the client internet address. 4844743Smarkm So, TLI services cannot be wrapped until SGI fixes their system so 4944743Smarkm that it works the way it is supposed to. 5044743Smarkm 5144743SmarkmI am not impressed by the quality of the IRIX system software. There 5244743Smarkmare many things that work on almost every other system except with IRIX. 5344743Smarkm 5444743Smarkm Wietse 55