Scheduling Network Print Requests

Each print client communicates directly with a print sever over the network. The communication is done between the requesting command (lp, lpstat, cancel, lpr, lpq, or lprm) and the print service on the print server. Doing so, reduces the print system overhead on client only systems, improving scalability, performance and accuracy of data.

Print servers listen for print request with the Internet services daemon (inetd). Upon hearing a request for print service from the network, the inetd daemon starts a program called the “protocol adaptor” (in.lpd). The protocol adaptor translates the print request and communicates it to the print spooler, returning the results to the requester. It starts on demand and exits when it has serviced the network request. This eliminates idle system overhead for printing. It also eliminates any additional system configuration for network printing support as was the case in previous versions of Solaris printing.