![](/images/new-backgrounds/1105423/105423103x1.webp)
CHAPTER 7: UNIX/RTEL Host Setup
queue_name | server | service | passwdoptions | |
rprint1 | eps1 | prt_srvc | null | banner |
/dev/ttyq1 | eps2 | mod_srvc | null | |
/dev/ttyq6 | eps2 | :4 | null | |
|
|
|
|
|
The second line will request a connection to EPS “eps2” and service “mod_srvc”, using
% rteld
in this case would be the same as
%rteld
%rteld
You can use the 3 different configuration lines (for both printer and device setups) in the same server_hosts file. You do not need any special handling or ordering.
Once the EPS starts the rteld process, you should be able to use the pseudo- device as any other physical device on the host. The EPS can echo files to it, dump applications programs output to it, etc.
Two other rteld options provide information and a means of removing the rteld process for a particular tty pair. The
7.9 Queueing with the RTEL Software
You can queue a job in two places— in the host’s print system (lp or lpr, etc) or in the EPS itself. If you are only printing to one queue from one host to one EPS service, the host provides the queueing, since it will not release a new job to the EPS until the previous job completes. The second case occurs when multiple print queues (possibly on more than one host) point to the same EPS queue. In this case, the hosts will provide local queueing, but you may still have multiple jobs attempting to access the EPS. In this case, the EPS will provide queueing among the hosts. Jobs from multiple hosts are handled in order, without regard to size or any priority, so if a particular host’s queue seems to stop for an extended time, this may be an explanation. The SHOW QUEUE display on the EPS will show the order of jobs pending on the EPS— you must use the host’s lp or lpr utilities to show jobs queued by the host.
51