The following task map identifies the tasks associated with converting printer configuration information.
Task |
Description |
For Instructions |
---|---|---|
Convert Existing Printer Configuration Information |
Convert Printer Configuration Information for Systems Running the SunOS 5.5.1 Release – If your site uses the SunOS 5.5.1 release, you can convert the printer configuration information in the /etc/lp/printers directory to the /etc/printers.conf configuration file. This is usually a one-time task. |
How to Convert Printer Information For a System Running the Solaris 2.5.1 Release |
|
Convert Printer Configuration Information for a System Running an lpd-based Print Server – If your site uses lpd-based software, you convert the printer configuration information in the /etc/printcap file to the /etc/printers.conf configuration file. This is usually a one-time task. |
How to Convert Printer Information For a System Running an lpd-based Print Server |
Existing printer configuration information is automatically converted when installing or upgrading to the Solaris 9 release. This section explains how to convert the printer configuration information for a system running SunOS 5.5.1 release or a system running a lpd-based printer server to the /etc/printers.conf printer configuration file. You'll use one of two print administration commands to automate the conversion task:
The conv_lp command enables you to convert information in the /etc/lp/printers directory on a SunOS 5.9 system to entries in the system's /etc/printers.conf file. For instructions, see How to Convert Printer Information For a System Running the Solaris 2.5.1 Release.
The conv_lpd command enables you to convert information in a /etc/printcap configuration file from a system running a lpd-based printer server to entries in a /etc/printers.conf file. For instructions, see How to Convert Printer Information For a System Running an lpd-based Print Server.
If you are not using a name service, you should create a master /etc/printers.conf file that includes the existing printers at your site. You can then copy the master file to all the print clients or by loading it into the NIS or NIS+ name service. This is a good way to initially enable all the new print clients access to the existing printers at your site.
If you are using the NIS or NIS+ name service to configure printer information, do not use a /etc/printers.conf file on your print clients. A print client uses the /etc/printers.conf file first to locate a printer; however, the /etc/printers.conf file might conflict with the printer information in the NIS or NIS+ maps and cause unexpected results. To avoid this problem, remove the /etc/printers.conf file on print clients when you want them to use NIS or NIS+ for printer information.
Log in as superuser on the system running the Solaris 9 release.
Convert the printer configuration information in the system's /etc/lp/printers directory to the /etc/printers.conf file.
# /usr/lib/print/conv_lp |
Copy the /etc/printcap file from a system running an lpd-based print server to a system running the Solaris 9 release.
Log in as superuser on the system running the Solaris 9 release where you copied the /etc/printcap file.
Convert the printer configuration information in the /etc/printcap file to the /etc/printers.conf file.
# /usr/lib/print/conv_lpd |