From: Bütow, Michael (michael.buetow@comsoft.de)
Date: Mon Jan 12 2004 - 08:01:58 EST
Hi all,
Thanks to Michael Polnick, Dr Thomas Blinn and Randy Rogers for
pointing out the things I missed.
The "Technical Updates for Tru64 UNIX Version 5.0 and Higher
Patch Kits" at
http://h30097.www3.hp.com/docs/patch/tu_update/TITLETXT.HTM
mention this problem, stating the following:
Version 5.1B Patch Kits
Patch Kit 3
The following problems and issues have been reported against Patch Kit 3.
December 11, 2003: Shell Argument List Exceeds Limit
When installing a Release patch kit using dupatch from the command line,
rather than using the dupatch menus, you may see a message such as
/sbin/ls: arg list too long.
This occurs because the large number of patches, when concatenated on the
command line, exceed the shell's arg limit. To work around this problem,
temporarily change the sysconfigtab value by entering the following command:
# sysconfig -r proc exec_disable_arg_limit=1
Performing this command prior to the dupatch command solved my problem and
all 318 patches installed fine.
Dr Blinn also pointed out:
Second, using ". relative" path names for the patch tool or
the kit location is risky. Use the absolute path, even if
you use command substitution (e.g., `/bin/pwd` ) to get the
real path into the command and hence into the tool. I can
not say for certain that this is part of your problem, I
suspect it's the first thing noted above, but using "." as
the path to the tool and the path to the kit is risky, and
I do not recommend it.
Thanks to all who helped,
Michael
The original question was:
> Hello managers,
>
> I have just encountered a strange problem installing PK3
> for Tru64 5.1B on a set of DS10 machines which have been
> freshly installed.
>
> I untar it, then change to patch_kit/ directory and
> call up dupatch like this (as root, in multiuser):
>
> ./dupatch -install -kit . -name root -note XYZ -patch all
>
> It get the strange output which I have appended at the end
> of this mail.
>
> I have successfully installed this same PK3 on other machines
> (also DS10, but with larger hard disks), and never had any problems.
>
> Any suggestions?
>
> Michael Bütow
>
>
>
> =============== output from dupatch ======================
>
> :
> <beginning snipped>
> :
>
> *** You have selected 318 patches ***
>
> ************************** CAUTION
> ************************************
>
> Interruption of this phase of the operation will corrupt your
> operating system software and compromise the patch database
> integrity.
>
> DO NOT Ctrl/C, power off your system, or in any other way
> interrupt the patch operation. The patch operation is complete
> when you are returned to the Patch Utility menus.
>
> **********************************************************************
> *
>
>
> === Installing "Tru64 UNIX V5.1B" Patches:
> /usr/sbin/setld: /sbin/tar: arg list too long
> tar: No input
> ls: *.ctrl not found
> setld: The following specified subsets are not available on the
> distribution media:
>
>
>
> *** KERNEL CONFIGURATION AND BUILD PROCEDURE ***
>
> Saving /sys/conf/FRB1 as /sys/conf/FRB1.bck
>
>
> *** PERFORMING KERNEL BUILD ***
>
> A log file listing special device files is located in /dev/MAKEDEV.log
> Working....Sun Jan 11 21:49:25 UTC 2004
>
> The new kernel is /sys/FRB1/vmunix
>
> Please copy the new kernel file, /sys/FRB1/vmunix, to /vmunix prior to
> rebooting the system.
>
> * There were problems installing the following patch(es):
>
> :
> <long listing of patches snipped>
> :
> Patch 01147.00 - OpenGL library missing two extensions
> Patch 01266.00 - Fixes various problems with the X
> font server Patch 01268.00 - Fixes various problems
> with the X font server
> awk: Input line OSFPAT00113300540 O cannot be longer than 3,000
> bytes.
>
> The source line number is 3.
>
>
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:48 EDT