Patch-ID# 101655-07
Keywords: NeWSprinter20 queue hang EnergyStar spd automatic tray select Japanese core
Synopsis: NeWSprint 2.5B: NeWSprinter20 EnergyStar support & queue hang fixes.
Date: Dec/24/97
Solaris Release: 2.1, 2.2, 2.3, 2.4, 2.5, 2.5.1
SunOS Release: 5.1, 5.2, 5.3, 5.4, 5.5, 5.5.1
Unbundled Product: NeWSprint, Japanese NeWSprint
Unbundled Release: 2.5B, J2.5B
Relevant Architectures: sparc
NOTE: sun4c, sun4m, sun4d
BugId's fixed with this patch: 1109837 1124518 1139468 1147368 1149358 1149733 1154661 1160288 1174503 1182007 1206787 1211076 1266610 4026534
Changes incorporated in this version: 1174503 4026534
Patches accumulated and obsoleted by this patch:
Patches which conflict with this patch:
Patches required with this patch:
Obsoleted by:
Files included with this patch:
/opt/NeWSprint/printer_classes/NeWSprinter20/install/NeWSprinter20_param
/opt/NeWSprint/printer_classes/NeWSprinter20/bin/descrip_NeWSprinter20.ps
/opt/NeWSprint/printer_classes/NeWSprinter20/bin/engine_ctl_NeWSprinter20
/opt/NeWSprint/printer_classes/NeWSprinter20/C/include/separator.ps
/opt/NeWSprint/printer_classes/NeWSprinter20/C/ps/npcomm.T
/opt/NeWSprint/printer_classes/HP/admin/share/add_HP_config_work
/opt/NeWSprint/drivers/spd/spd
/opt/NeWSprint/np/nps/dev.ps
/opt/NeWSprint/printer_classes/NeWSprinter20/ja/include/separator.ps
/opt/NeWSprint/printer_classes/NeWSprinter20/install/ja/NeWSprinter20_param
Problem Description:
4026534 NeWSprint 2.5B xnews core dumps without any messages
1174503 cancelling jobs on 5.x causes device busy: waiting for auto-retry error
(from 101655-06)
1266610 spd driver is missing from patch 101655-05
1206787 core dump when default tray has nonletter size of paper.
(from 101655-05)
BADPATCH
(from 101655-04)
1211076 job printed to the auxiliary-feeder will disappear.
(from 101655-03)
1182007 NeWSprinter20 print the same page forever due to tray out in A4 paper size.
(from 101655-02)
1109837 NeWSprint should automatically select tray when papersize is requested.
1124518 spd driver hangs queue and the handler process is unkillable.
1139468 The NeWSprinter 20 handler hangs when using manual feed.
1147368 The page count does not work when printing with the NeWSprinter 20.
1149358 The NeWSprinter 20 causes a "panic: Data fault" after paper jam.x
1149733 The SPARCCenter 2000 data faults when adding the maximum number
of printers (30).
1154661 The add_np_printer program to install an HP printer on Solaris 2.3
is broken by a change to sed.
Features included in this patch are the EnergyStar reduced power
consumption feature for the NeWSprinter 20 and the auto tray select feature,
which enables structured jobs which specify media size (e.g. legal) to
automatically find the proper tray (tray filled with legal paper).
Please refer to the documentation below for details on how to use the auto
tray feature, and other useful information.
Known Problems:
1. ASCII text printed to ledger paper via manual feed to the NeWSprinter 20
will print rotated 90 degrees.
Patch Installation Instructions:
--------------------------------
Generic 'installpatch' and 'backoutpatch' scripts are provided
within each patch package with instructions appended to this section.
Other specific or unique installation instructions may also be
necessary and should be described below.
Special Install Instructions:
-----------------------------
After installing the patch, you will need to do the following:
1. Log in as superuser (root):
# su
Password:
2. Apply the patch by typing:
//installpatch /
where is the directory containing the patch and
is the patch number. must be a full path name.
3. Stop the print system until re-installation is complete:
# lpshut
4. Remove all NeWSprinter 20 printer installations by following the instructions
of the rm_np_printer program:
[NOTE: If you have customized any files in the printers' spool directories,
please save these changes at this time. You can re-add the changes after
step #5.]
# /opt/NeWSprint/bin/rm_np_printer
5. Install the NeWSprinter 20 printers by following the instructions of the
add_np_printer program:
# /opt/NeWSprint/bin/add_np_printer -t
Features for the NeWSprinter 20
-----------------------------------
Patch 101655 (for SunOS 5.x operating systems) contains two features
for the NeWSprinter 20. These are Energy Star compliance and an automatic
tray selection feature.
Energy Star Compliance:
A new entry in the .param file, FUSER_TIMEOUT, has been added to turn off
the NeWSprinter 20 fuser after the printer is idle for 60 minutes in order
to meet EPA Energy Star guidelines for energy efficiency. If you prefer to
keep the fuser on at all times, comment this variable out of the .param file.
Automatic Tray Selection:
A new variable has been added to the .param file for the NeWSprinter 20
called AUTOTRAYSELECT, which enables the printer to automatically select
the paper tray based on the size of paper specified by the print job.
AUTOTRAYSELECT is set to false by default. If you set AUTOTRAYSELECT to
true, and a structured PostScript job sent to the printer specifies a
particular page size, the automatic paper tray selection is enabled. A
page size is specified by a structured PostScript file when the name of
a page size (e.g. legal, letter, or a4) appears by itself on a line in
the file. This can be accomplished by editing the PostScript file or by
specifying the page size using PreLimn or NPtool.
Whenever the PostScript job specifies a page size, AUTOTRAYSELECT (if set
to true) overrides any paper supply selection specified by NPtool or
PreLimn commands. If the document has embedded a page size different from
that shown in NPtool, NPtool will override the embedded setting. AUTOTRAYSELECT
also overrides the DEFAULTBANNERTRAY and DEFAULTTRAY settings in the .param
file. The printer automatically selects an appropriate paper tray, and the
banner page is printed from the DEFAULTBANNERTRAY.
When there are multiple trays containing the desired paper size and the
first paper tray becomes empty, auto tray selection depends on the PRINTCONT
variable. If PRINTCONT is true, the job continues, drawing paper from an
alternate paper tray. If PRINTCONT is false, the printer stops and waits
for more of the appropriate size paper to be added to the first paper tray.
Instructions to install patch using "installpatch"
--------------------------------------------------
1. Become super-user.
2. Apply the patch by typing:
//installpatch /
where is the directory containing the patch and
is the patch number. must be a full path name.
Example:
# /tmp/123456-01/installpatch /tmp/123456-01
3. If any errors are reported, see "Patch Installation Errors" in
the Command Descriptions section below.
Rebooting the system or restarting the application after a successful
patch installation is usually necessary to utilize patch.
NOTE: On client server machines the patch package is NOT applied
to existing clients or to the client root template space.
Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED
THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH
METHOD ON THE CLIENT. See the next section for instructions
for installing a patch on a client.
Instructions for installing a patch on a diskless or dataless client
--------------------------------------------------------------------
1. Before applying the patch, the following command must be executed
on the server to give the client read-only, root access to the
exported /usr file system so that the client can execute the
pkgadd command:
share -F nfs -o ro,anon=0 /export/exec/Solaris_2.1_sparc.all/usr
The command:
share -F nfs -o ro,root= \
/export/exec/Solaris_2.1_sparc.all/usr
accomplishes the same goal, but only gives root access to the
client specified in the command.
2. Login to the client system and become super-user.
3. Continue with step 2 in the "Instructions to install patch using
installpatch" section above.
Instructions for backing out patch using "backoutpatch"
-------------------------------------------------------
1. Become super-user.
2. Change directory to /var/sadm/patch:
cd /var/sadm/patch
3. Backout patch by typing:
/backoutpatch
where is the patch number.
Example:
# 123456-01/backoutpatch 123456-01
4. If any errors are reported, see "Patch Backout Errors" in
the Command Descriptions section below.
Instructions for identifying patches installed on system:
----------------------------------------------------------
Type:
installpatch -p
This command produces a list of the patch IDs of the patches that
are currently applied to the system. When executed with the -p
option, the installpatch command does not modify the system in
any way.
Command Descriptions
--------------------
NAME
installpatch - apply patch package to Solaris 2.x system
backoutpatch - remove patch package from Solaris 2.x system
SYNOPSIS
installpatch [-u] [-d]
backoutpatch
DESCRIPTION
These installation and backout utilities apply only to
Solaris 2.x associated patches. They do not apply to Solaris
1.x associated patches. These utilities are currently only
provided with each patch package and are not included with
the standard Solaris 2.x release software.
OPTIONS
installpatch
-u unconditional install, do not verify file attributes
-d do not save original files being replaced
-p print a list of the patches currently applied on the system
DIAGNOSTICS
Patch Installation Errors:
--------------------------
Error message: Patch has already been applied.
Explanation and recommended action: This patch has already been
applied to the system. If the patch has to be reapplied
for some reason, backout the patch and then reapply it.
Error message: This patch is obsoleted by a patch which has
already been applied to this system. Application of this
patch would leave the system in an inconsistent state.
Patch installation is aborted.
Explanation and recommended action: Occasionally, a patch
is replaced by a new patch which incorporates the bug fixes
in the old patch and supplies additional fixes also. At
this time, the earlier patch is no longer made available
to users. The second patch is said to "obsolete" the
first patch. However, it is possible that some users
may still have the earlier patch and try to apply it to
a system on which the later patch is already applied.
If the obsoleted patch were allowed to be applied, the
additional fixes supplied by the later patch would no
longer be available, and the system would be left in an
inconsistent state. This error message indicates that
the user attempted to install an obsoleted patch. There
is no need to apply this patch because the later patch
has already supplied the fix.
Error message: The packages to be patched are not installed on
this system.
Explanation and recommended action: None of the packages
to be updated by this patch are installed on the system.
Therefore, this patch cannot be applied to the system.
Error message: This patch is not applicable to client systems.
Explanation and recommended action: The patch is only
applicable to servers and standalone machines. Attempting
to apply this patch to a client system will have no effect on
the system.
Error message: The /usr/sbin/pkgadd command is not executable.
Explanation and recommended action: The /usr/sbin/pkgadd
command cannot be executed. The most likely cause of this
is that installpatch is being run on a diskless or dataless
client and the /usr file system was not exported with
root access to the client. See the section above on
"Instructions for installing a patch on a diskless or
dataless client".
Error message: Patch directory is not of expected format.
Explanation and recommended action: The patch directory
supplied as an argument to installpatch did not contain
any patch packages. Verify that the argument supplied
to installpatch is correct.
Error message: The following validation errors were found:
Explanation and recommended action: Before applying the patch,
the patch application script verifies that the current
versions of the files to be patched have the expected
fcs checksums and attributes. If a file to be patched has
been modified by the user, the user is notified of this
fact. The user then has the opportunity to save the
file and make a similar change to the patched version.
For example, if the user has modified /etc/inet/inetd.conf
and /etc/inet/inetd.conf is to be replaced by the patch,
the user can save the locally modified /etc/inet/inetd.conf
file and make the same modification to the new file
after the patch is applied. After the user has noted all
validation errors and taken the appropriate action for
each one, the user should re-run installpatch using
the "-u" (for "unconditional") option. This time, the
patch installation will ignore validation errors and
install the patch anyway.
Error message: Insufficient space in /var/sadm to save old files.
Explanation and recommended action: There is insufficient
space in the /var/sadm directory to save old files.
The user has two options for handling this problem:
(1) generate additional disk space by deleting unneeded
files, or (2) override the saving of the old files by
using the "-d" (do not save) option when running installpatch.
However if the user elects not to save the old versions of
the files to be patched, backoutpatch CANNOT be used.
One way to regain space on a system is to remove the
save area for previously applied patches. Once the user
has decided that it is unlikely that a patch will be
backed out, the user can remove the files that were saved
by installpatch. The following commands should be executed
to remove the saved files for patch xxxxxx-yy:
cd /var/sadm/patch/xxxxxx-yy
rm -r save/*
rm .oldfilessaved
After these commands have been executed, patch xxxxxx-yy can
no longer be backed out.
Error message: Save of old files failed.
Explanation and recommended action: Before applying the patch,
the patch installation script uses cpio to save the old
versions of the files to be patched. This error message
means that the cpio failed. The output of the cpio
would have been preceded this message. The user should
take the appropriate action to correct the cpio failure.
A common reason for failure will be insufficient disk
space to save the old versions of the files. The user
has two options for handling insufficient disk space:
(1) generate additional disk space by deleting unneeded
files, or (2) override the saving of the old files by
using the "-d" option when running installpatch. However
if the user elects not to save the old versions of the
files to be patched, the patch CANNOT be backed out.
Error message: Pkgadd of package failed. See
/tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
patch packages failed. Any previously installed packages
in the patch should have been removed. See the log file
for the reason for failure. Correct the problem and
re-apply the patch.
Error message: error while adding patch to root template
Explanation and recommended action: The install script
determined this system to be a client server. The attempt
to apply the patch package to the appropriate root
template space located under /export/root/templates
failed unexpectedly. Check the log file for any failure
messages. Correct the problem and re-apply the patch.
Patch Backout Errors:
---------------------
Error message: Patch has not been applied to this system.
Explanation and recommended action: The user has attempted to back
out a patch that was never applied to this system. It is
possible that the patch was applied, but that the patch
directory /var/sadm/patch/ was deleted somehow.
If this is the case, the patch cannot be backed out. The
user may have to restore the original files from the
initial installation CD.
Error message: Patch was installed without backing up the
original files. It cannot be backed out.
Explanation and recommended action: Either the -d option of
installpatch was set when the patch was applied, or the save
area of the patch was deleted to regain space. As a result, the
original files are not saved and backoutpatch cannot be used. The
original files can only be recovered from the original
installation CD.
Error message: Pkgrm of package failed. See
/var/sadm/patch//log for reason for failure.
Explanation and recommended action: The removal of one of
patch packages failed. See the log file
for the reason for failure. Correct the problem and
run the backout script again.
Error message: Restore of old files failed.
Explanation and recommended action: The backout script uses the
cpio command to restore the previous versions of the files
that were patched. The output of the cpio command should
have preceded this message. The user should take the
appropriate action to correct the cpio failure.
KNOWN PROBLEMS:
On client server machines the patch package is NOT applied
to existing clients or to the client root template space.
Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED
THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH
METHOD ON THE CLIENT. See instructions above for
applying patches to a client.
After a patch package has been installed pkginfo(1) will
not recognize the SUNW_PATCHID macro in the patch package
pkginfo file. Instead, to identify patches installed on
the system use the grep command method described in the
patch README.
The pkgadd command shipped with Solaris 2.1 fails (drops core
without any error message) when there are more than 100
entries in the /etc/mnttab file. This means that installpatch
can fail, because it uses pkgadd. Since this is very likely on
any big system with lots of automounts, ANY patch could fail.
Applying patch 100901-01 fixes this problem (the README for
patch 100901 mentions shutting down the automounter while
applying it).
SEE ALSO
pkgadd(1), pkgchk(1), pkgrm(1), pkginfo(1)