Hello,
Can someone explain to me how inetd services RPC requests?
Consider the following scenario:
1. portmap is running
2. rpc.ttdbserverd is NOT running
3. a remote machine sends a request intended for
the rpc.ttdbserverd service
Then I notice, on the server machine, that the rpc.ttdbserverd server is
started. This is presumably because of the following line in
/etc/inetd.conf:
rpc.ttdbserverd stream rpc/tcp wait root /usr/dt/bin/rpc.ttdbserverd rpc.ttdbserverd
Here are my questions:
1. On which port does the rpc.ttdbserverd request enter? Is it the
standard RPC service port 111 (I assume this is the port which
portmap listens to)? If so, when the first request arrives,
why doesn't portmap answer with "Program not registered" since,
at that time, the rpc.ttdbserverd isn't running ?
2. The inetd.conf man page states that the service name (the
first field, rpc.ttdbserverd) should be defined in /etc/services.
But "rpc.ttdbserverd" is not in /etc/services! What port is
inetd listening to so that it can start the correct server?
Does inetd stop listening to that port after the server is started?
Although I used rpc.ttdbserverd as an example, I don't understand how any
of the RPC services in /etc/inetd.conf are answered.
Thanks. Will summarize.
-Dave Wolinski
wolinski_at_umich.edu
Received on Wed Oct 20 1999 - 03:08:00 NZDT