System Administration Guide

The Structure of the LP Print Service

This section describes the directory structure, files, logs, and commands of the LP print service.

Directories

The files of the LP print service are distributed among seven directories, as shown in Table 45-1.

Table 45-1 Directories for the LP Print Service


Directory	Contents
`/usr/bin`	The LP print service user commands
`/etc/lp`	A hierarchy of LP server configuration files
`/usr/share/lib`	The `terminfo` database directory
`/usr/sbin`	The LP print service administrative commands
`/usr/lib/lp`	The LP daemons; directories for binary files and PostScript filters; and the `model` directory (which contains the standard printer interface program)
`/var/lp/logs`	The logs for LP activities: `lpsched.n -` Messages from `lpsched` and `requests.n` - Information about completed print requests
`/var/spool/lp`	The spooling directory where files are queued for printing

Configuration Files

The scheduler stores configuration information in LP configuration files located in the /etc/lp directory, as described in Table 45-2.

Caution -

The configuration files listed in Table 45-2 are private interfaces, and are subject to change in future releases. You should not build software that relies on these files being in their current locations or that relies on the data being in the format currently used.

Table 45-2 Contents of the /etc/lp Directory


File	Type	Description
`classes`	Directory	Files identifying classes provided by the `lpadmin -c` command.
`fd`	Directory	Description of existing filters.
`filter.table`	File	Print filter lookup table.
`forms`	Directory	Location to put files for each form. Initially, this directory is empty.
`interfaces`	Directory	Printer interface program files.
`logs`	Link to `/var/lp/logs`	Log files of printing activities.
`model`	Link to `/usr/lib/lp/model`	The standard printer interface program.
`printers`	Directory	Directories for each local printer. Each directory contains configuration information and alert files for an individual printer.
`pwheels`	Directory	Print wheel or cartridge files.

These configuration files serve a similar function to the /etc/printcap file in SunOS 4.x.

Note -

You can check the contents of the configuration files, but you should not edit them directly. Instead, use the lpadmin(1M) command to make configuration changes. Your changes will be written to the configuration files in the /etc/lp directory. The lpsched daemon administers and updates the configuration files.

The /etc/lp/printers directory has a subdirectory for each local printer known to the system. The following example shows the /etc/lp/printers subdirectories of printers sparc1 and luna.

$ ls -l /etc/lp/printers
drwxrwxr-x 2 lp lp 512 Jan 23 23:53 luna
drwxrwxr-x 2 lp lp 512 Jan 11 17:50 sparc1

Within each of the printer-specific directories, the following files can describe the printer:

alert.sh - Shell to execute in response to alerts
alert.vars - Alert variables
configuration - Configuration file
users.deny - List of users to whom printer access is denied
comment - Printer description

The configuration file for the printer luna, /etc/lp/printers/luna/configuration, would typically appear as follows:

Banner: on: Always
Content types: PS
Device: /dev/term/b
Interface: /usr/lib/lp/model/standard
Printer type: PS
Modules: default

The `terminfo` Database

The /usr/share/lib directory contains the terminfo database directory, which contains definitions for many types of terminals and printers. The LP print service uses information in the terminfo database to initialize a printer, to establish a selected page size, character pitch, line pitch, and character set, as well as to communicate the sequence of codes to a printer.

Each printer is identified in the terminfo database with a short name. See "Printer Type" for a description of the structure of the terminfo database. If necessary, you can add entries to the terminfo database, but it is a tedious and time-consuming process. See "Adding a terminfo Entry for an Unsupported Printer".

Daemons and LP Internal Files

The /usr/lib/lp directory contains daemons and files used by the LP print service, as described in Table 45-3.

Table 45-3 Contents of the /usr/lib/lp Directory


File	Type	Description
`bin`	Directory	Contains files for generating printing alerts, slow filters, and queue management programs.
`lpsched`	Daemon	Manages scheduling of LP print requests.
`model`	Directory	Contains the standard printer interface program.
`postscript`	Directory	Contains all PostScript filter programs provided by the SunOS 5.x LP print service. These filters come with descriptor files in the `/etc/lp/fd` directory that tell the LP print service the characteristics of the filters and where to locate them.

Log Files

The LP print service maintains two sets of log files:

/var/spool/lp -- A list of current requests that are in the print queue
/var/lp/logs/requests -- An ongoing history of print requests

Print Queue Logs

The scheduler for each system keeps a log of print requests in the directories /var/spool/lp/tmp/system and /var/spool/lp/requests/system. Each print request has two files (one in each directory) that contain information about the request. The information in the /var/spool/lp/requests/system directory can be accessed only by root or lp. The information in the /var/spool/lp/tmp/system can be accessed only by the user who submitted the request, root, or lp.

The following example shows the contents of the /var/spool/lp/tmp/terra directory:

$ ls /var/spool/lp/tmp/terra
20-0 21-0
terra$ cat 21-0
C 1
D slw2
F /etc/default/login
P 20
t simple
U tamiro
s 0x1000

These files remain in their directories only as long as the print request is in the queue. Once the request is finished, the information in the files is combined and appended to the file /var/lp/logs/requests, which is described in the next section.

