Skip Navigation Links | |
Exit Print View | |
System Administration Guide: Printing Oracle Solaris 11 Express 11/10 |
1. Introduction to Printing in the Oracle Solaris Operating System
2. Planning for Printing (Tasks)
3. Setting Up and Administering Printers by Using CUPS (Tasks)
4. Setting Up and Administering Printers by Using Print Manager for LP (Tasks)
5. Setting Up and Administering Printers by Using Oracle Solaris Print Manager (Tasks)
6. Setting Up Printers by Using LP Print Commands (Tasks)
7. Administering Printers by Using LP Print Commands (Tasks)
Administers Printers Using LP Print Commands (Task Map)
Setting Printer Definitions by Using LP Print Commands
How to Add a Printer Description by Using LP Print Commands
Setting Up a Default Printer Destination by Using LP Print Commands
How to Set a System's Default Printer Destination by Using LP Print Commands
Printing Banner Pages by Using LP Print Commands
How to Make Banner Pages Optional by Using LP Print Commands
How to Turn Off Banner Pages by Using LP Print Commands
Setting Up Printer Classes by Using LP Print Commands
How to Define a Class of Printers by Using LP Print Commands
Setting Up Printer Fault Alerts by Using LP Print Commands
How to Set Fault Alerts for a Printer by Using LP Print Commands
Setting Up Printer Fault Recovery by Using LP Print Commands
How to Set Printer Fault Recovery by Using LP Print Commands
Limiting User Access to a Printer by Using LP Print Commands
How to Limit User Access to a Printer by Using LP Print Commands
Administering Printers That Are Associated With PPD Files (Task Map)
Administering Printers That are Associated With PPD Files
How to Set Default Values for Print Queues That Are Associated With PPD Files
Determining Whether a PPD File Is Associated With a Print Queue
8. Customizing LP Printing Services and Printers (Tasks)
9. Administering the LP Print Scheduler and Managing Print Requests (Tasks)
10. Administering Printers on a Network (Tasks)
11. Administering Character Sets, Filters, Forms, and Fonts (Tasks)
12. Administering Printers by Using the PPD File Management Utility (Tasks)
13. Printing in the Oracle Solaris Operating System (Reference)
14. Troubleshooting Printing Problems in the Oracle Solaris OS (Tasks)
Table 7-1 Printer Administration by Using LP Print Commands (Task Map)
|
Setting definitions for the printers on your network is an ongoing task that lets you provide a more effective print environment for users. For example, you can assign printer descriptions for all your site's printers to help users find where a printer is located. Or, you can define a class of printers to provide the fastest turnaround for print requests. See Specifying a PPD File When Setting Up a Printer for more information about setting printer definitions by using LP print commands.
Many printer definitions can be set or reset by using Oracle Solaris Print Manager. For more information, see Setting Printer Definitions by Using Oracle Solaris Print Manager.
The following procedures provide step-by-step instructions on setting or resetting printer definitions by using LP Print Commands. These procedures show how to quickly set or reset printer definitions.
$ su root
# lpadmin -p printer-name -D "comment"
Specifies the name of the printer for which you are adding a description.
Specifies the characteristics of the printer, such as the location or administrative contact. Enclose characters that the shell might interpret, such as *, ?, \, !, ^, in single quotation marks.
For more information, see the lpadmin(1M) man page.
# lpstat -p printer-name -l
Example 7-1 Adding a Printer Description
The following example shows how to add a printer description for the printer luna.
$ su root
# lpadmin -p luna -D "Nathans office"
You can specify a default printer destination for a user so that the user does not need to type the printer name when using the print commands. Before you can designate a printer as the default, the printer must be known to the print service on the system.
Set a user's default printer destination by setting any of the following:
LPDEST environment variable
PRINTER environment variable
The _default variable in the user's .PRINTERS file
The system's default printer by using the lpadmin -d command or Oracle Solaris Print Manager
When an application provides a printer destination, that destination is used by the print service, regardless of whether you have set a system's default printer destination. If an application doesn't provide a printer destination or if you do not provide a printer name when using a print command, the print command searches for the default printer in a specific order. The following table shows the search order for a system's default printer destination.
Table 7-2 Search Order for Default Printer Destinations
|
# lpadmin -d [printer-name]
-d printer-name specifies the name of the printer you are assigning as the system's default printer. If you don't specify printer-name, the system is set up with no default printer.
# lpstat -d
Example 7-2 Setting a System's Default Printer Destination
The following example shows how to set the printer luna as the system's default printer. The printer luna is used as the system's default printer if the LPDEST or the PRINTER environment variables are not set.
# lpadmin -d luna # lpstat -d system default destination: luna
A banner page identifies who submitted the print request, the print request ID, and when the request was printed. A banner page also has a modifiable title to help users identify their printouts.
Banner pages make it easy to identify the owner of a print job, which is especially helpful when many users submit jobs to the same printer. However, printing banner pages uses more paper and might be unnecessary if a printer has only a few users. In some cases, printing banner pages is undesirable. For example, if a printer has special paper or forms mounted, such as paycheck forms, printing banner pages might cause problems.
By default, the print service forces banner pages to be printed. However, you can give users a choice to turn off printing of a banner page when they submit a print request. You can set this choice through the lpadmin command or through Oracle Solaris Print Manager. If you give the users a choice, they have to use the -o banner option to turn off banner page printing.
Also, if you don't need or want banner pages, you can turn off banner pages so that they are never printed. You can turn off banner page printing by using the lpadmin command or through Oracle Solaris Print Manager.
The following table describes command options that are used to manage banner page printing.
Table 7-3 Banner Page Printing
|
$ su root
# lpadmin -p printer-name -o banner=optional
Specifies the name of the printer for which you are making banner pages optional.
Enables users to specify no banner page when they submit a print request.
# lpstat -p printer-name -l
Example 7-3 Making Banner Pages Optional
The following example shows how to make the banner page optional on the printer luna.
# lpadmin -p luna -o banner=optional
$ su root
# lpadmin -p printer-name -o banner=never
Specifies the name of the printer for which you are turning off banner pages.
Disables banner page printing under all circumstances.
# lpstat -p printer-name -l
The command output contains the line Banner not printed.
Example 7-4 Turning Off Printing Banner Pages
The following example shows how to disable the printing of banner pages on the printer luna.
# lpadmin -p luna -o banner=never
The LP print service enables you to group several locally attached printers into one class. You can perform this task only by using the lpadmin -c command.
After you set up a printer class, users can then specify that class, rather than individual printers, as the destination for a print request. The first printer in the class that is available to print is used. The result is faster turnaround because printers are kept as busy as possible.
No default printer classes are known to the print service. Printer classes exist only if you define them.
Here are some ways you could define printer classes:
By printer type – For example, a PostScript printer.
By location – For example, a printer located on the 5th floor.
By work group or department – For example, the accounting department.
Alternatively, a class might contain several printers that are used in a particular order. The LP print service always checks for an available printer in the order in which printers were added to a class. Therefore, if you want a high-speed printer to be accessed first, add the high-speed printer to the class before you add a low-speed printer. As a result, the high-speed printer handles as many print requests as possible. The low-speed printer is reserved as a backup printer when the high-speed printer is in use.
Note - Print requests are balanced between printers in a class only for local printers.
Class names, similar to printer names, must be unique and can contain a maximum of 14 alphanumeric characters and underscores.
You are not obligated to define printer classes. You should add printer classes only if you determine that using them would benefit users on the network.
$ su root
# lpadmin -p printer-name -c printer-class
Specifies the name of the printer you are adding to a class of printers.
Specifies the name of a class of printers.
# lpstat -c printer-class
Example 7-5 Defining a Class of Printers
The following example shows how to add the printer luna in the printer class roughdrafts.
# lpadmin -p luna -c roughdrafts
If you choose, the LP print service can notify you when it detects a printer fault. With the lpadmin -A command or with Oracle Solaris Print Manager, you can select any of the following methods to receive printer fault notification:
A message to the terminal on which root is logged in
Electronic mail to root
No notification
However, the lpadmin -A command offers you an additional option of receiving a message specified by the program of your choice. The lpadmin -A command also enables you to selectively turn off notification for an error that you already know about.
Unless you specify a program to deliver fault notification, the content of the fault alert is a predefined message that states that the printer has stopped printing and needs to be fixed.
The following table lists the alert values that you can set for a printer with the lpadmin -A command. These alert values can also be set for print wheels, font cartridges, and forms.
Table 7-4 Values for Printer Fault Alerts
|
$ su root
# lpadmin -p printer-name -A alert [-W minutes]
Specifies the name of the printer for which you are specifying an alert for printer faults.
Specifies what kind of alert occurs when the printer faults. Some valid values are mail, write, and quiet.
Specifies how often, in minutes, the fault alert occurs. If you don't specify this option, the alert is sent one time.
# lpstat -p printer-name -l
Example 7-6 Setting Fault Alerts for a Printer
The following example shows how to set up the printer mars to send fault alerts by email to a user named joe. A reminder is sent every 5 minutes.
# lpadmin -p mars -A 'mail joe' -W 5
The following example shows how to set up the printer venus to send fault alerts to the console window. A reminder i sent every 10 minutes.
# lpadmin -p venus -A write -W 10
The following example shows how to stop fault alerts for the printer mercury.
# lpadmin -p mercury -A none
The following example shows how to stop fault alerts until the printer venus has been fixed.
# lpadmin -p venus -A quiet
If you choose not to send any fault notification, you can still find out about printer faults so that you can correct the problem. The LP print service will not continue to use a printer that has a fault. In addition to alerts for printer faults, you can also provide alerts that instruct you to mount print wheels, font cartridges, and forms when print requests require them.
You can define the fault recovery options for a printer only by using the lpadmin -F command. This task is not available in Oracle Solaris Print Manager.
Printer faults can be as simple as running out of paper or needing to replace a toner cartridge. More serious problems can include complete printer failure or power failure.
After you fix a printer fault, the print request that was active when the fault occurred begins printing in one of three ways:
Starts printing from the beginning
Continues printing from the top of the page where printing stopped
After you enable the printer, continues printing from the top of the page where the printing stopped
The LP print service requires a separate print filter to continue printing from the top of a page where the printing stopped. This print filter records the control sequences set by the default print filters. The printer uses these control sequences to track page boundaries. You will be notified by the LP print service if recovery cannot proceed with the specified print filter. For information about writing filters, see How to Create a New Print Filter.
If you want printing to resume immediately after a printer fault is fixed, enable the printer by using the enable command.
The following table lists the fault recovery values that you can set for a printer by using the lpadmin -F command.
Table 7-5 Values for Printer Fault Recovery
|
# lpadmin -p printer-name -F recovery-options
Specifies the name of the printer for which you are specifying fault recovery.
Specifies one of the three valid recovery options: beginning, continue, or wait.
For more information, see the lpadmin(1M) man page.
# lpstat -p printer-name -l
Example 7-7 Setting Printer Fault Recovery
The following example shows how to set up the printer luna to continue printing at the top of the page where printing stopped.
# lpadmin -p luna -F continue
You can control which users can access some printers or all of the available printers. For example, you can prevent some users from printing on a high-quality printer to minimize expense. To restrict user access to printers, you create allow and deny lists by using the lpadmin -u command on the print server. Oracle Solaris Print Manager enables you to create only allow lists. If you create neither list, a printer is available to all users who can access the printer.
An allow list contains the names of users who are allowed access to the specified printer. A deny list contains the names of users denied access to the specified printer.
The rules for allow and deny lists are explained in the following table:
|
Because the print server is responsible for controlling access to the printer, allow and deny lists can only be created on the print server. If you create allow and deny lists, the print server will exclusively control user access to printers.
The following table lists the values that you can add to an allow list or a deny list to limit user access to a printer.
Table 7-6 Values for Allow and Deny Lists
|
# lpadmin -p printer-name -u allow:user-list [deny:user-list]
Specifies the name of the printer to which the allow or deny access list applies.
Specifies the user names to be added to the allow access list. You can specify multiple user names with this command. Use a space or a comma to separate names. If you use spaces, enclose the list of names in quotation marks.
Specifies user names to be added to the deny user access list. You can specify multiple user names with this command. Use a space or a comma to separate names. If you use spaces, enclose the list of names in quotation marks.
The specified users are added to the allow or deny list for the printer in one of the following files on the print server:
Note - If you specify none as the value for user-list in the allow list, the following files are not created on the print server:
# lpstat -p printer-name -l
Example 7-8 Limiting User Access to a Printer
The following example shows how to allow only the users nathan and george access to the printer luna.
# lpadmin -p luna -u allow:nathan,george
The following example shows how to deny the users nathan and george access to the printer asteroid.
# lpadmin -p asteroid -u deny:"nathan george"