Microplex M204, Installation And Configuration Manual

Page: 42 / 204

34 CONFIGURING THE M204 FOR TCP/IP: Host Configuration
translate data to printer format
) | communication program
where communication program is the command executing rsh/rcmd/remsh or
npwrite so the print job is redirected over the network to the M204.
(
FILE=$6
#the spool file is found in the sixth parameter on System V
cat $FILE | onlcr
#filter the job
) | rcmd spike lp -d d3com1
where spike is the name of the M204 and the print jobs are being sent to its destina-
tion d3com1 by remotely executing the print server’s lp print command.
Please see npwrite on page 30, rsh/rcmd/remsh on page 31, and lp on page 89 for
more details on each command’s syntax.
Even if you have a very simplistic script, it’s important that you enclose your script
with brackets and then add in a communication program at the end.
Using npd and Your Own Script
If npd is the print method you would like to use with your interface script, you need to
start the npd daemon on your host and then incorporate it into your print setup. Please
see npd Pseudo-device Interface on page 42 to find out more about npd and how to
get it started.
Once you have this daemon running, you can go ahead and work it into your printer
configuration. For BSD systems, this requires an lp= field in your printcap entry along
with the standard if= field for the name of your interface script. The lp= field is filled
in with the name of the npd devicefile used in npd’s startup command. If you have a
System V setup, the -v option in the lpadmin command will equal the npd devicefile.
Example
Note