Use the information in the /var/spool/lp logs if you need to track the status of a print request that is currently in the queue.

History Logs

The LP print service records a history of printing services in two log files: lpsched and requests. These log files are located in the /var/lp/logs directory. You can use the information in these logs to diagnose and troubleshoot printing problems. This is an example of the contents of the /var/lp/logs directory:

# cd /var/lp/logs
# ls
lpsched.1    requests    requests.2
lpsched     lpsched.2    requests.1
#

The files with the .1 and .2 suffixes are copies of the previous day's logs. Each day, the lp cron job cleans out the lpsched and requests log files and keeps copies for two days. See "Creating and Editing crontab Files" in Chapter 59, Scheduling System Events (Tasks) , for suggestions on modifying the cron job for cleaning out the requests log.

The two most important log files for troubleshooting is the lpsched log, which contains information about local printing requests

The requests log contains information about print requests that are completed and no longer in the print queue. Once a request is finished printing, the information in the /var/spool/lp log files is combined and appended to the /var/lp/logs/requests log.

The requests log has a simple structure, so that you can extract data using common UNIX shell commands. Requests are listed in the order they are printed, and are separated by lines showing their request IDs. Each line below the separator line is marked with a single letter that identifies the kind of information contained in that line. Each letter is separated from the data by a single space.

The following example shows the contents of a requests log:

# pwd
/var/lp/logs
# tail requests.2
= slw2-20, uid 200, gid 200, size 5123, Tue Jun 17 10:16:10 MDT
1997
z slw2
C 1
D slw2
F /etc/motd
P 20
t simple
U irving
s 0x0100
#

Table 45-4 shows the letter codes and the content of their corresponding lines in the LP requests log.

Table 45-4 Letter Codes in the LP requests Log


Letter	Content of Line
`=`	The separator line. It contains the following items: request ID, user ID (UID), and group IDs (GIDs) of the user, the total number of bytes in the original (unfiltered) file size, and the time when the request was queued.
`C`	The number of copies printed.
`D`	The printer or class destination or the word `any`.
`F`	The name of the file printed. The line is repeated for each file printed; files were printed in the order shown.
`f`	The name of the form used.
`H`	One of three types of special handling: resume, hold, and immediate.
`N`	The type of alert used when the print request was successfully completed. The type is the letter `M` if the user was notified by email or `W` if the user was notified by a message to the terminal.
`O`	The printer-dependent `-o` options (for example, nobanner).
`P`	The priority of the print request.
`p`	The list of pages printed.
`r`	A single-letter line that is included if the user asked for "raw" processing of the files (the `-r` option of the `lp` command).
`S`	The character set, print wheel, or cartridge used.
`s`	The outcome of the request, shown as a combination of individual bits expressed in hexadecimal form. Several bits are used internally by the print service. The bits and what they mean are describe in Table 45-5.
`T`	The title placed on the banner page.
`t`	The type of content found in the files.
`U`	The name of the user who submitted the print request.
`x`	The slow filter used for the print request.
`Y`	The list of special modes for the print filters used to print the request.
`z`	The printer used for the request. This printer differs from the destination (the `D` line) if the request was queued for any printer or a class of printers, or if the request was moved to another destination.

Table 45-5 shows the outcome codes in the LP requests log and their descriptions.

Table 45-5 Outcome Codes in the LP requests Log


Outcome Code	Description
`0x0001`	The request was held pending resume.
`0x0002`	Slow filtering is running.
`0x0004`	Slow filtering finished successfully.
`0x0008`	The request is on the printer.
`0x0010`	Printing finished successfully.
`0x0020`	The request was held pending user change.
`0x0040`	The request was canceled.
`0x0080`	The request will print next.
`0x0100`	The request failed filtering or printing.
`0x0200`	The request is in transit to a remote printer. (obsolete)
`0x0400`	The user will be notified.
`0x0800`	A notification is running.
`0x1000`	A remote system has accepted the request. (obsolete)
`0x2000`	The administrator placed a hold on the request.
`0x4000`	The printer had to change filters.
`0x8000`	The request is temporarily stopped.

Spooling Directories

Files queued for printing are stored in the /var/spool/lp directory until they are printed, which may be only seconds. Table 45-6 shows the contents of the /var/spool/lp directory.

Table 45-6 Contents of the /var/spool/lp Directory


File	Type	Description
`SCHEDLOCK`	File	Lock file for the scheduler. Check for this file if the scheduler dies and will not restart.
`admins`	Directory	Link to `/etc/lp.`
`bin`	Directory	Link to `/usr/lib/lp/bin.`
`logs`	Link	Link to `../lp/logs` where completed print requests are logged.
`model`	Link	Link to `/usr/lib/lp/model.`
`requests`	Directory	Directory that contains subdirectories for each configured printer where print requests are logged until printed. Users cannot access this log.
`system`	Directory	A print status file for the system.
`temp`	Link	Link to `/var/spool/lp/tmp/hostname`, which contains the spooled requests.
`tmp`	Directory	Directory for each configured printer where print requests are logged until printed. Changes to existing print requests are also recorded in this log.