pdserver server port details

InfoPrint Manager sets aside and assigns pdserver server-to-server ports automatically. Just like the default client port, these ports are assigned on each machine and not per InfoPrint Manager system. This means that a pdserver on two different machines can be listening on the same server port number just like they can be listening on the same client port number (6874). By default, ten ports are selected starting with the lowest block of ten available above 2000 in /etc/services. Each InfoPrint Manager server is assigned a port from the available ports when it first starts. If possible, it reuses that port on subsequent runs.

The fstshow -o command can be used to view the current server ports for a machine running InfoPrint Manager servers. For example, fstshow -o might display: Results from -$ fstshow -o, which is explained in the text following this art.

The first column displays whether a server port is in use; the second column displays the port number; and the third column displays the process ID (PID) of the process using the port. Notice how port 2062 is assigned to info3, but it is not currently running. Also the NAME column displays the name of the InfoPrint Manager server.

To start more than ten InfoPrint Manager servers (including the notification daemon and any SAP callback daemons) on one machine, you must add more server ports. If you try to start a server when there are not enough server ports available, you receive 5010-760 There are no available ports error message. The server ports can be redefined (both the quantity and the starting number) by using pdinitports. All InfoPrint Manager servers on the machine must be shutdown to run pdinitports. See the RICOH InfoPrint Manager: Reference guide for more information about the pdinitports utility.

Each InfoPrint Manager server advertises its server port in the namespace when it starts. A pdserver discovers what server port to use to communicate with another object through the namespace.