Patch-ID# 101317-06 Keywords: lp bug fixes lpnet lpsched cf recvjob end_chage BSD lpstat class Synopsis: SunOS 5.3: lp jumbo patch Date: Mar/14/94 Solaris Release: 2.3 SunOS release: 5.3 Unbundled Product: Unbundled Release: Topic: SunOS 5.3: lp jumbo patch BugId's fixed with this patch: 1141029 1135499 1137207 1137927 1100419 1137926 1136082 1101959 1098546 1139105 1115802 1137210 1128006 1044250 1070962 1129606 1140418 1140477 1141160 1141332 1141761 1141956 1139662 1143441 1143444 1143446 1143510 1143055 1143838 1141249 1136170 1141853 1143367 1144048 1144072 1111688 1141029 1135499 1137207 1137927 1100419 1137926 1136082 1101959 1098546 1139105 1115802 1137210 1128006 1044250 1070962 1129606 1140418 1140477 1141160 1141332 1141761 1141956 1139662 1143441 1143444 1143446 1143510 1143055 1143838 1141249 1136170 1141853 1143367 1144048 1144072 1111688 1145448 1145870 1144043 1144449 1145327 1145152 1141849 1145123 1142820 1144635 1145448 1149427 1149580 1146832 1149964 1144207 1147848 1147650 1147671 1141893 1147668 1148893 1151467 1146831 1151762 1146147 1152980 1153256 1153621 1155160 1154392 1156459 1156226 1157069 Changes incorporated in this version: 1154392 1156459 1156226 1157069 Relevant Architectures: sparc 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: /usr/lib/lp/lpsched /usr/lib/lp/lpNet /usr/ucb/lpq /usr/ucb/lpc /usr/ucb/lpr /usr/ucb/lprm /usr/ucb/lptest /usr/bin/enable /usr/bin/disable /usr/bin/lpstat /usr/bin/lp /usr/bin/cancel /usr/sbin/lpadmin /usr/sbin/lpsystem /usr/sbin/lpforms /usr/sbin/lpusers /usr/sbin/lpmove /usr/sbin/lpfilter /usr/sbin/accept /usr/sbin/reject /usr/lib/lp/postscript/postio /usr/lib/lp/postscript/postreverse /usr/sbin/lpshut /etc/lp/fd/postprint.fd /usr/lib/lp/model/standard Problem Description: 1154392 'lpstat -o all' does not show jobs sent to a printer class 1156459 when printing to a class, special forms are ignored 1156226 lpNet can loose print jobs when receiving them from a 4.X/BSD system 1157069 Setting up two printers to use the same device dosn't work, jobs get mixed This patch fixes the following bugs: 1154392 lpstat -o all' does not show jobs sent to a pri 1156459 when printing to a class, special forms are ign 1156226 lpNet can loose print jobs when receiving them 1157069 Setting up two printers to use the same device (from 101317-05) 1152980 lpnet/lpsched botches up cf file when printing lots of files 1153256 lpNet overwrites existing print job with same job id in spool directory 1153621 changed print priorities will not take effect until lpsched has been restarted 1155160 when printing using forms, jobs from BSD clients print on any form This patch fixes the following bugs: 1152980 lpnet/lpsched botches up cf file when printing lots of files 1153256 updated recvjob, to correct request ID collisions 1153621 updated so end_chage reorders requests if priority changes 1155160 when printing using forms, jobs from BSD clients print on any form (from 101317-04) 1149427 lpsystem creates system with default threshold of 0 1149580 lpNet doesn't report some error informatio 1146832 the lp code has some serious problem that lint reports 1149964 error msg can cause command to segv on intel 1144207 lpstat causes system hang 1147848 lpNet dumps core/doesn't recover from TLI state change errors 1147650 lpstat -p -l dumps core 1147671 Spooler doesn't handle request-id collisions well; overwrites the older request. 1141893 postreverse often totally screws up 1147668 lpc clean doesn't clean all jobs in the queue. 1148893 lpNet logs connection/disconnect which can fill a filesystem 1151467 lpstat -t doesn't report the correct state (enable/disable) of printer. 1146831 parallel postscript printing support only works on bpp devices 1151762 lpsched auto-retry timeout is too long... 1146147 0 length files are left around in /var/spool/lp/tmp/ This patch fixes the following bugs: 1149427 lpsystem should create a system with the defa 1149580 lpNet doesn't report some error informatio 1146832 the lp code has some serious problem that lint 1149964 error msg can cause command to segv on intel 1144207 lpstat causes system hang 1147848 lpNet dumps core/doesn't recover from TLI st 1147650 lpstat -p -l dumps core 1147671 Spooler doesn't handle request-id collisions we 1141893 postreverse often totally screws up 1147668 lpc clean doesn't clean all jobs in the queue 1148893 lpNet logs connection/disconnect which can fill 1151467 lpstat -t doesn't report the correct state (ena 1146831 parallel postscript printing support only works 1151762 lpsched auto-retry timeout is too long... 1146147 0 length files are left around in /var/spool/lp (from 101317-03) This patch corrects a typo in the SUNW_PATCHID field in the pkginfo file in 101317-02 (from 101317-02) 1145448 too many print jobs can hang around and make /var very full 1145870 lpsched sends unnescessary work across net when multiple printers 1144043 lpNet will not accept a BSD print job if datafile is not sent first 1144449 disable(1M) doesn't fully disable printing from a print client. 1145327 lpNet hangs causing queue backup 1145152 status queries get queued when they shouldn't 1141849 lp xxx; rm xxx hangs lp system 1145123 lpNet can fial to connect to remote and cause request to never xfer 1142820 when using lp -H hold for remote printers, the held jobs don't show up 1144635 lpstat does not report when LaserWriter status This patch collects all of the lp bug fixes that have been made to date. This patch fixes a number of problems when printing with PC-NFS. This patch fixes a number of bugs that can cause lpsched to segv. If the print server already has a postscript printer configured, then the new standard interface script should be copied in place of the exisiting interface script. For example, if the printer is named xyz, then once the patch is installed, the standard interface script, /usr/lib/lp/model/standard, should be copied to /etc/lp/interfaces/xyz. Each printer will have a copy of the standard interface script in /etc/lp/interfaces, so a copy will need to be made for each printer. (from 101317-01) 1141029 lpsched crashed with "unexpected signal 11" 1135499 job forwarding causes lpsched abort 1137207 lpstat doesn't work well when remote printer doesn't exist 1137927 lpstat -o print status after printer removed 1100419 lpsched: very inefficient polling 1137926 can't remove system after connection established 1136082 lpsystem fails when modifying server type 1101959 Give no filter-name to"lpfilter -f" option doesn't receive proper error message 1098546 fix error message from cancel with no arguments 1139105 LP doesn't tranfer jobs to remote when printer has '-' in it's name 1115802 cancelling a 5.x job from a 4.x client sends an e-mail warning 1137210 lp -n X prints X copies of a document uncoalated 1128006 BSD lpr commands don't know about printer classes 1044250 lpc crashes with segmentation fault 1070962 cancel -u can not clean up the printing queue completely 1129606 lp cancels requests for no apparent reason 1140418 lpadmin doesn't remove all files when deleting printer 1140477 get printer idle when using bsd proto and remote spooler is down 1141160 job transmission error cause lpNet to loop.. 1141332 lpq doesn't work when print server is PC-NFS server 1141761 lpsched can hang after cancel pc-nfs print job 1141956 lpsched can segv after adding printer 1139662 LP system doesn't pass filenames back on status inqueries 1143441 lpsched leaks memory and accesses garbage 1143444 lpsched backlogs unnescessary work when a remote print server is down 1143446 lpstat -p name can cause lpsched to segv when pending lpstat 1143510 Intermittent delays while printing to a BSD print server. 1143055 the "all" keyword for lpadmin printer access does not work. 1143838 job-ids over 999 cause problems 1141249 lpstat hangs when lpshut during a job 1144048 using BSD protocol to non-BSD based systems can cause lpsched to segv 1144072 lpstat -o can hang 1111688 Messaging in LP package commands needs overhaul. 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: ----------------------------- Note: Before installing this patch, the print spooler must be shutdown since this patch replaces the print spooler daemons; lpsched and lpNet. As root, run lpshut before installing this patch. After the patch is installed, run /usr/lib/lpsched to restart the print spooler ----------------------------- none 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//usr The command: share -F nfs -o ro,root= \ /export/exec//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: ---------------------------------------------------------- Patch packets that have been installed can be identified by using the showrev command with the "-p" option: showrev -p Also note that installpatch has a similar "-p" option which will also just identify patches already installed. Command Descriptions -------------------- NAME installpatch - apply patch package to Solaris 2.x system backoutpatch - remove patch package, restore previously saved files SYNOPSIS installpatch [-udpV] [-S ] backoutpatch [-fV] [-S ] 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, turns off file validation. Allows the patch to be applied even if some of the files to be patched have been modified since original installation. -d Don't back up the files to be patched. This means that the patch can't be backed out. -p Print a list of the patches currently applied -V Print script version number -S Specify an alternate service (e.g. Solaris_2.3) for patch package processing references. backoutpatch: -f force the backout regardless of whether the patch was superseded -V print version number only -S Specify an alternate service (e.g. Solaris_2.3) for patch package processing references. 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 patch which has already been applied to this system. 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: None of the packages to patch are installed on this system. Explanation and recommended action: The original packages for this patch have not been installed and therefore the patch cannot be applied. The original packages need to be installed before applying the patch. 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: packages are not proper patch packages. Explanation and recommended action: The patch directory supplied as an argument to installpatch did not contain the expected package format. Verify that the argument supplied to installpatch is correct. Error message: The following validation error was 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/patch to save old files. Explanation and recommended action: There is insufficient space in the /var/sadm/patch 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 with error code . 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. Patch Installation Messages: --------------------------- Note: the messages listed below are not necessarily considered errors as indicated in the explanations given. These messages are, however, recorded in the patch installation log for diagnostic reference. Message: Package not patched: PKG=SUNxxxx Original package not installed Explanation: One of the components of the patch would have patched a package that is not installed on your system. This is not necessarily an error. A Patch may fix a related bug for several packages. Example: suppose a patch fixes a bug in both the online-backup and fddi packages. If you had online-backup installed but didn't have fddi installed, you would get the message Package not patched: PKG=SUNWbf Original package not installed This message only indicates an error if you thought the package was installed on your system. If this is the case, take the necessary action to install the package, backout the patch (if it installed other packages) and re-install the patch. Message: Package not patched: PKG=SUNxxx ARCH=xxxxxxx VERSION=xxxxxxx Architecture mismatch Explanation: One of the components of the patch would have patched a package for an architecture different from your system. This is not necessarily an error. Any patch to one of the architecture specific packages may contain one element for each of the possible architectures. For example, Assume you are running on a sun4m. If you were to install a patch to package SUNWcar, you would see the following (or similar) messages: Package not patched: PKG=SUNWcar ARCH=sparc.sun4c VERSION=11.5.0,REV=2.0.18 Architecture mismatch Package not patched: PKG=SUNWcar ARCH=sparc.sun4d VERSION=11.5.0,REV=2.0.18 Architecture mismatch Package not patched: PKG=SUNWcar ARCH=sparc.sun4e VERSION=11.5.0,REV=2.0.18 Architecture mismatch Package not patched: PKG=SUNWcar ARCH=sparc.sun4 VERSION=11.5.0,REV=2.0.18 Architecture mismatch The only time these messages indicate an error condition is if installpatch does not correctly recognize your architecture. Message: Package not patched: PKG=SUNxxxx ARCH=xxxx VERSION=xxxxxxx Version mismatch Explanation: The version of software to which the patch is applied is not installed on your system. For example, if you were running Solaris 5.3, and you tried to install a patch against Solaris 5.2, you would see the following (or similar) message: Package not patched: PKG=SUNWcsu ARCH=sparc VERSION=10.0.2 Version mismatch This message does not necessarily indicate an error. If the version mismatch was for a package you needed patched, either get the correct patch version or install the correct package version. Then backout the patch (if necessary) and re-apply. Patch Backout Errors: --------------------- Error message: Patch has not been successfully 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: This patch was obsoleted by patch $1. Patches must be backed out in the order in which they were installed. Patch backout aborted. Explanation and recommended action: The obsoleted contents of an older patch rev that apparently still exists under /var/sadm/patch should never be restored out of sequence. This could undermine the integrity of the more current patch rev installed and the restoration of the files it has saved. 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 return code . 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. A bug affecting a package utility (eg. pkgadd, pkgrm, pkgchk) could affect the reliability of installpatch or backoutpatch which uses package utilities to install and backout the patch package. It is recommended that any patch that fixes package utility problems be reviewed and, if necessary, applied before other patches are applied. Such existing patches are: 100901 Solaris 2.1 101122 Solaris 2.2 101331 Solaris 2.3 SEE ALSO pkgadd, pkgchk, pkgrm, pkginfo, showrev