Jimmy_Guse.NSD@LCCMAIL.OCF.LLNL.GOV (Jimmy Guse) (11/22/90)
Reply to: RE>tcplisten problem ? > However page 124 of vol 2 of the manual says: > if na_port equals zero, the service on port 102 is used. My guess is that this is for an initiator. Since my V2,pg.124 is different than yours (I use 6.0), I'm not sure of the context. It needs a port unless it is a static server. Port 102 is used by the TSAP daemon which starts dynamic servers. > p.s. I do have a cmip service defined on port 163 in my etc/services file, > but perhaps isodeserver does not know of this. How should one proceed to > avoid the error mentioned above ? ISODE does not "know" of /etc/services. The relevant info is in $(ETCDIR)/isoentities. isodeserver() turns an AEI (<isoaddrs.h>) into an address. Generally, you obtain the AEI using str2aei, look in ryresponder.c for an example. The "lookup" (passwd) server example which is completely explained in the manual is a useful way to understand how binding works in ISODE. If you are not familiar with the terms static/dynamic server, or isoentities, you need to be. Descriptions are found in (V6.0) V2,Ch.9,pg136+ and V1,Ch.10,pg.159-162, respectively. Essentially, isodeserver determines that the responder is dynamic by the argc/argv that are passed to it (TSAPD appends some "magic" arguments when it invokes a server). If you are indeed writing a responder which listens for connections on port 163 (you manually invoke it), it is a static responder. Jimmy