1    Preparing for the Installation

Before starting the installation procedures in Chapter 2, review the release notes available on the CD-ROM and the installation requirements outlined in this chapter.

1.1    Release Notes

Release notes for the Advanced Printing Software product are included with the documentation kit that accompanies the software. Hewlett-Packard Company strongly recommends that you read the release notes before using this product. The release notes identify known problems and restrictions in this release, and provide information on errors in the documentation.

1.2    Installation Overview

There are two methods of installing Advanced Printing Software and its reference pages:

If you expect to install the software from a RIS server, you need to know the name of the server and who maintains the RIS areas on the server. Before you begin a RIS installation, confirm the following:

See the Guide to Sharing Software on a Local Area Network for more information about setting up a RIS server, adding clients, and providing software kits for remote installation.

1.3    Installation Requirements

Allow approximately 10 minutes to complete this installation procedure. Network activity during a remote installation can increase the installation procedure time. The following sections describe requirements for installing Advanced Printing Software.

1.3.1    Hardware Requirements

To perform the installation you need the following hardware:

1.3.2    System Memory Requirements

Advanced Printing Software can be run on any Alpha-based system that meets the following memory requirements:

1.3.3    Back Up Your System Disk

Always back up your system before installing any software. Use the backup procedures established at your site. For details on performing a system backup, refer to your Tru64 UNIX documentation.

1.3.4    Login Privilege

You must be able to log in as the root user on the system where you are installing the Advanced Printing Software.

1.3.5    Software Requirements

The Advanced Printing Software is supported on any Alpha-based processor running Tru64 UNIX Version 5.1B or higher.

In most cases you can view the /etc/motd file to determine what version of the operating system you are running. If this file has been edited and does not contain the operating system version, you can verify the version you are running by executing the following command:

# /usr/sbin/sizer -v 

If you have previously installed Advanced Printing Software Version 1.0, Version 1.01, or Version 1.1, you must begin the installation by deinstalling the older version. The deinstallation process preserves your configuration. When you install Version 1.2, your configuration (servers, printers, and so on) will be in a usable state.

1.3.6    Advanced Printing Software Subsets

The Advanced Printing Software is packaged in the following subsets:

1.3.7    Disk Space Requirements

The following table lists the disk space requirements for loading and running the software subsets on a Tru64 UNIX system.

Subset / (root) /usr
APXBASE120 0K 3.75 MB
APXSVR120 0K 1.2 MB
APXGW120 0K .5 MB
APXGUI120 0K 6.8 MB
APXADMIN120 0K 2.1 MB
     

Refer to the disk space requirements table and total the values for each directory, then compare the space required for subsets with the free space currently on the disks where the Advanced Printing Software files will reside.

To determine the current amount of free space for a directory path, log in to the system where you will be installing the Advanced Printing Software software and enter the df command as follows:

% df -k /usr

This command produces output similar to the following:

 
Filesystem    kbytes   used    avail   capacity  Mounted on
/dev/rz0g     396703   328807  28225      92%     /usr

In this case the output indicates that there are 28225 kilobytes of free space on the file /usr system.

1.4    Installing a GUI Subset from an Unowned X Window Display

If you install or deinstall the APXGUI subset from a terminal or window that is not owned by the X session owner, the installation process installs files correctly, but it cannot integrate the GUI tools into the CDE environment. This occurs, for example, if you use the su command to become the root user from a terminal window belonging to a nonroot user. The install (or uninstall) process displays the following messages:

Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
/usr/bin/X11/xprop:  unable to open display ':0.0'
usage:  /usr/bin/X11/xprop [-options ...] [[format [dformat]] atom]
 
where options include:
    -grammar                       print out full grammar for command line
    -display host:dpy              the X server to contact
    -id id                         resource id of window to examine
    -name name                     name of window to examine
    -font name                     name of font to examine
    -remove propname               name of property to remove
    -root                          examine the root window
    -len n                         display at most n bytes of any property
    -notype                        do not display the type field
    -fs filename                   where to look for formats for properties
    -frame                         don't ignore window manager frames
    -f propname format [dformat]   formats to use for property of given name
    -spy                           examine window properties forever
This procedure was not able to refresh your current
X session.  In order for the Advanced Printing Software
GUIs to run properly, please do one of the following:
 
    1.  Log out and back in again to CDE
    2.  Using the Application Manager, issue the
        ReloadApps command
    3.  From a terminal window, while logged in as
        the user who owns the current CDE session
        (not su-ed to another user), issue the command
           /usr/dt/bin/dtaction ReloadApps
 
 

Follow one of the steps listed in the message to complete the integration of the Advanced Printing GUI tools into your CDE environment. To avoid this situation, log in to a CDE environment as the root user before installing the APXGUI subset.

1.5    Stopping the Installation

You can stop the installation at any time by pressing Ctrl/C. However, files installed up to that point are not deleted. You must delete each Advanced Printing Software file manually. Appendix B lists the files that are installed during the Advanced Printing Software installation procedure.

1.6    Deleting Subsets

After installing the Advanced Printing Software, you can delete subsets by using the setld command with the -d option. For example, to delete the APXGUI110 subset use the following command:

# setld -d APXGUI110

If you stop this procedure before it is completed, you will have to manually delete all of the files that have been installed. Appendix B lists the files that are installed during the Advanced Printing Software installation procedure.

