Advanced printer configuration

Printer interface scripts

A ``printer interface script'' is a program that the print service uses to manage the printer each time it prints a file. The interface script initializes the printer, takes advantage of its particular capabilities, prints the file, and reports any errors.

NOTE: If you have an interface program that you have used with the print service of an older UNIX system, it should still work. Note, though, that several -o options have been "standardized" and will be passed to every interface program. These may interfere with similarly named options your interface program uses.

The printer interface scripts are associated with the printer model and are located in /etc/lp/model. For example, the printer interface script for a PostScript^® printer is called /etc/lp/model/PS. You can also create your own interface scripts or customize existing ones to suit your needs. See ``Creating printer interface scripts''.

Interface scripts:

initialize the printer port (the connection between the computer and the printer). The standard (/etc/lp/model/standard) interface script uses stty(1) to initialize the printer port.
initialize the physical printer (restore the printer to a normal state in case a previously printed file has left it in an unusual state), setting the character pitch, line pitch, page size, and character set requested by the user. The standard interface script uses lp.set(1M) to initialize the printer.
print banner page (or pages), if required.
print the requested files. The standard interface script calls the lp.cat(1M) printer filter to print the files.
report any errors to the print service. The standard interface script uses lp.tell(1M) to send descriptions of printer faults to the print service; the print service forwards that information as an alert to the print administrator.

The interface script does not open the printer port; the print service opens the printer port (or calls a dialup printer if that is how the printer is connected). The print service gives the printer port connection to the interface script as standard output and sets the printer to be the controlling terminal for the interface script. If the port experiences a hangup, a SIGHUP signal is sent to the interface script.

Many of the interface scripts provide special options that the user can specify with the -o option to lp(1). (Read the appropriate interface file for this information.)

The print service runs the interface script to send the print job to the printer:

/etc/lp/interfaces/printer id user title copies options file1 file2 ...

Arguments to the interface script are:

printer: The name of the interface script (the same as the printer name).
id: Request-ID returned by lp.
user: Login name of user who made the request.
title: Optional title specified by the user.
copies: Number of copies requested by the user.
options: List of blank-separated options, specified by the user (using lp -o) or by the print service (from default values specified by the administrator with lpadmin). See lp(1) for the list of options recognized by the standard interface.
file: Full pathname of a file to be printed.

When the interface script is invoked, standard input comes from /dev/null, standard output is directed to the printer port, and standard error output is directed to a file that will be displayed to the user who submitted the print request.

The print service passes additional printer configuration information to the interface script as shell variables:

TERM=printer-type: Specifies the printer type. The value is used as a key for getting printer capability information from the extended terminfo database.
FILTER='pipeline': Specifies the filter to use to send the request content to the printer; the filter is given control of the printer.
CHARSET=character-set: Specifies the character set to use when printing the content of a print request. The standard interface script extracts the control sequences needed to select the character set from the terminfo database.

Creating printer interface scripts

If you have a printer that is not supported by simply adding an entry to the terminfo database, or if your printing needs are not supported by the standard or other interface scripts provided in /etc/lp/model, you can create your own printer interface script.

To create a customized interface script:

Start with the standard interface script (or one of the other scripts in /etc/lp/model) and modify it, rather than starting from scratch. For example:

cd /etc/lp/model
cp standard okidatanew
Make sure that the custom interface script sets the proper stty modes (terminal characteristics such as baud rate or output options). Look for the section that begins with this line:
```
   ## Initialize the printer port
```
Modify the code in the standard interface script. It sets both the default modes and the adjusted modes given by the print service or the user with a line like:

stty mode options 0<&1
This command line takes the standard input for the stty command from the printer port. For example, this stty command line sets the baud rate to 1200bps and sets some of the option modes:

stty -parenb -parodd 1200 cs8 cread clocal ixon 0<&1
Set the hardware flow control printer port characteristic. The standard interface script does not set hardware flow control. This is set according to your computer hardware. The code for the standard interface script suggests where to set this and other printer port characteristics. Look for the section that begins with this line:
```
   # Here you may want to add other port initialization code.
```
Because different printers have different numbers of columns, make sure the header and trailer for your interface script correspond to your printer. The standard interface script prints a banner that fits on an 80-column page (except for the user's title, which may be longer). Look for the section in the code for the standard interface script that begins with this line:
```
   ## Print the banner page
```
Some applications, when run with certain printers, may require that you turn off page breaking. If you must turn off page breaking, you can modify the standard interface program (/usr/lib/lp/model/standard) at this line:
```
   if [ -n "${FF}" -a "no" = "${nofilebreak}" ]
```
Change the no to yes to shut off page breaking.
Specify that the custom interface script print all user-related error messages to the standard output or to the standard error. The print service prints standard output errors on the page and mails standard error to the user.
Specify that when printing is complete, the interface script exits with a code that tells the status of the print job. ``Exit codes'', describes how the print service interprets exit codes.
One way of alerting the administrator to a printer fault is to exit with a code of 129. Unfortunately, if the interface script exits, the print service reprints the print job from the beginning once the fault is cleared. To get an alert to the administrator without reprinting the entire job, specify that the interface script send a fault message to the print service, but wait for the fault to clear. When the fault clears, the interface script resumes printing the job. When finished printing, the interface script can exit with zero as if the fault never occurred. An added advantage is that the interface script can detect when the fault is cleared automatically so that the administrator does not have to reenable the printer.
To specify that fault messages be sent to the print service, use lp.tell(1M). The standard printer interface code calls lp.tell(1M) with the LPTELL shell variable. The lp.tell program sends its standard input to the print service. The print service forwards the message as an alert to the administrator. If its standard input is empty, lp.tell does not initiate an alert. Examine the code immediately following these comments in the standard interface script for an example of how to use the lp.tell (LPTELL) program:
```
   # Here's where we set up the $LPTELL program to capture
   # fault messages.
   #
   # Here's where we print the file.
```
With the special exit code 129 or lp.tell, there is no longer the need for the interface script to disable the printer itself. Your interface script can disable the printer directly, but doing so overrides the fault-alerting mechanism. Alerts are sent only if the print service detects that the printer has faulted and the special exit code and lp.tell program are its main detection tools.
If the print service has to interrupt the printing of a file at any time, it kills the interface script with a signal 15 (see signal(2) and kill(1) for more information).
If the interface script dies from receipt of any other signal, the print service assumes that future print jobs are not affected and continues to use the printer. The print service notifies the person who submitted the print job that the job did not finish successfully.
The signals SIGHUP, SIGINT, SIGQUI, and SIGPIP (trap numbers 1, 2, 3, and 13) start out being ignored when the interface is invoked. The standard interface script changes this to trap these signals at appropriate times, interprets these signals to mean that the printer has a problem, and issues a fault.

Exit codes

Code Meaning to the print service

0 The print job completed successfully. If a printer fault occurred, it was cleared.

1 to 127 The print service encountered a problem in printing the job (for example, there were too many nonprintable characters or the job exceeded the printer's capabilities). This problem does not affect future print jobs. The print service should notify the person who submitted the print job - via write(1) or mail(1) - that an error occurred in printing the job. If a printer fault occurred, it was cleared.

128 Reserved for internal use by the print service. Interface scripts must not exit with this code.

129 The print service encountered a printer fault in printing the job. This problem affects future print jobs. If the fault recovery for the printer directs the print service to wait for the administrator to fix the problem, the print service should disable the printer. If the fault recovery is to continue printing, the print service should not disable the printer, but try printing again in a few minutes.

> 129 Reserved for internal use by the print service. Interface scripts must not exit with codes in this range.

Code	Meaning to the print service
0	The print job completed successfully. If a printer fault occurred, it was cleared.
1 to 127	The print service encountered a problem in printing the job (for example, there were too many nonprintable characters or the job exceeded the printer's capabilities). This problem does not affect future print jobs. The print service should notify the person who submitted the print job - via write(1) or mail(1) - that an error occurred in printing the job. If a printer fault occurred, it was cleared.
128	Reserved for internal use by the print service. Interface scripts must not exit with this code.
129	The print service encountered a printer fault in printing the job. This problem affects future print jobs. If the fault recovery for the printer directs the print service to wait for the administrator to fix the problem, the print service should disable the printer. If the fault recovery is to continue printing, the print service should not disable the printer, but try printing again in a few minutes.
> 129	Reserved for internal use by the print service. Interface scripts must not exit with codes in this range.

Setting up printer interface scripts

By default, the print service uses the standard interface script, /etc/lp/model/standard. This interface script should handle most of your printing needs.

To change the interface script after you add the printer,

NOTE: You cannot change the interface script from the Printer Setup Manager.

You can specify an interface program using the -i option of lpadmin(1M).

The following example adds a new printer called laser on printer port /dev/term/tty01. It uses a customized interface program, located in the directory /usr/doceng/laser_intface. It can handle three file types--i10, i300, and impress--and it may be used only by the users doceng and docpub. (The following command line is split into multiple lines for readability.)

lpadmin -p laser -v /dev/term/tty01 \
-i /usr/doceng/laser_intface \
-I "i10,i300,impress" \
-u "allow:doceng,docpub"