1.6.1    Removing Spool Directories

When you remove the Advanced Printing Software from your system (by using setld -d), the directory /var/spool/pd and any files and subdirectories contained within it are not deleted.

The spool directories are left in place to prevent the loss of any job data that had not yet been printed at the time the kit was removed. This is particularly necessary during an upgrade, where the system administrator must remove the current kit, then install a new kit.

If, however, the print system is being removed from the system permanently (for example, printing is being transferred to a different host), then these directories are no longer needed. The system administrator should ensure that no important print job data remains in the directories, at which time the /var/spool/pd directories can be safely removed.

1.7    Upgrading Advanced Printing Software

Upgrading from a previous release of Advanced Printing Software requires that you shut down its services, remove the old version, install the new version, and restart it. A rolling upgrade of Advanced Printing Software is not supported. You can run only one version of Advanced Printing Software on a host or TruCluster at a time. However, the lpd printing software continues to function, uninterrupted, while you upgrade the Advanced Printing Software.

To minimize print services down time, ensure that you have the new software distribution mounted and ready to load.

1.7.1    Upgrading on a TruCluster System

To upgrade on a TruCluster System:

  1. Shutdown the Advanced Printing application resources controlled by the CAA (Cluster Application Availability) subsystem. These may include the apx-default resource as well as other resources you have created.

    1. List the CAA application resources:

      # caa_stat -t
      Name          Type         Target    State     Host
      ---------------------------------------------------------------
      apx-default   application  ONLINE    ONLINE    daffy
      apx_d1        application  ONLINE    ONLINE    bugs
      apx_d2        application  ONLINE    ONLINE    droopy
      apd_d3        application  ONLINE    ONLINE    bugs
      cluster_lockd application  ONLINE    ONLINE    bugs
      dhcp          application  OFFLINE   OFFLINE  
      named         application  OFFLINE   OFFLINE
      

    2. Stop the resources associated with the Advanced Printing Software by stopping the printing services they provide:

      # caa_stop apx-default apx_d1 apx_d2 apx_d3
      Attempting to stop 'apx-default on member 'daffy'
      Stop of 'apx-default' on member 'daffy' succeeded.
      Attempting to stop 'apx_d1' on member 'bugs'
      Stop of 'apx_d1' on member 'bugs' succeeded.
      Attempting to stop 'apx_d2' on member 'droopy'
      Stop of 'apx_d2' on member 'droopy' succedded.'
      Attempting to stop 'apx_d3' on member 'bugs'
      Stop of 'apx_d3' on member 'bugs' succeeded.
      

      Use the caa_stop command with the -f option to force a resource to the OFFLINE state if the caa_stop command was not successful.

    3. Run the /sbin/init.d/apx stop command on each cluster member to stop remaining daemons:

      On member 0:

      # /sbin/init.d/apx stop
      Stopping Advanced Printing Software Inbound Gateway daemon 603983
      Stopping Advanced Printing Software Notification Server daemon 642760
      Advanced Printing Software Protoserver daemon not running
      

      On member 1:

      # /sbin/init.d/apx stop
      Stopping Advanced Printing Software Inbound Gateway daemon 1675930
      Advanced Printing Software Protoserver daemon not running
      

      Repeat for any remaining cluster members.

  2. Delete the old software subsets:

    1. List the installed Advanced Printing Software subsets:

      # setld -i | grep ^APX | grep installed | grep -v 'not installed'
      APXADMIN110 installed Advanced Pritning Software Administrator Utilities
      APXBASE110  installed Advanced Printing Software BASE and Client Commands
      APXGUI110   installed Advanced Printing Software Graphical User Interface
      APXGW110    installed Advanced Printing Software lpr/lpd Gateway
      APXSVR110   installed Advanced Printing Software Spooler and Supervisor
      

    2. Delete the old subsets:

      # setld -d APXADMIN110 APXBASE110 APXGUI110 APXGW110 APXSVR110
      

      The deinstallation process automatically saves your print system database in /var/opt/APXsavedata.tar. The database is automatically restored when you install the new software version.

  3. Install the new subsets. You can perform this step on any of your cluster hosts. Refer to Chapter 2 for information on installing subsets. Choose the subsets appropriate for the host mahcine and your environment.

  4. Restart the printing daemons on each cluster member:

    On member 0:

    # /sbin/init.d/apx start
    Starting Advanced Printing Software Inbound Gateway daemon
    

    On member 1:

    # /sbin/init.d/apx start
    Starting Advanced Printing Software Inbound Gateway daemon
    

    Continue until all of the printing daemons are running.

  5. Restart CAA resources:

    # caa_start apx-default on member 'daffy'
    Attempting to start 'apx-default' on member 'daffy'
    Start of 'apx-default' on member 'daffy' succeeded.
    # caa_start apx_d1 on member 'droopy'
    Attempting to start 'apx_d1' on member 'droopy'
    Start of 'apx_d1' on member 'droopy' succeeded.
    # caa_start apx_d2 on member 'bugs'
    Attempting to start 'apx_d2' on member 'bugs'
    Start of 'apx_d2' on member 'bugs' succeeded.
    

    Continue until each application resource associated with Advanced Printing Software is running. When all of the resources have been started, printing services will be available in your environment.