|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
HP-UX series 700 11.X patch digest
From: IT Resource Center (support_feedback
us-support2-mail.external.hp.com)
Date: Sun Jul 13 2003 - 13:57:16 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
HP Support Information Digests
===============================================================================
o IT Resource Center World Wide Web Service
---------------------------------------------------
If you subscribed through the IT Resource Center and would
like to be REMOVED from this mailing list, access the
IT Resource Center on the World Wide Web at:
http://support.itrc.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Support Information Digests (located under
Maintenance and Support). You may then unsubscribe from the
appropriate digest.
To download a patch referenced below, access the
IT Resource Center on the World Wide Web at:
http://support.itrc.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Individual Patches (under Maintenance and Support)
to access the patch. You may also download a patch via anonymous
ftp(1) from ftp.itrc.hp.com.
===============================================================================
Digest Name: weekly HP-UX series 700 11.X patch digest
Created: Sun Jul 13 6:05:20 EDT 2003
Table of Contents:
Document ID Title
--------------- -----------
PHSS_29375 s700_800 11.X OV SIP3.1 reporter performance module
PHNE_28409 s700_800 11.22 sendmail(1m) 8.11.1 patch
PHSS_28783 s700_800 11.00 OV ITO6.0X HP-UX 11.00/11.11 Agent A.06.15
PHKL_29080 s700_800 11.00 dyn semphores; big data space; msgmn; msgsnd
PHKL_29070 s700_800 11.11 application hangs using msg queues
PHCO_29236 s700_800 11.22 libc cumulative patch
PHNE_28809 s700_800 11.00 sendmail(1m) 8.9.3 patch
PHNE_28449 s700_800 11.00 Bind 4.9.7 components
PHCO_28845 s700_800 11.11 ioinitrc(1M) cumulative patch
PHCO_28830 s700_800 11.11 security(4) man page cumulative patch
PHCO_28798 s700_800 11.11 init(1M) cumulative patch
PHCO_28797 s700_800 11.11 /sbin/fs/hfs/bcheckrc patch
PHCO_27884 s700_800 11.11 /sbin/initcond cumulative patch
PHCO_29229 s700_800 11.00 Cumulative tar(1) patch
PHCO_29108 s700_800 11.00 Pthread library cumulative patch
PHNE_28993 s700_800 11.22 intl100 driver patch
PHNE_29032 s700_800 11.00 FTAM9000 E.06.01 patch
PHNE_29033 s700_800 11.11 FTAM9000 E.07.00 cumulative patch
PHSS_28959 s700_800 11.X OV ITO7.1X HP-UX 10.x Agent Patch A.07.20
PHSS_28960 s700_800 11.X OV ITO7.1X HP-UX 11.X ia64 Agent A.07.20
PHSS_29301 s700_800 11.X OV SIP3.0 Various problems in proxy
PHCO_29109 s700_800 11.11 Pthread enhancement and fixes
PHCO_29029 s700_800 11.11 libc cumulative patch
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_29375
Date Loaded: 20030711
Title: s700_800 11.X OV SIP3.1 reporter performance module
Patch Name: PHSS_29375
Patch Description: s700_800 11.X OV SIP3.1 reporter performance module
Creation Date: 03/07/09
Post Date: 03/07/11
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
OpenView Service Information Portal 3.1
Filesets:
HPOVSIP.OVSIP,fr=B.01.10,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_29375
Symptoms:
PHSS_29375:
The performance integration on OVReporter does not work
with Analyzer version greater than A.04.02.49.
Defect Description:
PHSS_29375:
Analyzer versions greater than A.04.02.49 require that the
SKIN parameter be specified in all requests. In this
particular case if the SKIN parameter is not specified it
does not return the list of groups accurately. It only
returns the "All" group. This causes reporter to fail.
Resolution:
Added "SKIN: REPORTER" to the call to Analyzer. This
ensures that Analyzer returns all the groups that the
reporter module is interested in.
Enhancement:
No
SR:
8606312745
Patch Files:
HPOVSIP.OVSIP,fr=B.01.10,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/reporter/Reporter.class
what(1) Output:
HPOVSIP.OVSIP,fr=B.01.10,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/reporter/Reporter.class:
None
cksum(1) Output:
HPOVSIP.OVSIP,fr=B.01.10,fa=HP-UX_B.11.00_32/64,v=HP:
2348976274 22287 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/modules/reporter/
Reporter.class
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
OVSIPSOL_00029:
sparcSOL: 2.6 2.7 2.8
OVSIPNT_00028:
intelWIN2000: 1.00
Patch Package Size: 40 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_29375
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_29375.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_29375. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_29375.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_29375.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_29375.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
========================================================
BEFORE LOADING THIS PATCH...
- Stop the Tomcat server.
- If you want to reinstall SIP, then you will have to
remove the patch. Once the re-install is over you
can apply the patch again.
NOTE : Tomcat is not started after the patch is loaded
You will need to manually start it.
Also, in order to keep a history of the patches
installed on your system the post-install script
will attempt to copy the PHSS_29375.text file
to /opt/OV/SIP/patches. Please make
sure this file is in /tmp before installation.
========================================================
-----End of Document ID: PHSS_29375------------------------------------------
Document ID: PHNE_28409
Date Loaded: 20030711
Title: s700_800 11.22 sendmail(1m) 8.11.1 patch
Patch Name: PHNE_28409
Patch Description: s700_800 11.22 sendmail(1m) 8.11.1 patch
Creation Date: 03/05/26
Post Date: 03/07/11
Hardware Platforms - OS Releases:
s700: 11.22
s800: 11.22
Products: N/A
Filesets:
InternetSrvcs.INETSVCS2-RUN,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP
InternetSrvcs.INETSVCS-RUN,fr=B.11.22,fa=HP-UX_B.11.22_IA/PA,v=HP
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.22,fa=HP-UX_B.11.22_IA/PA,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_28409
Symptoms:
PHNE_28409:
SR 8606281277/JAGae45221
1. Sendmail does not log the transient error message, "Name
server timeout" in the log file while processing the mail
queue.
SR 8606280837/JAGae44804
2. Under certain conditions, Sendmail does not
terminate/restart properly.
SR 8606291119/JAGae54962
3. Under certain conditions, Sendmail does not process the
mail queue properly.
SR 8606304587/JAGae67929
4. In some cases, Sendmail does not parse the headers
properly.
SR 8606295553/JAGae59235
5. In some cases, Sendmail does not parse the mail headers
properly.
SR 8606280818/JAGae44787
6. Under certain conditions, Sendmail or its associated
utilities may not operate properly.
SR 8606289625/JAGae53555
7. In some cases, smrsh(1m) does not operate properly.
SR 8606303971/JAGae67321
8. In some cases, Sendmail allows improper relaying.
SR 8606299235/JAGae62729
9. When the resolver retransmission timeout is set
to a value greater than 20 seconds in the Sendmail
configuration file /etc/mail/sendmail.cf, Sendmail
fails to resolve the client host names.
SR 8606293315/JAGae57065
10. When a name server transient error occurs, Sendmail
instantly retries to resolve the host name.
Defect Description:
PHNE_28409:
SR 8606281277/JAGae45221
1. When Sendmail is unable to resolve the address of the
host using the name service, a transient error "Name
Server Timeout" occurs. This error is displayed on the
terminal and is not logged in syslog file.
The default syslog file is /var/adm/syslog/mail.log.
Resolution:
Sendmail now logs the transient error messages in the
syslog file when the option "AlertTmpFailure" is
enabled in the Sendmail configuration file
/etc/mail/sendmail.cf. The error messages are logged as
a LOG_ALERT message at Loglevel >=2, and contain the
status information as specified below:
stat= "Transient parse error -- message queued for
future delivery"
To enable this option in the Sendmail configuration
file, perform the following steps:
a) Use /usr/newconfig/etc/mail/sendmail.cf as the base
Sendmail configuration file (/etc/mail/sendmail.cf)
with site-specific changes as required.
b) Edit "#O AlertTmpFailure=False" entry in the
/etc/mail/sendmail.cf as follows:
O AlertTmpFailure=True
c) Restart the Sendmail daemon.
SR 8606280837/JAGae44804
2. Due to a race condition, Sendmail does not
terminate/restart properly.
Resolution:
Code has now been modified to fix the problem.
SR 8606291119/JAGae54962
3. Under certain conditions, Sendmail does not process the
mail queue properly.
Resolution:
Use /usr/newconfig/etc/mail/sendmail.cf as the base
configuration file (/etc/mail/sendmail.cf) with
site-specific changes as required and restart the
Sendmail daemon.
SR 8606304587/JAGae67929
4. In some cases, Sendmail does not parse the headers
properly.
Resolution:
The code has been modified to parse the headers
properly.
SR 8606295553/JAGae59235
5. In some cases, Sendmail does not parse the mail headers
properly.
Resolution:
The code has been modified to parse the mail headers
properly.
SR 8606280818/JAGae44787
6. Under certain conditions, Sendmail or its associated
utilities may not operate properly.
Resolution:
Code has now been modified to fix the problem.
SR 8606289625/JAGae53555
7. In some cases, smrsh(1m) does not operate properly.
Resolution:
Code has now been modified to fix the problem.
SR 8606303971/JAGae67321
8. Due to specially quoted recipient addresses, Sendmail
allows improper relaying.
Resolution:
A new ruleset has now been added in the
/usr/newconfig/etc/mail/sendmail.cf file to remove
the special quotes in the recipient address.
Use /usr/newconfig/etc/mail/sendmail.cf as the base
configuration file (/etc/mail/sendmail.cf) with
site-specific changes as required and restart the
Sendmail daemon.
SR 8606299235/JAGae62729
9. Sendmail incorrectly sets resolver retry count to 0 when
the resolver retransmission timeout is set to a value
greater than 20 seconds.
Resolution:
Code has been modified to set the retry count to 1, when
the resolver retransmission timeout is set to a value
greater than 20 seconds.
SR 8606293315/JAGae57065
10. Sendmail interprets name server transient error values
in milliseconds instead of seconds. Due to this wrong
interpretation of the timeout value, Sendmail retries
to resolve the host name instantly.
Resolution:
Code has now been modified to interpret name server
timeout values in seconds.
Enhancement:
No
SR:
8606281277 8606280837 8606291119 8606304587 8606295553
8606280818 8606289625 8606303971 8606299235 8606293315
Patch Files:
InternetSrvcs.INETSVCS2-RUN,fr=B.11.22,fa=HP-UX_B.11.22_IA,
v=HP:
/usr/sbin/sendmail
/usr/sbin/makemap
/usr/sbin/mailstats
/usr/sbin/smrsh
/usr/bin/praliases
InternetSrvcs.INETSVCS-RUN,fr=B.11.22,
fa=HP-UX_B.11.22_IA/PA,v=HP:
/usr/newconfig/etc/mail/aliases
/usr/sbin/killsm
/usr/newconfig/etc/mail/convert_awk
/usr/newconfig/etc/mail/cf/README
/usr/newconfig/etc/mail/cf/cf/gen_cf
/usr/newconfig/etc/mail/sendmail.cf
/usr/newconfig/etc/mail/cf/m4/cfhead.m4
/usr/newconfig/etc/mail/cf/m4/proto.m4
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.22,
fa=HP-UX_B.11.22_IA/PA,v=HP:
/usr/share/man/man1m.Z/sendmail.1m
/usr/share/man/man1m.Z/killsm.1m
/usr/share/man/man1.Z/mailstats.1
/usr/share/man/man1.Z/praliases.1
what(1) Output:
InternetSrvcs.INETSVCS2-RUN,fr=B.11.22,fa=HP-UX_B.11.22_IA,
v=HP:
/usr/sbin/sendmail:
University of California. All rights reserved.
including Sendmail, Inc., and the Regents of the
Copyright (c) 1998 HEWLETT PACKARD COMPANY and its l
icensors,
version.c 8.11.1 (Berkeley) - PHNE_28409 - 05/05/2
003
HP-UX/General Millicode B.11.20.00 (IPF TOT): (MILLI
- 05/01/01)
/usr/sbin/makemap:
makemap.c 8.135.4.11 (Berkeley) 05/05/2003 (PHNE_284
09)
HP-UX/General Millicode B.11.20.00 (IPF TOT): (MILLI
- 05/01/01)
/usr/sbin/mailstats:
mailstats.c 8.53.16.11 (Berkeley) 05/05/2003 (PHNE_2
8409)
/usr/sbin/smrsh:
smrsh.c 8.31.4.5 (Berkeley) 05/05/2003 (PHNE_28409)
/usr/bin/praliases:
praliases.c 8.59.4.10 (Berkeley) 05/05/2003 (PHNE_28
409)
HP-UX/General Millicode B.11.20.00 (IPF TOT): (MILLI
- 05/01/01)
InternetSrvcs.INETSVCS-RUN,fr=B.11.22,
fa=HP-UX_B.11.22_IA/PA,v=HP:
/usr/newconfig/etc/mail/aliases:
aliases $Revision: 1.1.212.1 $ $Date: 99/09/13 15:13
:16 $
/usr/sbin/killsm:
05/05/2003 PHNE_28409
/usr/newconfig/etc/mail/convert_awk:
None
/usr/newconfig/etc/mail/cf/README:
None
/usr/newconfig/etc/mail/cf/cf/gen_cf:
None
/usr/newconfig/etc/mail/sendmail.cf:
cfhead.m4 8.76.4.13 (Berkeley) 05/05/2003 ###
##
cf.m4 8.32 (Berkeley) 2001/07/16 #####
generic-hpux10.mc 8.11 (Berkeley) 2001/07/16 #####
hpux11.m4 8.1 (Berkeley) 2001/07/16 #####
generic.m4 8.15 (Berkeley) 2001/07/16 #####
redirect.m4 8.15 (Berkeley) 2001/07/16 #####
use_cw_file.m4 8.9 (Berkeley) 2001/07/16 #####
always_add_domain.m4 8.9 (Berkeley) 2001/07/16 #
####
proto.m4 8.446.2.5.2.29 (Berkeley) 05/05/2003
#####
local.m4 8.50.16.2 (Berkeley) 2001/07/16 ###
##
smtp.m4 8.56.2.1.2.3 (Berkeley) 2001/07/16
#####
uucp.m4 8.38 (Berkeley) 2001/07/16 #####
/usr/newconfig/etc/mail/cf/m4/cfhead.m4:
cfhead.m4 8.76.4.13 (Berkeley) 05/05/2003')
/usr/newconfig/etc/mail/cf/m4/proto.m4:
proto.m4 8.446.2.5.2.29 (Berkeley) 05/05/2003
')
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.22,
fa=HP-UX_B.11.22_IA/PA,v=HP:
/usr/share/man/man1m.Z/sendmail.1m:
None
/usr/share/man/man1m.Z/killsm.1m:
None
/usr/share/man/man1.Z/mailstats.1:
None
/usr/share/man/man1.Z/praliases.1:
None
cksum(1) Output:
InternetSrvcs.INETSVCS2-RUN,fr=B.11.22,fa=HP-UX_B.11.22_IA,
v=HP:
2093134837 2312468 /usr/sbin/sendmail
64206590 1033808 /usr/sbin/makemap
3851395572 20272 /usr/sbin/mailstats
3742113927 16036 /usr/sbin/smrsh
4113978029 1030032 /usr/bin/praliases
InternetSrvcs.INETSVCS-RUN,fr=B.11.22,
fa=HP-UX_B.11.22_IA/PA,v=HP:
1003701682 870 /usr/newconfig/etc/mail/aliases
3542390776 1191 /usr/sbin/killsm
848421388 2197 /usr/newconfig/etc/mail/convert_awk
1289403273 129635 /usr/newconfig/etc/mail/cf/README
2328392203 32722 /usr/newconfig/etc/mail/cf/cf/gen_cf
3563491284 100762 /usr/newconfig/etc/mail/sendmail.cf
23678029 55104 /usr/newconfig/etc/mail/cf/m4/cfhead.m4
3491630843 95283 /usr/newconfig/etc/mail/cf/m4/proto.m4
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.22,
fa=HP-UX_B.11.22_IA/PA,v=HP:
217235634 15074 /usr/share/man/man1m.Z/sendmail.1m
776513495 1068 /usr/share/man/man1m.Z/killsm.1m
3264046413 2626 /usr/share/man/man1.Z/mailstats.1
2657485999 1816 /usr/share/man/man1.Z/praliases.1
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHNE_28810:
s700: 11.11
s800: 11.11
PHNE_28809:
s700: 11.00
s800: 11.00
Patch Package Size: 2100 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHNE_28409
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_28409.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_28409. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHNE_28409.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_28409.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_28409.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
To comply with industry-standard sendmail(1M) practices,
after the installation of PHNE_28409, or any superseding
patch, the following behavior will be observed:
1. Non-root users will not be able to print system-wide
sendmail aliases using the praliases(1) command.
2. Non-root users will not be able to print mail traffic
statistics using the mailstats(1) command.
3. Non-root users will not be able to send signals to
sendmail processes, even their own.
4. Sendmail reacts more appropriately to user signals,
which may introduce some delay in terminating and
restarting sendmail.
5. Sendmail and mailstats reports notification messages
on any improper related files or databases.
The behaviors one and two mentioned above may
remain even after the removal of the patch.
This patch delivers a new copy of the sendmail
configuration file /etc/mail/sendmail.cf as
/usr/newconfig/etc/mail/sendmail.cf. You need to merge
your site-specific customizations with this new
sendmail.cf file. Then, stop and start the sendmail
daemon by using the following commands, respectively:
/sbin/init.d/sendmail stop
/sbin/init.d/sendmail start
-----End of Document ID: PHNE_28409------------------------------------------
Document ID: PHSS_28783
Date Loaded: 20030710
Title: s700_800 11.00 OV ITO6.0X HP-UX 11.00/11.11 Agent A.06.15
Patch Name: PHSS_28783
Patch Description: s700_800 11.00 OV ITO6.0X HP-UX 11.00/11.11 Agent A.06.15
Creation Date: 03/07/09
Post Date: 03/07/10
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
OpenView IT/Operations 6.0
Filesets:
OVOPC-CLT.OVOPC-UX11-CLT,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28783
Symptoms:
PHSS_28783:
- SR: 8606262299
The logfile encapsulator reports that the File to be
executed for preprocessing of a logfile template failed.
This error occurs randomly and only from time to time.
You will get an error message similar to the following:
Command 'opcfwtmp /tmp/wtmp.stat /var/adm/wtmp
/tmp/wtmp.out' configured in source 'Logins (10.x/11.x
HP-UX)' returns 1. Ignoring this logfile. (OpC30-107)
- SR: B555014591
When the OPC_INT_MSG_FLT is set to TRUE then the filtered
message is received corrupted on the server in
a Japanese environment.
- SR: B555015331
The monitor agent, opcmona, may report wrong results of
executed monitor scripts or programs when using many
'advanced monitors' such as OVPERF. In some of these
cases opcmona might even abort.
- SR: B555015626
opcif_read() doesn't return data if the signal pipe is
empty, but there is still more data in the queue file.
This can for example happen if the maximum pipe size of
8192 bytes was reached and therefore no more signal
bytes could be written into the signal pipe.
- SR: B555015758
opcmsgi aborts if one of the set attributes has an
unmatched '<'.
PHSS_28177:
HSLco33987
- SR: H555007666
mailq_l.sh does not count mails correctly if a sendmail
version 10 or above is used.
- SR: H555008275
Message Agent can hang for no apparent reason and stop
sending all messages to the Management Server regardless
of its state.
- SR: H555008529
If a process dies immediately after being started by
Control Agent, it is possible that OpC30-1094 messages
start appearing in the error logfile.
- SR: H555008553
- itochecker was able to collect only information from
the management server. There was no possibility to
collect information from the managed nodes.
Checking the kernel parameters did not return
the correct values by itochecker. No information
about opcerror was gathered by itochecker.
- SR: H555008602
Customer sets OPC_RPC_ONLY to TRUE in opcinfo. After a
while, Message Agent coredumps.
- SR: 8606187183
After deploy/undeploy of policies/templates the
suppressing-times are lost. Messages that should be
suppressed after a deploy/undeploy of policies/templates
are shown.
- SR: 8606189243
Utility for checking basic types of communication
between ito server and agents is missing.
- SR: 8606232431
VPO tries to resolve node name that only contains only
blanks because of typo in template definition or
variable assignment.
- SR: 8606242614
Messages are incorrectly suppressed by the logfile
encapsulator if "suppress identical output messages" is
specified and the messages differ only in the values of
<$LOGFILE> and/or <$LOGPATH>.
- SR: 8606282247
The Logfile Encapsulator does not perform variable
replacement for all Message Defaults fields, e.g. the
<$LOGFILE> and <$LOGPATH> variables are not replaced
in the Object and Application fields.
- SR: B555014942
The opcle process loops if a logfile is removed while
it is being read.
- SR: 8606244523
When using the syntax <`script`> in the logfile template
and the script returns the same logfile name twice, the
opcle will abort.
- SR: B555013620
Support for pmd's "u" option needed in opctrapi: use the
UDP packet's address as source of the trap.
- SR: B555013719
Message agent doesn't stop message buffering when the
management server is available again after a network
outage, fixed DNS problem or similar.
This can happen when the agent restarts/the machine
reboots during the network problem occurred.
- SR: B555013794
The current directory should be removed from the agent's
environment PATH. That way only files can be executed
that are either specified with the full path or the path
is explicitly specified in the PATH.
- SR: B555013891
In MoM environments, opcmsga does not return action
responses to SECONDARY managers, if their name is not
resolvable.
- SR: B555014093
opcmona may crash (UNIX) or doesn't process all SCHEDULE
templates (Windows) when using SCHEDULE templates.
- SR: B555014132
During a distribution the agent may report an error like:
ITO responsible manager configuration. (OpC30-1203)
Cannot open file \usr\OV\tmp\OpC\cfgchg.
System Error Number: 13 (d) - The data is invalid.
(OpC20-63)
- SR: B555014215
The port should be configurable where opctrapi listens
for incoming traps.
- SR: B555014245
Traps of size greater than 5 Kb not handled properly by
opctrapi if local trap interception is used.
- SR: B555014574
opcagt -start/-stop/-status doesn't work correctly, if
the currently running agent can't be reached over RPC.
- SR: B555014596
Including fixes from the ECS runtime engine with
PHSS_26909 and equivalent.
- SR: B555014715
The Control Agent slowly grows in memory usage.
- SR: B555014851
opcmsga sends the same message operation (e.g. an
acknowledge request created by opcmack(1) )
again and again if the related message is not in the
cache and one of the target managers can not be reached.
- SR: B555008674
The opcagt command has a -version option which is not
described in the opcagt(1m) man page.
PHSS_26727:
- SR: 8606222554
Certain policies in VPW do not work as expected, for
example:
VP_WIN-WINS-FwdAllInformation
VP_WIN-WINS-FwdAllWarnError
VP_WIN-DHCPCl_FwdAllInfo
VP_WIN-DHCPCl_FwdAllWarnError
This problem can also occur for VPO during condition
matching. Matching the application and object attributes
is now case sensitive. For example, a message with
application "TEST" is matched but application "tEST" is
unmatched.
- SR: 8606227840
Variables in the template default message key are not
resolved for unmatched messages.
- SR: 8606233602
If using a pattern like '<*.prefix>ERR<*.suffix>', the
prefix variable will get assigned a wrong text if it
should be empty.
- SR: B555012929
If you run opcdista from commandline, you don't get any
useful messages, only the internal status letters.
For supportability, it would be better to have
some explicit status and error reporting.
- SR: B555013371
Sometimes the new scheduled action template configuration
is not loaded after a distribution. Instead, the old
scheduled actions are still started.
- SR: B555013435
The message agent opcmsga hangs unpredictably. This is
more likely to happen on systems with a very high ICMP
traffic.
- SR: B555013495
In Japanese environments programs using the agent APIs
can fail with errors on invalid or incompatible codesets.
- SR: B555013699
When running actions or applications like 'yes |
something', the 'yes' process keeps running after the
action finished on HPUX 11.
PHSS_25540:
- SR: H555006719
If the agent is running as a non-root user, when the
management server processes are restarted, the agent has
to be restarted, else messages are buffered.
- SR: 8606213476
The distribution to nodes may hang or fail. This is more
likely to happen while distributing to Windows NT/2000
nodes rather than on UNIX nodes.
- SR: B555007980
Local automatic actions are started immediately, even
though agent MSI is enabled in divert mode and the
'Immediate Local Automatic Action' box is not checked.
- SR: B555008220
The <$MSG_TIME_CREATED> variable is not substituted in
the message template.
- SR: B555008838
The event correlation engine creates a 'Time cannot go
backwards' error if the system is very busy.
- SR: B555009745
The template default of the object field of a monitor
template is not used.
- SR: B555010620
Some messages are missing in the Japanese message
catalog. You get a 'Cannot generate message' error.
- SR: B555010955
Even if you used opcswitchuser.sh to specify a non-root
user which should run the ITO agent, it will still be
started as user root after a system reboot.
- SR: B555010966
A message key relation containing <*> does not always
match message keys correctly. This results in messages
not being acknowledged when they should.
- SR: B555011184
opcagt fails to start opcctla if it is started as
./opcagt and /opt/OV/bin/OpC is not in the search PATH.
- SR: B555011505
1. opcecm/opceca might run in a dead lock while
processing lots of ECS annotate nodes
2. opcecm/opceca might leak memory when ECS annotate
nodes are used
- SR: B555011594
The original message text of a logfile encapsulator
message is wrong if <$LOGPATH> or <$LOGFILE> is used.
- SR: B555011638
Pattern matching cannot match the new line character
of multi-line messages.
- SR: B555011979
Pattern matching hangs if only single byte Japanese
HANKAKU KANA characters are used.
- SR: B555011990
ECS event log (ecevilg) has invalid time difference to
the next message which can cause the ECS simulator
to hang or appear to hang when loading an event log file
with such values.
- SR: B553000162
After opcagt -stop, opcagt -status tells that the control
agent does not run although it is running and sometimes
you get the following error in the message browser:
'Ouput of kill -0 differs from internal pids-table for
index <number> (OpC30-1094)'
PHSS_24610:
- SR: B555010879
opctrapi aborts during template distribution if
conditions with the 'Suppress Identical Output Messages'
features are used.
- SR: B555010899
opcdista requests distribution data from a wrong manager
if there is a secondary manager with the same short
hostname than the appropriate primary manager.
- SR: B555010948
Nested alternatives were not handled correctly in the
pattern matching algorithm, e.g. the pattern '[a|b]c|d'
was handled like '[a|b|d]c'.
- SR: B555010980
Traps without a SNMP variable are not matched because
server patch adds an extra attribute to the template.
- SR: B555011126
Agent distribution using the new Secure Shell (SSH)
method introduced with the A.06.08 server patches
doesn't work for HP-UX agents. Nothing is installed
but you get no error message about it. The only hint is
that the "Unpacking truck file /tmp/opc_tmp/opc_pkg.Z"
message is not displayed during the installation.
PHSS_23989:
- SR: 8606180583
When the VPO agent was started manually from an MC/SG
shared volume, the agent was killed upon package stop.
This was because the agent used this volume as the
current directory. Now the agent always starts in /tmp.
This also has the side effect that any core file for the
agent is written into /tmp.
- SR: 8606180891
The template default for the service name is not used.
- SR: 8606181988
The event interceptor doesn't forward on
"forward unmatched" if a "suppress unmatched" condition
is used in a second template
- SR: 8606182250
opcfwtmp doesn't trap bad login from CDE login.
- SR: 8606182981
The ITO agent is not started after system reboot if the
default runlevel is lower than 3 and you don't get any
warning about that fact.
- SR: B555010341
Agent sometimes does not start automatically after reboot
while manual start works fine.
PHSS_23822:
- The event correlation process opceca (agent) / opcecm
(server) might crash after processing several annotation
nodes
- The VPO A.06.03 patches for HP-UX and Solaris do
not work as expected in firewall environments:
While server port restrictions are still regarded,
client-side port restrictions are ignored.
PHSS_22882:
- Changes were required for the security add-on product
VantagePoint Advanced Security.
- agent installation configure script fails to convert
ITO 4 queue files: awk syntax error in swagent.log file
PHSS_22013:
- disk_mon.sh returns invalid values if the bdf command
returns more than one line output for a filesystem
(e.g. if the filesystem name exceeds its column width)
- Several changes for firewall environments. For detailed
information refer to the VPO Firewall Configuration
White Paper version 3.0
- When executing large numbers of autoactions, some of them
were staying in 'running' state.
- opctrapi aborts after getting traps with unresolvable IP
address.
- The handling of '\' was different in the pattern
definition and the "matching pattern".
- if buffer file size limitation is enabled the agent may
discard low-severity messages even if there is still
space in the buffer file
Defect Description:
PHSS_28783:
- SR: B555014591
The defect was caused by the double conversion from the
server code set to the internal code set, once on the
agents side when it sent the internal message to opcmsga
and once by opcmsgi when it forwarded the message again.
Now, the message is converted back from the internal code
set to the server code set in opcmsga before sending the
message to the opcmsgi queue. The management server will
get the message through opcmsga in the internal code set,
and it will convert it into the server code set.
The conversion is made only if the internal code set is
different from the server code set.
- SR: B555015331
opcmona holds a central table for all subprocess related
information. Advanced monitors are executed in separate
threads and could access this table in parallel, thus
overwriting each other's data. The table accesses are now
serialized by a mutex.
for SR's not listed in this section please see
the list of symptoms
PHSS_28177:
- SR: H555007666
The output of sendmail been changed. So the regular
expression needs to be modified.
- SR: H555008275
Signal handler for SIGIO was installed before the socket
on which we receive ICMP replies was set to non-blocking
mode. An unsolicited SIGIO would trigger the signal
handler which would wait indefinitely on the socket for
data, which would never arrive. Since NCS agent is
single-threaded, all communication would stop.
The fix is in setting the non-blocking mode before
installing the signal handler, so it would not wait
forever.
- SR: H555008529
This is a timing issue, where internal structures are not
updated by the signal handler in time for proper values
to be written in the PIDS file.
An additional check for process presence has been
implemented before writing of the PIDS file.
- SR: H555008553
Resolution:
- itochecker_agt and its configuration file
itochecker_agt.conf were introduced.
Checking the kernel parameters now returns the
correct values. An additional option (8) was
added which gets opcerror file on management
server.
- SR: H555008602
When using OPC_RPC_ONLY, ICMP handling is not
initialized, but Message Agent will call
opc_pb_ping_reset() after a successful server checkalive
cycle. This causes an invalid (NULL) pointer to be
dereferenced and causes a coredump.
opc_pb_ping_reset() now has a check to see if ICMP
handling has been initialized and if not, immediately
returns from the function.
- SR: 8606187183
The OpenMessageInterceptor restarts after a
deploy/undeploy of policies/templates. During this
process all the policy-/template-information is cleaned
and read again from a temp-file. Because suppressing-
times are not stored in this temp-file, this times are
lost.
Now the suppressing-times are taken over to the new data.
- SR: 8606189243
Basic ICMP check, TCP chack and SNMP check is needed.
- SR: 8606232431
VPO now ignores node names that contain only white space
characters without contacting the name service.
- SR: 8606242614
The variables <$LOGFILE> and <$LOGPATH> were replaced
after the suppression rules were evaluated. Therefore the
comparison did not use the actual logfile name or path,
but compared the string "<$LOGFILE>" or "<$LOGPATH>".
- SR: 8606244523
The opcle aborts when a <`script`> returns a logfile name
twice. This is because of referencing and handling the
same file twice.
To fix this, the opcle checks whether the same logfile
has been returned already and when adding to the internal
list, each logfile gets added exactly once.
- SR: B555013620
NNM 6.2 introduced an event option to pmd - "u". This
option specifies to prefer the IP address in an SNMPv1
trap's UDP header over the contents of the SNMPv1 trap
PDU's agent_addr field.
A new opcinfo variable OPC_USE_UDP_AS_TRAP_SOURCE was
added for opctrapi. If set to TRUE, opctrapi will use the
UDP address instead of the agent_addr.
- SR: B555013719
Message agent remains in buffering mode even when
the management server is available again.
The reason is that the agent wasn't able to resolve
the management server name to an IP address at startup
and the agent doesn't try again during runtime.
This has been fixed by checking for a resolvable name
every time a message should be buffered till the name can
be resolved, after this the normal checkalive mechanism
which handles buffered message takes place.
- SR: B555013891
Even if the IP address of the management server was
specified in the mgrconf file, it was not used except for
the primary manager. This behaviour was changed to give
the mgrconf file precedence over name resolution.
- SR: B555014093
opcmona may crash (UNIX) or doesn't process all SCHEDULE
templates (Windows) when using SCHEDULE templates.
This can occur when there are only spaces in
one of the schedule fields (Minute, Hour, Day of the
Month, Month, Year, Day of the Week).
You can verify this by going to the conf/OpC directory on
the node and doing an opcdcode monitor. When
there are entries like WEEKDAY " " the problem can occur.
Now the monitor agent treats sequences of spaces like
an empty string that is a wildcard and uses all valid
values in the possible range.
For WEEKDAY this is 0-6.
- SR: B555014132
During a distribution the agent may report error number
OPC30-1203/OPC20-63 when trying to access the cfgchg
file.
The cause for this problem is that there are several
processes trying to get exclusive access to this file
at the same time. The problem has been fixed by doing a
retry for 10 times in case the error should occur with a
delay of one second.
- SR: B555014215
Using the new opcinfo variable SNMP_TRAP_PORT <port_num>
opctrapi can now be configured to listen on another port
than 162. This is only effective, if traps are not
received through the NNM pmd.
- SR: B555014574
With this changes the opcctla is now be able to deal with
a running opcctla that is not reachable via RPC:
opcagt -status will display a warning if the currently
running opcctla is not reachable over RPC, but then it
will display the status according to the pids file.
opcagt -stop will also kill the unresponsive opcctla and
try to start a new one.
If opcctla not reachable over RPC, opcagt -start will
kill all running agent processes and then start a new
opcctla which starts the agent processes.
But of course, the agent won't be able to start if RPC
is still not available at that time.
- SR: B555014851
opcmsga maintains an internal cache to find out the
target managers per message ID. The cache expires
after 1 hour (can be changed with the opcsvinfo variable
OPC_STORE_TIME_FOR_MGR_INFO) and then it runs into a
problem in its algorithm so that a message operation on
a non-cached message is sent again and again until the
last target manager in an internal list can be reached.
for SR's not listed in this section please see
the list of symptoms
PHSS_26727:
- SR: 8606222554
The condition test for the message attributes
application, object and message group are always done
case sensitive, therefore a message with the application
"TEST" matches but "tEST" does not match.
With this patch an opcinfo flag is introduced, which
allows to switch between case sensitive and case
insensitive check.
flag : OPC_COND_FIELD_ICASE
type : boolean
default: FALSE
By setting this to true the policies mentioned above will
work.
- SR: B555012929
The opcdista communicates with the opcctla process via
stdin/stdout so if you run it from commandline, you only
see the status letters but don't know what they mean.
The new '-v' option prints more output, e.g.:
$ ./opcdista -v
0 - No distribution data available.
- SR: B555013435
One thread tried to read from a socket while another
thread closed it. This could happen due to missing
locking of global data. This data is now guarded by a
mutex.
- SR: B555013495
When tracing was added to the API functions a necessary
NLS initialization was not done. This problem was
introduced only by the A.06.10 patches for HPUX.
- SR: B555013699
Before executing the action, the signal handler function
of opcacta was not reset.
for SR's not listed in this section please see
the list of symptoms
PHSS_25540:
- SR: H555006719
When a communication to a message receiver fails, the
message agent starts buffering messages. It periodically
checks if a server is alive by sending it ICMP packets.
If the server cannot be reached with ICMP packets, no RPC
communication is attempted. Sending ICMP packets is not
possible when the agent is running as a non-root user, so
the sending function cannot actually send anything.
Therefore we also never receive any replies and the
message agent will buffer messages forever. To fix this,
the internal state of the message agent is updated after
we tried to send an ICMP packet if the agent is running
as a non-root user.
- SR: 8606213476
While the agent receives several RPC calls, like "Start
Distribution", "Execute Action" or "Set Primary Manager"
in parallel, it may happen that the call results in a
conflict within the control agent, which causes the
NT control agent to bring a Dr. Watson window.
This conflict can also occur on UNIX but the control
agent does not die, rather the RPC request may fail.
With this version the RPC calls which could cause
conflicts are serialized.
- SR: B555010955
The non-root user was added to the startup configuration
file but not used.
- SR: B555010966
The processing of the key relation is wrong for the log
file encapsulator. The problem is that all unresolved
entries followed by a resolved entry are removed.
Other unresolved entries are kept as they are.
- SR: B555011184
The working directory for the ITO agent was changed
from /opt/OV/bin/OpC to /tmp to avoid problems if
the agent is running in an MC/SG environment.
- SR: B555011638
VPO could not match for for new line of multi line
messages. Following changes have been made to allow this:
It is now possible to use ^M (\r) as field separator.
New patterns are introduced: </> to match any number of
line breaks (UNIX style \n or NT style \r\n) and <n/> to
match exactly n line breaks, for example <1/> will match
exactly one line break.
This change works only for sources that already can
create multi line messages (for example opcmsg or NT
event log), it does not allow multi line logfile
encapsulation.
This change requires a fix on the management server and
the agent. Therefore a patch on the management server and
a patch for the agent is required to use the new
functionality.
for SR's not listed in this section please see
the list of symptoms
PHSS_24610:
- SR: B555010879
When freeing the allocated memory, a wrong function was
used.
- SR: B555010899
opcdista requests distribution data from a wrong manager
if there is a secondary manager with the same short
hostname than the appropriate primary manager because it
searches the whole list in for each name it tries to
match first the long then the short name. Instead it
should try the long names for all systems first and only
then try to match using the short names.
- SR: B555010948
The grammar was changed to allow nested alternatives and
process it correctly.
- SR: B555011126
The SSH agent installation method is not known to the
opcrinst script which should unpack the agent on the
target not. Thus the opcrinst script simply does nothing.
for SR's not listed in this section please see
the list of symptoms
PHSS_23989:
- SR: 8606182250
opcfwtmp didn't handle the LOGIN_PROCESS value of the
wtmprec.ut_type field of the WTMP structure, so the bad
logins from CDE haven't been detected.
- SR: 8606182981
The ITO agent was integrated into the systems startup
process at runlevel 3 but up we didn't check the
default runlevel from /etc/inittab. Now there is a check
and you'll get a warning if the default runlevel is
lower than 3.
- SR: B555010341
When the process ID of the 'opcctla -start' is the same
as of the running opcctla before the shutdown, the
internal logic concluded that the agent is already
running and did not start up the subprocesses.
for all other defects not listed in this section please see
the list of symptoms
PHSS_23822:
see the list of symptoms
PHSS_22882:
see the list of symptoms
PHSS_22013:
see the list of symptoms
Enhancement:
No
SR:
H555008602 H555008553 H555008529 H555008275 H555007666
H555006719 B555015758 B555015626 B555015331 B555014942
B555014851 B555014715 B555014596 B555014591 B555014574
B555014245 B555014215 B555014132 B555014093 B555013891
B555013794 B555013719 B555013699 B555013620 B555013495
B555013435 B555013371 B555012929 B555011990 B555011979
B555011638 B555011594 B555011505 B555011184 B555011126
B555010980 B555010966 B555010955 B555010948 B555010899
B555010879 B555010620 B555010341 B555010079 B555009745
B555009155 B555009152 B555008838 B555008674 B555008613
B555008314 B555008220 B555007980 B555007752 B555007709
B555007602 B555007426 B555006890 B555006267 B553000162
8606282247 8606262299 8606244523 8606242614 8606233602
8606232431 8606227840 8606222554 8606213476 8606189243
8606187183 8606182981 8606182250 8606181988 8606180891
8606180583 8606137088
Patch Files:
OVOPC-CLT.OVOPC-UX11-CLT,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/opc_pkg.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/install/opcrclchk
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/install/opcrdschk
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/install/opcrndchk
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/install/opcroschk
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/install/opcrverchk
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/install/opcrinst
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/ana_disk.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/cpu_mon.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/disk_mon.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/last_logs.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/mailq_l.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/proc_mon.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/sh_procs.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/swap_mon.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/vp_chk.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/dist_mon.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/mondbfile.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/ssp_chk.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/opcfwtmp.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/opcnprcs.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/
opc_get_ems_resource.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/actions/mailq_pr.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/actions/st_inetd.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/actions/st_syslogd.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/actions/st_mail.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/actions/dist_del.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/cmds/opcdf.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/cmds/opclpst.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/cmds/opcps.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/cmds/E10000Log.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/cmds/ssp_config.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/cmds/opc_sec_v.sh.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/AgentPlatform
what(1) Output:
OVOPC-CLT.OVOPC-UX11-CLT,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/opc_pkg.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/install/opcrclchk:
HP OpenView VantagePoint A.06.15 (03/05/03)
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/install/opcrdschk:
HP OpenView VantagePoint A.06.15 (03/05/03)
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/install/opcrndchk:
HP OpenView VantagePoint A.06.15 (03/05/03)
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/install/opcroschk:
HP OpenView VantagePoint A.06.15 (03/05/03)
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/install/opcrverchk:
HP OpenView VantagePoint A.06.15 (03/05/03)
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/install/opcrinst:
HP OpenView VantagePoint A.06.15 (03/05/03)
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/ana_disk.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/cpu_mon.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/disk_mon.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/last_logs.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/mailq_l.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/proc_mon.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/sh_procs.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/swap_mon.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/vp_chk.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/dist_mon.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/mondbfile.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/ssp_chk.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/opcfwtmp.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/opcnprcs.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/monitor/
opc_get_ems_resource.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/actions/mailq_pr.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/actions/st_inetd.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/actions/st_syslogd.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/actions/st_mail.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/actions/dist_del.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/cmds/opcdf.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/cmds/opclpst.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/cmds/opcps.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/cmds/E10000Log.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/cmds/ssp_config.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/A.06.15/RPC_DCE_TCP/cmds/opc_sec_v.sh.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
hp-ux11/AgentPlatform:
None
cksum(1) Output:
OVOPC-CLT.OVOPC-UX11-CLT,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
2270676370 7845843 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
opc_pkg.Z
2838479126 6708 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
install/opcrclchk
1521528796 28923 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
install/opcrdschk
1307548077 6720 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
install/opcrndchk
1125915935 6287 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
install/opcroschk
1575687533 31983 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
install/opcrverchk
415936657 105394 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
install/opcrinst
3859795075 2731 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
monitor/ana_disk.sh.Z
1079954573 5979 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
monitor/cpu_mon.sh.Z
2023332698 6060 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
monitor/disk_mon.sh.Z
1204538408 5849 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
monitor/last_logs.sh.Z
2054002572 5844 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
monitor/mailq_l.sh.Z
3584826231 6008 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
monitor/proc_mon.sh.Z
1933828630 5437 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
monitor/sh_procs.sh.Z
3419925051 5879 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
monitor/swap_mon.sh.Z
2428729855 5736 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
monitor/vp_chk.sh.Z
77690629 6126 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
monitor/dist_mon.sh.Z
1820341262 14374 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
monitor/mondbfile.sh.Z
3629045713 5980 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
monitor/ssp_chk.sh.Z
1452569009 14447 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
monitor/opcfwtmp.Z
4262503135 10961 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
monitor/opcnprcs.Z
1375255420 19575 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
monitor/opc_get_ems_resource.Z
1301661940 2537 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
actions/mailq_pr.sh.Z
4179670471 2581 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
actions/st_inetd.sh.Z
2882149068 2590 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
actions/st_syslogd.sh.Z
2066026786 2582 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
actions/st_mail.sh.Z
1319021143 6112 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/
actions/dist_del.sh.Z
3029083079 325 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/cmds/
opcdf.Z
3456064330 386 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/cmds/
opclpst.Z
4254404400 401 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/cmds/
opcps.Z
2955809827 3322 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/cmds/
E10000Log.sh.Z
1585784939 3109 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/cmds/
ssp_config.sh.Z
1228535185 13159 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/A.06.15/RPC_DCE_TCP/cmds/
opc_sec_v.sh.Z
3588571212 6324 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/pa-risc/hp-ux11/AgentPlatform
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_28177 PHSS_26727 PHSS_25540 PHSS_24610 PHSS_23989 PHSS_23822
PHSS_22882 PHSS_22013
Equivalent Patches: None
Patch Package Size: 7610 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_28783
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28783.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28783. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_28783.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28783.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28783.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
(A) Patch Installation Instructions
-------------------------------
(A1) Install the patch, following the standard installation
instructions provided above under "Installation
Instructions".
Observe that you can use opc_backup(5) for backing up
your system before installing a patch.
NOTE: Make sure that no agent of the platform
addressed by this patch is distributed (either
from the ITO Administrator's GUI or from command
line using inst.sh) while running swremove.
If you are running VPO in a MC/ServiceGuard
installation:
- Note, that only files on the shared disk volume
at /var/opt/OV/share will be patched. Therefore
install the patch on one cluster node while the
shared disks are mounted. The server processes
may be running during patch installation.
- It is not necessary to install this patch on all
cluster nodes. Even if the software inventory on
the other cluster nodes will not be updated, the
patched files will be available there when the
shared disk is switched to them.
NOTE: This patch must be installed on the VPO Management
Server system, NOT on an VPO Managed Node directly.
Changes will take effect on managed nodes by means of
VPO Software Distribution (using 'Force Update' if
there is already an agent installed on the managed
node). See chapter 2 of the VPO Administrator's
Reference manual for more information.
Be aware that if you redistribute agent software
to MC/ServiceGuard cluster nodes you have to update
the agent registration on these nodes like this:
(this is also documented in the Installation Guide)
# INSTDIR=/opt/OV/bin/OpC/install
# cp /opt/OV/newconfig/OpC/$INSTDIR/itoagt_sg.reg \
$INSTDIR/itoagt.reg
# opcagtreg -add $INSTDIR/itoagt.reg
(B) Patch Deinstallation Instructions
---------------------------------
NOTE: Make sure that no agent of the platform
addressed by this patch is distributed (either
from the ITO Administrator's GUI or from
command line using inst.sh) while running
swremove.
If you are running VPO in a MC/ServiceGuard
installation make sure to mount the shared
disks at the node and only at the node that
had them mounted during patch installation.
Otherwise restoration of the original files
onto the shared disk will fail.
-----End of Document ID: PHSS_28783------------------------------------------
Document ID: PHKL_29080
Date Loaded: 20030710
Title: s700_800 11.00 dyn semphores; big data space; msgmn; msgsnd
Patch Name: PHKL_29080
Patch Description: s700_800 11.00 dyn semphores; big data space; msgmn; msgsnd
Creation Date: 03/06/05
Post Date: 03/07/10
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
OS-Core.CORE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
ProgSupport.C-INC,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_29080: HANG
Application hang.
Category Tags:
defect_repair enhancement general_release critical
halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_29080
Symptoms:
PHKL_29080:
( SR:8606306960 CR:JAGae69995 )
Applications may hang using Sys V message sends.
PHKL_26136:
( SR:8606229781 CR:JAGad98832 )
Can not allocate new semaphores despite enough space being
available.
PHKL_25417:
( SR:8606198599 CR:JAGad67788 )
Can not allocate new semaphores despite enough space being
available.
PHKL_21039:
The maximum number of IPC semaphores per set (SEMMSL) is
presently a hard-coded value with a limit of 2048 in
./sys/sem.h.; it is not a kernel tunable.
PHKL_21518:
( SR: 5003460949 DTS: JAGab15326 )
This is an enhancement for increasing the SysV IPC MSGMNB
message queue capacity from a 16bit(ushort) limit to a
32bit(int) limit for re-compiled applications which are
designed specifically to take advantage of this feature.
The enhancement is contained in three patches; this one
(SysV IPC changes) plus PHKL_21684 (pstat(2) support) and
PHKL_21778 (new tunables range limits, used by SAM).
PHKL_21684 must be installed for this patch to be enabled
and it is strongly advised that all three patches be
installed if this feature is desired. Without installing
this patch and PHKL_21684, this change will have no impact
on the system.
PHKL_20901:
(SR: 8606110995 CR: JAGab83745)
Call to semget() with number of semaphores (nsems) set to
zero correctly returns EINVAL but still allocates semaphore.
PHKL_20229:
( SR: 8606107525 DTS: JAGab77768 )
This patch is one of 8 patches necessary to add support
for the 3 Gb private address space feature.
Defect Description:
PHKL_29080:
( SR:8606306960 CR:JAGae69995 )
If during the usage of message operations, an application
erroneously attempts a message send that is too large,
the application can hang and become unkillable. This can
happen only if the system and the application are setup
in the following manner:
Patches PHKL_26136, PHKL_26008 and PHKL_24487 need to be
installed on the system to allow the tuning of the msgmnb
>65535 (enable big message queues) and msgmax >65535
(allow big individual messages).
The application must be compiled without the
-D__BIGMSGQUEUE_ENABLED option and it attempts to enqueue
a large single message >65535 bytes.
Resolution:
The application hang is due to the code not releasing
the semaphore lock in the error reporting code. The
resolution is to release this lock when reporting the
error.
PHKL_26136:
( SR:8606229781 CR:JAGad98832 )
The space allocated for use by semaphores becomes fragmented
under heavy use of semaphores. Semaphore allocation may be
prevented due to this fragmentation.
Resolution:
System V IPC semaphore allocation has been replaced by full
dynamic allocation, so the memory space for semaphores is
no longer limited to that allocated at boot time.
PHKL_25417:
( SR:8606198599 CR:JAGad67788 )
The space allocated for use by semaphores becomes fragmented
under heavy use of semaphores. Semaphore allocation may be
prevented due to this fragmentation.
Resolution:
The semmap[] structure originally used to allocate a new
semaphore is maintained unless there is no longer a memory
chunk that can fit it due to fragmentation. At that point
the needed chunk is dynamically allocated through malloc().
PHKL_21039:
( SR: 8606126584 DTS: JAGac57149 )
Description:
Enhancement to the IPC semaphore sub-system: changes the
SEMMSL hard-coded value of 2048 to a kernel tunable with a
default value of 2048.
Resolution:
SEMMSL, the hard-coded max number of semaphores per ID, has
been superceded by a new 'semmsl_override' kernel tunable
which will have a minimum (and default) value of 2048. SAM
can increase the value of the new tunable up to a maximum
of 10240. The value of SEMMSL read by pstat() will still
correctly reflect the value set in semmsl_override.
PHKL_21518:
( SR: 5003460949 DTS: JAGab15326 )
This patch, PHKL_21518, is the primary patch of a
three-patch-set which, all together, increase the SysV IPC
MSGMNB message queue capacity from the 16bit(ushort) limit
of 65Kbytes to a 32bit(int) (64Mbyte core-hpux limit)
maximum. The following patches are required:
o PHKL_21518 (this patch): providing the core
functionality for the enhancement
o PHKL_21684, providing pstat(2) support
o PHKL_21778, providing the new tunables limit values for
SAM
The following patch will make maintenence of the
patch-set enhancement possible via SAM:
o PHCO_21187 providing the necessary SAM upgrades
To enable this enhancement after installing all of the
above patches, user applications are required to either
include a #define __BIGMSGQUEUE_ENABLED in every application
or use a -D__BIGMSGQUEUE_ENABLED flag and then re-compile.
Without this patch set, applications are limited to <=64k
of message queue space. With this patch set installed,
the limit is increased to <=64M.
Not installing the PHKL_21518 (sysV_msg.o) patch will
mean that the large message queue enhancement is not
available.
Resolution:
After the above patch set is installed, the following
guidelines, rules and issues will apply:
Note; in this context:
o 'small-queue' refers queues <=64Kbytes
o 'big-queue' refers queues >64Kbytes
o 'patch-set' refers to at least the minimum patch
set of PHKL_21518 plus PHKL_21684
o Old 'small-queue' apps will run unaffected whether
they are re-compiled or not.
o New 'big-queue' apps can ignore the patch and run
with the old 'small-queue' model and remain unaffected
by the patches
Application guidelines:
-----------------------
o Read all applicable text in /usr/include/sys/ipc.h,
/usr/include/sys/msg.h and the patch documents
o New 'big-queue' apps can enable 32bit queues by
#define __BIGMSGQUEUE_ENABLED PRIOR to ipc.h and
msg.h #includes -OR- use -D__BIGMSGQUEUE_ENABLED
when compiling
o If an application attempts to use message queues larger
than 64K (by defining __BIGMSGQUEUE_ENABLED) and the
PHKL_21684 (pstat.o) patch is missing, an EINVAL error
code will be returned (from msgget(2)) and a message
will be placed into the system log (just on first
occurrence).
o Messages can be passed between new 'big-queue' apps
and old 'small-queue' apps but with some restrictions
o If a new 'big-queue' app (as root) expands its queue
from less-than max ushort [created as a 'small-queue']
to greater-than maxushort, that queue will then
automatically be re-tagged as a 'big-queue'.
o Old apps using msgctl(IPC_STAT) will report msg_qbytes
and msg_cbytes as 'full' for any real value of
msg_qbytes/msg_cbytes => max ushort; thus the
msgctl(IPC_STAT) result can 'under-report' msg_qbytes
and/or msg_cbytes. However, pstat results will always
correctly report msg_cbytes. It is not known how apps
may interpret this condition.
o Applications using queues >64k may misbehave where that
queue is used in common with a client or other
application that was not re-compiled with the #define
__BIGMSGQUEUE_ENABLED.
o There is no effect on any program if the admin keeps
the max queue size <=64K. Even where the admin
configures the message queue size >64K, there is no
effect as long as no programs sharing a common message
queue have been recompiled with the special symbol
__BIGMSGQUEUE_ENABLED.
o A program compiled with __BIGMSGQUEUE_ENABLED defined
(and the patch-set installed) which is later executed on
a system without the patch-set may:
o fail a msgget(IPC_CREAT) with errno set to ENOENT
o or succeed in the msgget() if the queue already
exists, but it will not grow beyond MSGMNB/64K in size
or return zero for queue sizes from msgctl(IPC_STAT)
o or set the queue size via msgctl(IPC_SET) to some
arbitrary size (<=64K) because the new fields were
not initialized int the old structure.
o The "GROUP", "CBYTES", "QNUM" and "QBYTES" fields listed
by the 'ipcs' command may "run together" when the queue
size exceeds 999,999
PHKL_20901:
(SR: 8606110995 CR: JAGab83745)
An uninitialized variable (sem_perm.mode) caused the
semaphore to still remain allocated after calling procedure
ipcgetperm().
Resolution:
This variable is now correctly being reset to 0 after
calling ipcgetperm().
PHKL_20229:
( SR: 8606107525 DTS: JAGab77768 )
This is one of 8 patches necessary to add support for the
3 Gb private address space feature. This feature allows a
process to have a private 3rd quadrant (normally the 3rd
quadrant, which is a 1 Gb range of address space from
0x80000000 to 0xC0000000, is used for shared objects). The
chatr command must be used to enable this feature for an
executable (chatr +q3p enable <a.out>). Note that this
feature is only enabled for 32 bit processes running on the
64 bit version of HP-UX.
The other 7 patches necessary to enable this feature are
PHKL_20222, PHKL_20223, PHKL_20224, PHKL_20225, PHKL_20226,
PHKL_20227 and PHKL_20228. Each patch may be installed
independently of the others - if enabling the 3 Gb private
address space feature is not desired. If fewer than all
8 patches are installed, the 3 Gb private address space
feature will not be enabled. The code in this patch that
is part of this feature will not have any impact on the
system until all 8 patches are installed.
Resolution:
A subset of the code to support the 3 Gb private address
space feature was added. When all 8 patches are installed
the following code changes to support this feature will
have been added:
1) Code to recognize the request for a private 3rd
quadrant (Q3) during exec() of an executable.
An executable that requests a private 3rd
quadrant will be referred to as a q3p process
below.
2) Code to prevent allocation of shared objects
in q3p processes.
3) Code to allow data to extend over the 2nd/3rd
quadrant boundary for q3p processes.
4) Code to put the stack for the primary thread
in the 3rd quadrant for q3p processes.
5) Code to map a shared library into the private
address space if there is no more room in the
4th shared quadrant for q3p processes.
Enhancement:
No (superseded patches contained enhancements)
PHKL_29080:
Enhancements were delivered in a patch this one has
superseded. Please review the Defect Description
text for more information.
SR:
5003460949 8606107525 8606110995 8606126584 8606198599
8606229781 8606306960
Patch Files:
OS-Core.CORE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/conf/h/ipc.h
/usr/conf/h/msg.h
ProgSupport.C-INC,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/include/sys/ipc.h
/usr/include/sys/msg.h
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libhp-ux.a(sysV_ipc.o)
/usr/conf/lib/libhp-ux.a(sysV_msg.o)
/usr/conf/lib/libhp-ux.a(sysV_sem.o)
/usr/conf/lib/libhp-ux.a(sysV_shm.o)
OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/master.d/sysvipc-tune
/usr/conf/space.h.d/sysvipc-tune.h
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libhp-ux.a(sysV_ipc.o)
/usr/conf/lib/libhp-ux.a(sysV_msg.o)
/usr/conf/lib/libhp-ux.a(sysV_sem.o)
/usr/conf/lib/libhp-ux.a(sysV_shm.o)
OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/master.d/sysvipc-tune
/usr/conf/space.h.d/sysvipc-tune.h
what(1) Output:
OS-Core.CORE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/conf/h/ipc.h:
ipc.h $Date: 2000/06/05 13:48:46 $Revision: r11ros/4
PATCH_11.00 (PHKL_21518) MSGMNB
/usr/conf/h/msg.h:
msg.h $Date: 2000/06/22 10:02:44 $Revision: r11ros/4
PATCH_11.00 (PHKL_21518) MSGMNB
ProgSupport.C-INC,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/include/sys/ipc.h:
ipc.h $Date: 2000/06/05 13:48:46 $Revision: r11ros/4
PATCH_11.00 (PHKL_21518) MSGMNB
/usr/include/sys/msg.h:
msg.h $Date: 2000/06/22 10:02:44 $Revision: r11ros/4
PATCH_11.00 (PHKL_21518) MSGMNB
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libhp-ux.a(sysV_ipc.o):
sysV_ipc.c $Date: 2000/05/26 14:29:08 $Revision: r11
ros/2 PATCH_11.00 (PHKL_21518) MSGMNB
/usr/conf/lib/libhp-ux.a(sysV_msg.o):
sysV_msg.c $Date: 2003/05/29 13:22:11 $Revision: r11
ros/9 PATCH_11.00(PHKL_29080)
/usr/conf/lib/libhp-ux.a(sysV_sem.o):
sysV_sem.c $Date: 2002/01/18 15:11:40 $Revision: r11
ros/11 PATCH_11.00 (PHKL_26136)
/usr/conf/lib/libhp-ux.a(sysV_shm.o):
sysV_shm.c $Date: 2000/06/05 13:48:46 $Revision: r11
ros/7 PATCH_11.00 (PHKL_21518) MSGMNB
OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/master.d/sysvipc-tune:
sysvipc-tune $Date: 2000/09/13 17:03:15 $Revision: r
11ros/1 PATCH_11.00 (PHKL_21039)
/usr/conf/space.h.d/sysvipc-tune.h:
sysvipc-tune.h $Date: 2000/09/13 17:03:15 $Revision:
r11ros/1 PATCH_11.00 (PHKL_21039)
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libhp-ux.a(sysV_ipc.o):
sysV_ipc.c $Date: 2000/05/26 14:29:08 $Revision: r11
ros/2 PATCH_11.00 (PHKL_21518) MSGMNB
/usr/conf/lib/libhp-ux.a(sysV_msg.o):
sysV_msg.c $Date: 2003/05/29 13:22:11 $Revision: r11
ros/9 PATCH_11.00(PHKL_29080)
/usr/conf/lib/libhp-ux.a(sysV_sem.o):
sysV_sem.c $Date: 2002/01/18 15:11:40 $Revision: r11
ros/11 PATCH_11.00 (PHKL_26136)
/usr/conf/lib/libhp-ux.a(sysV_shm.o):
sysV_shm.c $Date: 2000/06/05 13:48:46 $Revision: r11
ros/7 PATCH_11.00 (PHKL_21518) MSGMNB
OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/master.d/sysvipc-tune:
sysvipc-tune $Date: 2000/09/13 17:03:15 $Revision: r
11ros/1 PATCH_11.00 (PHKL_21039)
/usr/conf/space.h.d/sysvipc-tune.h:
sysvipc-tune.h $Date: 2000/09/13 17:03:15 $Revision:
r11ros/1 PATCH_11.00 (PHKL_21039)
cksum(1) Output:
OS-Core.CORE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
1417744864 5980 /usr/conf/h/ipc.h
1462845435 9015 /usr/conf/h/msg.h
ProgSupport.C-INC,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
1417744864 5980 /usr/include/sys/ipc.h
1462845435 9015 /usr/include/sys/msg.h
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
3343021987 1748 /usr/conf/lib/libhp-ux.a(sysV_ipc.o)
3746105385 15880 /usr/conf/lib/libhp-ux.a(sysV_msg.o)
1361464872 21220 /usr/conf/lib/libhp-ux.a(sysV_sem.o)
2328942000 11048 /usr/conf/lib/libhp-ux.a(sysV_shm.o)
OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
1530785713 349 /usr/conf/master.d/sysvipc-tune
1858305369 246 /usr/conf/space.h.d/sysvipc-tune.h
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
2688313537 3720 /usr/conf/lib/libhp-ux.a(sysV_ipc.o)
2708463588 41888 /usr/conf/lib/libhp-ux.a(sysV_msg.o)
293780355 48648 /usr/conf/lib/libhp-ux.a(sysV_sem.o)
4076208488 26728 /usr/conf/lib/libhp-ux.a(sysV_shm.o)
OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
1530785713 349 /usr/conf/master.d/sysvipc-tune
1858305369 246 /usr/conf/space.h.d/sysvipc-tune.h
Patch Conflicts: None
Patch Dependencies:
s700: 11.00: PHKL_18543
s800: 11.00: PHKL_18543
Hardware Dependencies: None
Other Dependencies:
PHKL_21518: PHKL_21684, PHKL_21778, and PHKL_21518 together
provide an enhancement to increase the SysV IPC MSGMNB
message queue capacity. To enable the enhancement, both
PHKL_21684 and PHKL_21518 must be installed, and PHKL_21778
is required if SAM support is desired to modify system
tunables. Each may be installed independently of the
others.
Supersedes:
PHKL_20901 PHKL_20229 PHKL_26136 PHKL_25417 PHKL_21518 PHKL_21039
Equivalent Patches:
PHKL_29070:
s700: 11.11
s800: 11.11
Patch Package Size: 150 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHKL_29080
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_29080.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_29080. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_29080.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_29080.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_29080.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
Max number of semas per ID
--------------------------
For the PHKL_21039 patch, SAM is used to change the
maximum number of semas per ID (previously SEMMSL) by
adjusting the new 'semmsl_override' tunable. The SEMMNS
(max number of semas in the system) tunable value MUST be
greater than or equal to 'semmsl_override' otherwise
applications will be limited to the smaller of the two
values.
SEMMNS MAX # of semas in the system [must be >= SEMMSL]
SEMMSL MAX # of semas per ID [presently 64 IDs MAX]
To make the semas-per-ID (previously SEMMSL) adjustable,
the 'semmsl_override' kernel tunable has been added. The
value can be set and adjusted up from (the minimum and
default value of 2048) to an arbitrary maximum of 10240
(0x2800). This global 'semmsl_override', is the only way
to adjust the maximum number of semas per ID and the
changes take effect only after re-boot.
Because a new tunable is being added, it is highly
reccommended that you install patch PHCO_19047, which has
the necessary SAM upgrades. Without the upgrades, SAM
will still be aware of the new tunable but will not be
aware of the new range limitations for that tunable.
Therefore, SAM will show a warning message to this effect
when attempting to access the tunable. With PHCO_19047
installed, SAM will automatically update the range values.
The tunable can still be set by SAM using values within
the range limits specified in the
/usr/conf/master.d/sysvipc-tune file but it is not the
reccommended procedure as SAM will not perform the
necessary checks and SAM will not guarantee a successful
kernel creation if the tunable is modified.
SysV IPC MSGMNB message queue capacity
--------------------------------------
o The PHKL_21518 (sysV_msg.o) (or superseding) patch
and the pstat.o patch (PHKL_21684 or superseding patch)
MUST BOTH be installed on the system together to enable
the MSGMNB enhancement.
o It is also highly recommended that patches PHKL_21778
(core-hpux) PHCO_21187 (with the necessary SAM
enhancements) also be installed.
o Installing only the PHKL_21778 (core-hpux) patch
will allow the admin to set MSGMNB >64k but the change
will have no effect as the kernel will hard-limit the
value to 64k.
o Applications compiled with __BIGMSGQUEUE_ENABLED will
not run on systems which do not have the appropriate
patches installed.
o Not having either the PHKL_21518 (sysV_msg.o) patch or
the PHKL_21684 (pstat.o) patch installed means that
applications compiled with the #define
__BIGMSGQUEUE_ENABLED may not run or may not run
correctly.
o Not installing PHKL_21778 (core-hpux) and PHCO_21187
(SAM) patches will make it more difficult to adjust the
kernel message tunables.
o If an application attempts to use message queues larger
than 64K (by defining __BIGMSGQUEUE_ENABLED) and the
PHKL_21684 (pstat.o) companion patch is missing, an
EINVAL error code will be returned (from msgget(2))
and a message will be placed into the system log (but
only on the first occurrence).
Kernel Tunables:
----------------
o Follow the procedures below for setting the kernel
tunables and tunable ranges using SAM.
o Follow these guidelines for setting new message queue
kernel tunables:
o MSGMNB [max number of bytes per queue]
Set >= the largest queue required. If single large
messages are expected, also set >= the largest single
message expected.
o MSGMAX [max message size in bytes]
Set <= MSGMNB dependent on the need to use single
large messages which may fill the queue.
o MSGTQL [max number of message headers]
Set >= the largest number of messages expected.
o MSGSSZ [number of bytes in one "segment"]
MSGSEG [number of segments]
MSGSSZ*MSGSEG [total message storage space]
o Set MSGSSZ*MSGSEG >= at least to the maximum a
single large message queue can hold.
o If multiple large queues are expected, that
will need to be factored in.
o MSGSSZ is the "granularity" for message storage.
If MSGSSZ=256 then a 257-byte message will
consume two segments.
o Note that MSGSEG must be < 32768 so that if 32M
were allocated, the segment size MSGSSZ would
need to be set to 1K bytes.
Updating MSGMNB/MSGMAX Tunable Ranges:
--------------------------------------
Presently, the "range" values in master/core-hpux will
prevent users of SAM from configuring MSGMNB and MSGMAX to
>64K. In order to allow larger queues, the admin should
install PHCO_21187 (SAM) patch as a companion to
PHKL_21778 (core-hpux) which will automatically update
SAM's range values. If that is not desired, the admin can
follow the following special procedure outlined below:
SAM, as installed on customer systems, may prevent the
administrator from selecting queue (and message) sizes in
excess of 64Kbytes. This is due to the range values in
/usr/conf/master.d/core-hpux or SAM's "params.tx" file
(significant in older versions of SAM).
We are providing the PHKL_21778 (core-hpux) patch for the
"core-hpux" files (for both 32bit and 64bit kernels).
However, due to SAM version differences, the customer has
several procedural options, as described below.
o If installation of the PHKL_21778 (core-hpux) patch to
/usr/conf/master.d/core-hpux is desired, follow
these steps:
make a backup copy of /usr/conf/master.d/core-hpux
install the patch
inspect changes to /usr/conf/master.d/core-hpux
o Note that installation of this patch will overwrite
any local changes, these should be merged back in.
o This particular patch will make the following changes:
Old:
*range msgmax<=64*1024
*range msgmnb<=64*1024
New:
*range msgmax<=64*1024*1024
*range msgmnb<=64*1024*1024
o Any other changes are due to: having not been
previously up-to-date with superseded patches to
this file; superseding patches to this file; or
prior local changes to this file.
o Once statisfied with /usr/conf/master.d/core-hpux,
perform one of the following procedures.
a) If the PHCO_21187 (SAM) patch is installed, the
procedure is:
- make backup copy of /var/sam/boot.config
- execute /usr/sam/lbin/getkinfo -b
- inspect changes made to /var/sam/boot.config
o The "KC_PARAM_MAX" values for "msgmax" and
"msgmnb" should have change from 65536 (64Kbytes)
to 67108863 (64Mbytes). If there are any other
changes to this file, they represent additional
core-hpux changes from superseding patches,
or changes which from superseded patches,
but not rolled into SAM.
o Start SAM, change MSGMAX/MSGMNB kernel parameters
to desired values. These values will depend upon
the application's needs. You may also need to
adjust the MSGSEG/MSGSSZ parameters to allocate
more memory for total message storage (the upper
limits for these do not change). Then regenerate
and reboot the kernel in the usual manner.
or:
b) If the PHCO_21187 (SAM) patch is not installed,
install it then follow procedure for "a".
or:
c) If installing the PHCO_21187 (SAM) patch is not
desired, first:
o Edit the /usr/sam/lib/kc/params.tx file to change
the upper limits:
Old:
msgmax:65536:0:Message:8192:Message Max Size...
msgmnb:0x10000:0:Message:16384:Max Number ...
New:
msgmax:67108863:0:Message:8192:Message Max Size...
msgmnb:67108863:0:Message:16384:Max Number...
o Do not change any other message queue parameters.
o After editing, follow the procedure under "a", as
if the patch was installed.
o If installation of the PHKL_21778 (core-hpux) patch is
not desired (despite the recommendation that it be
installed), then the administrator will need to edit
/usr/conf/master.d/core-hpux directly to change the
upper limits:
Old:
*range msgmax<=64*1024
*range msgmnb<=64*1024
New:
*range msgmax<=64*1024*1024
*range msgmnb<=64*1024*1024
o Once this is done, follow one of the above
procedures, "a", "b", or "c", as appropriate.
o If SAM is not the means for kernel configuration at
the site, the PHKL_21778 (core-hpux) patch (or editing
core-hpux may not be needed. In this case the
tunables for MSGMNB, MSGMAX, MSGSEG, and MSGSSZ should
be modified, and the kernel regenerated and rebooted,
in the usual manner for the site. (For example: edit
the /stand/system file then build a new kernel via
'mk_kernel -s /stand/system'). The maximum for MSGMNB
and MSGMAX is now 67108863 rather than 65536.
3GB Private Address Space
-------------------------
This patch contains part of the enhancement to enable the
3 Gb private address space feature. It is one of 8
patches. The other 7 patches necessary to enable this
feature are PHKL_20222, PHKL_20223, PHKL_20224,
PHKL_20225, PHKL_20226, PHKL_20227 and PHKL_20228. Each
patch may be installed independently of the others - if
enabling the 3 Gb private address space feature is not
desired. If fewer than all 8 patches are installed, the 3
Gb private address space feature will not be enabled. The
code in this patch that is part of this feature will not
have any impact on the system until all 8 patches are
installed.
In order to be able to use this feature you will need to
reconfigure the kernel with a larger value for the kernel
configurable variable "maxdsiz". In order to do this with
SAM, you will also need to install patch PHKL_20174.
Without PHKL_20174 installed SAM will not allow maxdsiz to
exceed ~1.9 Gb. Note that if PHKL_20174 is not installed
it is still possible to manually configure a kernel with a
larger value of maxdsiz (up to 3 Gb) using config(1M).
-----End of Document ID: PHKL_29080------------------------------------------
Document ID: PHKL_29070
Date Loaded: 20030710
Title: s700_800 11.11 application hangs using msg queues
Patch Name: PHKL_29070
Patch Description: s700_800 11.11 application hangs using msg queues
Creation Date: 03/06/05
Post Date: 03/07/10
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_29070: HANG
Multi-threaded application hang.
Category Tags:
defect_repair general_release critical halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_29070
Symptoms:
PHKL_29070:
( SR:8606306961 CR:JAGae69996 )
Applications may hang using Sys V message sends.
Defect Description:
PHKL_29070:
( SR:8606306961 CR:JAGae69996 )
If during the usage of message operations, an application
erroneously attempts a message send that is too large,
the application can hang and become unkillable. This can
happen only if the system and the application are setup
in the following manner:
The system is tuned such that msgmnb >65535 (enable big
message queues) and msgmax >65535 (allow big individual
messages).
The application must be compiled without the
-D__BIGMSGQUEUE_ENABLED option and it attempts to enqueue
a large single message >65535 bytes.
Resolution:
Release the semaphore lock in the error reporting code.
Enhancement:
No
SR:
8606306961
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libpm.a(sysV_msg.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libpm.a(sysV_msg.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libpm.a(sysV_msg.o):
sysV_msg.c $Date: 2003/05/05 14:37:21 $Revision: r11
.11/1 PATCH_11.11 (PHKL_29070)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libpm.a(sysV_msg.o):
sysV_msg.c $Date: 2003/05/05 14:37:21 $Revision: r11
.11/1 PATCH_11.11 (PHKL_29070)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
286338991 14824 /usr/conf/lib/libpm.a(sysV_msg.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
2566199761 43552 /usr/conf/lib/libpm.a(sysV_msg.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHKL_29080:
s700: 11.00
s800: 11.00
Patch Package Size: 40 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHKL_29070
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_29070.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_29070. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_29070.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_29070.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_29070.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHKL_29070------------------------------------------
Document ID: PHCO_29236
Date Loaded: 20030709
Title: s700_800 11.22 libc cumulative patch
Patch Name: PHCO_29236
Patch Description: s700_800 11.22 libc cumulative patch
Creation Date: 03/06/04
Post Date: 03/07/09
Hardware Platforms - OS Releases:
s700: 11.22
s800: 11.22
Products: N/A
Filesets:
OS-Core.C-MIN,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP
OS-Core.C-MIN-64ALIB,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP
OS-Core.CORE2-64SLIB,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP
OS-Core.CORE2-SHLIBS,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP
ProgSupport.PROG2-AUX,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
Yes
PHCO_29236: CORRUPTION
Category Tags:
defect_repair general_release critical corruption
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_29236
Symptoms:
PHCO_29236:
( SR:8606296004 CR:JAGae59640 )
strcpy() and strcat() corrupts data when destination
is not 8 byte aligned.
Defect Description:
PHCO_29236:
( SR:8606296004 CR:JAGae59640 )
Using the strcpy() or strcat() function with a destination
address that is not word aligned may result in some
corrupted characters.
Resolution:
strcpy() and strcat() are changed in such a way that
it can handle unaligned addresses.
NOTE: The defect manifests itself only when the
parameter to the destination string points to an
unaligned buffer and an unusual combination of
residual data occurs in the registers used by these
functions. These two conditions rarely occur. In
this scenario strcpy and strcat APIs do not function
as documented. This defect is fixed in the C library
in this patch, PHCO_29236. Applications that are
affected by this defect must be relinked with the
patched library to function correctly.
Enhancement:
No
SR:
8606296004
Patch Files:
OS-Core.C-MIN,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
/usr/lib/hpux32/unix95.o
/usr/lib/hpux32/unix98.o
OS-Core.C-MIN-64ALIB,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
/usr/lib/hpux64/unix95.o
/usr/lib/hpux64/unix98.o
OS-Core.CORE2-64SLIB,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
/usr/lib/hpux64/libc.so.1
OS-Core.CORE2-SHLIBS,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
/usr/lib/hpux32/libc.so.1
/usr/lib/hpux32/libcres.a
/usr/lib/hpux64/libcres.a
ProgSupport.PROG2-AUX,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
/usr/lib/hpux32/libp/libc.so.1
/usr/lib/hpux32/libp/libcres.a
/usr/lib/hpux64/libp/libc.so.1
/usr/lib/hpux64/libp/libcres.a
what(1) Output:
OS-Core.C-MIN,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
/usr/lib/hpux32/unix95.o:
None
/usr/lib/hpux32/unix98.o:
None
OS-Core.C-MIN-64ALIB,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
/usr/lib/hpux64/unix95.o:
None
/usr/lib/hpux64/unix98.o:
None
OS-Core.CORE2-64SLIB,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
/usr/lib/hpux64/libc.so.1:
$ PATCH_11.22/PHCO_29236 Jun 4 2003 00:23:20 $
HP-UX/General Millicode B.11.20.00 (IPF TOT): (MILLI
- 05/01/01)
OS-Core.CORE2-SHLIBS,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
/usr/lib/hpux32/libc.so.1:
$ PATCH_11.22/PHCO_29236 Jun 4 2003 00:18:41 $
HP-UX/General Millicode B.11.20.00 (IPF TOT): (MILLI
- 05/01/01)
/usr/lib/hpux32/libcres.a:
$ PATCH_11.22/PHCO_29236 Jun 4 2003 00:27:58 $
/usr/lib/hpux64/libcres.a:
$ PATCH_11.22/PHCO_29236 Jun 4 2003 00:28:04 $
ProgSupport.PROG2-AUX,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
/usr/lib/hpux32/libp/libc.so.1:
$ PATCH_11.22/PHCO_29236 Jun 4 2003 00:25:24 $
HP-UX/General Millicode B.11.20.00 (IPF TOT): (MILLI
- 05/01/01)
/usr/lib/hpux32/libp/libcres.a:
$ PATCH_11.22/PHCO_29236 Jun 4 2003 00:28:11 $
/usr/lib/hpux64/libp/libc.so.1:
$ PATCH_11.22/PHCO_29236 Jun 4 2003 00:27:26 $
HP-UX/General Millicode B.11.20.00 (IPF TOT): (MILLI
- 05/01/01)
/usr/lib/hpux64/libp/libcres.a:
$ PATCH_11.22/PHCO_29236 Jun 4 2003 00:28:18 $
cksum(1) Output:
OS-Core.C-MIN,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
227069456 1312 /usr/lib/hpux32/unix95.o
3026525948 1312 /usr/lib/hpux32/unix98.o
OS-Core.C-MIN-64ALIB,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
3328448689 1632 /usr/lib/hpux64/unix95.o
2365888115 1632 /usr/lib/hpux64/unix98.o
OS-Core.CORE2-64SLIB,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
3509746509 3843952 /usr/lib/hpux64/libc.so.1
OS-Core.CORE2-SHLIBS,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
3615053654 4105304 /usr/lib/hpux32/libc.so.1
96159891 65138 /usr/lib/hpux32/libcres.a
3828125023 74750 /usr/lib/hpux64/libcres.a
ProgSupport.PROG2-AUX,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
1487956211 4418584 /usr/lib/hpux32/libp/libc.so.1
2208566650 71234 /usr/lib/hpux32/libp/libcres.a
1126562256 3889808 /usr/lib/hpux64/libp/libc.so.1
1585824875 82734 /usr/lib/hpux64/libp/libcres.a
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 5690 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHCO_29236
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_29236.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_29236. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHCO_29236.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_29236.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_29236.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_29236------------------------------------------
Document ID: PHNE_28809
Date Loaded: 20030708
Title: s700_800 11.00 sendmail(1m) 8.9.3 patch
Patch Name: PHNE_28809
Patch Description: s700_800 11.00 sendmail(1m) 8.9.3 patch
Creation Date: 03/06/23
Post Date: 03/07/08
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
InternetSrvcs.INETSVCS-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
No (superseded patches were critical)
PHNE_26304: ABORT
Category Tags:
defect_repair enhancement general_release critical
halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_28809
Symptoms:
PHNE_28809:
SR 8606314706/ CR JAGae77457
1. Information present in manpages delivered with
PHNE_26304 is incorrect.
PHNE_26304:
SR 8606248880/ CR JAGae15277
1. identd terminates on receiving a SIGPIPE signal and
it does not log an appropriate error message in the
syslog file.
SR 8606267547/ CR JAGae31789
2. Sendmail does not log the transient error
message, "Name server timeout" in the log file
while processing the mail queue.
SR 8606280817/ CR JAGae44786
3. Under certain conditions, Sendmail or its
associated utilities may not operate properly.
SR 8606280836/ CR JAGae44803
4. Under certain conditions, Sendmail does not
terminate/restart properly.
SR 8606289291/ CR JAGae53222
5. Under certain conditions, Sendmail does not
process the mail queue properly.
SR 8606295551/ CR JAGae59233
6. In some cases, Sendmail does not parse the mail
headers properly.
SR 8606303975/ CR JAGae67325
7. In some cases, Sendmail does not parse the headers
properly.
SR 8606305629/ CR JAGae68677
8. In some cases, Sendmail relays mails illegally.
PHNE_24419:
SR 8606189011 / CR JAGad58227:
1. When a user searches for aliases using nis+, the search
will fail.
SR 8606194375 / CR JAGad63585:
2. When there are large number of active TCP connections,
'ndd' invoked by identd holds the TCP lock for over a
minute. This causes a Transfer Of Control.
SR 8606213171 / CR JAGad82359:
3. Sendmail can mishandle addresses in "Diagnostic-Code:"
warning message.
SR 8606172226 / CR JAGad41486:
4. /The /etc/mail/aliases file credentials change after
the installation of Sendmail patch.
PHNE_18546:
SR 8606105321 / CR JAGab73332:
1. Upgrade Sendmail-8.8.6 to Sendmail-8.9.3.
SR 1653274639 / CR JAGaa26556:
2. Update documentation in future sendmail patches to
include NIS info.
SR 8606136180 / CR JAGaa27064:
3. expand_alias command fails to expand aliases for hosts
that have MX records but not A or CNAME records.
SR 1653301234 / CR JAGab13472:
4. When sending mail if you accidentally specify a non
existent host, message delivery is deferred.
SR 5003458570 / CR JAGab11180:
5. Subject field of a message having Japanese characters
may be garbled when sent using sendmail.
SR 8606136181 / CR JAGab16315:
6. Error message "unable to qualify my own domain
name (<hostname>) -- using short name" from sendmail
is being displayed on the console if the host name is
not a fully qualified domain name(FQDN).
SR 8606132690 / CR JAGad01838:
7. Sendmail-8.9.3 creates a 10MB file in /var/tmp for
every DB access. This caused performance degradation.
SR 8606124372 / CR JAGac39755:
8. identd does not work on 64 bit HP-UX 11.00
SR 8606127691 / CR JAGac78493:
9. When heavily loaded, Sendmail-8.9.3 exits without any
error or core file.
SR 8606131029 / CR JAGad00187:
10. When DNS server is down, sendmail fails to use
files (/etc/hosts) for host lookup.
SR 1653304592 / CR JAGab16783:
11. Sendmail error 'readqf: cannot open df#: No such
file or directory' problem is seen at times, when
system is heavily loaded.
SR 1653241869 / CR JAGaa26527:
12. Sendmail patch overwrites the link created by
Netscape Mailer when it is installed.
SR 8606102174 / CR JAGab67684:
13. Sendmail start script may refuse to start at boot.
SR 8606105428 / CR JAGab73480:
14. sendmail drops the last destination address in some
cases.
SR 8606127266 / CR JAGac68812:
15. Usage of the -f option of sendmail is wrongly
documented in the sendmail manpage.
SR 8606136331 / CR JAGaa26967:
16. ER : Default sendmail aliases database should have
'ftp-bugs' aliased to root.
SR 8606105137 / CR JAGab73015:
17. newaliases/makemap commands generate a huge db file
on 'hfs' file system with 64kb Block size.
SR 8606126031 / CR JAGac47219:
18. gen_cf script option 1, wrongly sets promiscuous
relay in the sendmail configuration file generated.
SR 5003396077 / CR JAGaa26922:
19. ER:Request to add LDAP functionality to sendmail.
SR 8606137834 / CR JAGad06991:
20. Sendmail-8.9.3 drops the MIME encoding information line
in the message when sent to openmail.
PHNE_17190:
1. sendmail: When processing multi-part mime message
sendmail generates core.
2. sendmail does not handle properly the value of
"Errors-To:" variable.
3. sendmail does not build sendmail.cw properly.
4. UUCP problem with ISP because of delivery agent.
5. expand_alias fails if PrivacyOptions is set to
needexpnhelo.
6. Maximum number of header lines should be configurable.
7. sendmail is optimized to accept connections efficiently.
PHNE_16852:
1. "Bad System Call" with a command used in a Sendmail
patch script.
PHNE_15509:
1. Patch outputs extraneous message within
install log.
2. Patch preinstall script gets "bad system call" error.
PHNE_13947:
1. Sendmail does not support /etc/hosts.smtp file.
2. Sendmail does not support UUCP relay.
3. Rejected mail cannot be saved anywhere; messages
appear on console.
4. Sendmail gives error if NIS is not installed.
PHNE_10495:
1. Upgrade sendmail(1m) to 8.8.6.
2. Errors in openmail-specific rules of ruleset 0 of
sendmail.cf
3. In the absence of /etc/nsswitch.conf, sendmail can't
send external mails, sendmail does not use DNS MX
records and sendmail causes NIS aliases to fail.
4. Received sendmail errors during initial boot, sendmail
panics.
5. killsm/sendmail start does not parse ps correctly, may
kill other processes.
6. Sendmail has problems with DBM files.
7. Sendmail won't deliver mail to file, wrongly thinks
shell is bad.
8. Sendmail ignores lines after "." when sent by dtmail.
9. Sendmail has bad lines in sendmail.cf file.
10. Sendmail has different behavior with aliased hostnames.
11. Support the old functionality of DL macro in 8.8.6
sendmail.
12. Fix interoperability problem of sendmail-8.8.6 with
Openmail.
13. killsm script (sendmail) has a missing rval statement
and prints duplicate messages.
14. improve detection of sendmail already running in
/sbin/init.d/sendmail.
15. Sendmail 8.8.6 does not send mail to localdomain only,
but to relay.
16. Sendmail has problems with UUCP rules and spaces.
Defect Description:
PHNE_28809:
SR 8606314706/ CR JAGae77457
1. The patch PHNE_26304 contains an incorrect version
of manpages.
Resolution:
The correct version of the manpages are included
in the current patch PHNE_28809.
PHNE_26304:
SR 8606248880/ CR JAGae15277
1. identd does not contain any specific signal handler
to handle the signal SIGPIPE and identd terminates,
as the default behavior of SIGPIPE is to terminate
the process.
Resolution:
A signal handler has now been included in identd to
handle the signal SIGPIPE. Hence, identd terminates
with an appropriate error message logged as
LOG_DEBUG in the syslog file as:
"SIGPIPE triggered, exiting"
The error message is logged only if the `-l' option
is given as an argument to identd.
SR 8606267547/ CR JAGae31789
2. The transient error message "Name Server Timeout"
occurs when Sendmail is unable to resolve the host
using the name service. The error message is only
displayed on the terminal, and is not logged in the
default syslog file /var/adm/syslog/mail.log.
Resolution:
Sendmail now logs the transient error messages in the
default syslog file, /var/adm/syslog/mail.log. These
error messages contain the status information as
specified below:
stat= "Transient parse error -- message queued for
future delivery"
An option "AlertTmpFailure" is added in the /usr/
newconfig/etc/mail/sendmail.cf file to log the
transient error messages as LOG_ALERT messages. For
more information, refer to the sendmail(1M) manpage.
To make the sendmail configuration file
compatible with lower versions of this patch,
the "AlertTmpFailure" option must be removed or
commented in the sendmail.cf file.
SR 8606280817/ CR JAGae44786
3. Under certain conditions, Sendmail or its
associated utilities may not operate properly.
Resolution:
Code has now been modified to fix the problem.
SR 8606280836/ CR JAGae44803
4. Due to a race condition, Sendmail does not
terminate/restart properly.
Resolution:
Code has now been modified to fix the problem.
SR 8606289291/ CR JAGae53222
5. Under certain conditions, Sendmail does not
process the mail queue properly.
Resolution:
Use /usr/newconfig/etc/mail/sendmail.cf as the
base configuration file (/etc/mail/sendmail.cf)
with site-specific changes as required and
restart the sendmail daemon.
SR 8606295551/ CR JAGae59233
6. In some cases, sendmail does not parse the mail
headers properly.
Resolution :
The code has now been modified to parse the mail
headers properly.
SR 8606303975/ CR JAGae67325
7. In some cases, sendmail does not parse the headers
properly.
Resolution :
The code has now been modified to parse the headers
properly.
SR 8606305629/ CR JAGae68677
8. Sendmail illegally relays mails due to the specially
quoted recipient address.
Resolution:
A new ruleset has now been added in the configuration
file /usr/newconfig/etc/mail/sendmail.cf to remove the
quotes from the recipient address, thus disallowing
illegal relaying of mails. Use /usr/newconfig/etc/mail/
sendmail.cf as base configuration file (/etc/mail/
sendmail.cf) with site-specific changes as required
and restart the sendmail daemon.
PHNE_24419:
SR 8606189011 / CR JAGad58227:
1. In sendmail-8.9.3, an alias search using nis+ fails
due to incorrect compilation flag.
Resolution:
Sendmail-8.9.3 is now built with an appropriate
compilation flag.
SR 8606194375 / JAGad63585:
2. identd uses 'ndd' to get the credentials of the remote
owner of a TCP connection which causes a TOC.
Resolution:
The identd code has been modified to use a new ioctl()
command instead of 'ndd'.This patch has a dependency
on the ARPA transport patch PHNE_24715.
SR 8606213171 / CR JAGad82359:
3. Sendmail can mishandle addresses in "Diagnostic-Code:"
warning message.
Resolution:
The code has been modified to resolve this problem.
SR 8606172226 / CR JAGad41486:
4. After the installation of the patch, a backup of the
file /etc/mail/aliases is taken and the processing is
done on the backup file. After the processing, the
backup file is moved back to the /etc/mail directory.
During this process of moving the /etc/mail/aliases
file to a backup directory and back to the original
directory, the credentials of the /etc/mail/aliases
file are changed.
Resolution:
The installation script has been modified to retain the
original credentials of the /etc/mail/aliases file.
PHNE_18546:
SR 8606105321 / CR JAGab73332:
1. Upgrade Sendmail-8.8.6 to Sendmail-8.9.3.
Resolution: Upgraded to the new version.
SR 1653274639 / CR JAGaa26556:
2. Update documentation in sendmail patches
to include NIS information.
Resolution: Special Installation Instructions in the
patch has the information to configure sendmail if
NIS is used for aliases.
SR 8606136180 / CR JAGaa27064:
3. expand_alias script tries to telnet to the host given
as input to it at port 25. telnet fails to connect to
the given hostname if the host does not have either an
A or CNAME record. Hence expand_alias fails.
Resolution: expand_alias script has been modified to
get the mailserver name for the given host using
nslookup and then the aliases are expanded at that
mailserver.
SR 1653301234 / CR JAGab13472:
4. When gethostbyname() call fails, h_errno gets set.
This h_error has to be checked to either defer or
report failure immediately. However, instead of
checking the h_errno the errno was being used to
check the failure. The errno was getting set to
different error and hence the mail was getting
deferred.
Resolution: This is now corrected and the h_errno is
being checked.
SR 5003458570 / CR JAGab11180:
5. Sendmail when scanning the Subject field used to skip
all those characters whose value was in the range
0x80 - 0x9f. Because of this, subject field used to
get garbled for Japanese characters.
Resolution: A new option "EightBitHeader=TRUE" has to be
added to the configuration file to avoid this subject
field garbling.
SR 8606136181 / CR JAGab16315:
6. Sendmail used to log this error message to syslog at
LOG_ALERT level if the host name was not a fully
qualified one.
Resolution: The error message is now logged at LOG_INFO
level.
SR 8606132690 / CR JAGad01838:
7. Sendmail creates a file /var/tmp/#pid of 10MB for
every db file access and removes it after the access.
DB uses this file for memory mapping. If lot of
sendmail process are running simultaneously, then
/var/tmp gets filled up.
Resolution: Sendmail now uses a new version of DB,
db-3.0.55 which does not create a file in /var/tmp
for memory mapping.
SR 8606124372 / CR JAGac39755:
8. identd reads some of the needed structures from the
memory, depending on the size of the structure. When
identd is compiled in a 32bit environment and the same
binary is used on a 64 bit m/c the size of those
memory structures will vary and hence it fails in a
64 bit m/c.
Resolution: identd is now interfaced with a new library
libp4 which provides calls to get the structures from
the memory. These calls are independent of 32bit or
64bit architecture.
SR 8606127691 / CR JAGac78493:
9. When sendmail is highly loaded, the memory of the
proc_list could get removed in signal handler. This
used to leave the memory map in an inconsistent state.
This led to sendmail exiting without any error message
or core file
Resolution: Now the memory of a previously filled slot
is freed only when we are adding a new process,
to the process list.
SR 8606131029 / CR JAGad00187:
10. When doing host lookups, if the DNS server is down,
sendmail is not continuing its lookup in /etc/hosts,
even though the policy is mentioned in the switch
file. This problem is occurring because there is no
proper check of the h_error number resulting in a
different code path.
Resolution: Error check is done properly.
SR 1653304592 / CR JAGab16783:
11. If two sendmail queue processes work on the same
message on a queue at same time, it gives the
error message "Error: readqf: cannot open df#: No
such file or directory".
Resolution: In the above condition a pointer
initialization was not being done. This is now taken
care in the code.
SR 1653241869 / CR JAGaa26527:
12. When installing sendmail there was no check to see
whether there is a link from sendmail binary to some
other file. So when sendmail is installed in this
situation, it overwrites the other file.
Resolution: Now check is done in the patch script. It
gives an error message during the installation
of the patch, it the link exists and stops the
installation. The user needs to manually remove the
softlink and then start the installation again.
This will avoid overwriting of the linked file.
SR 8606102174 / CR JAGab67684:
13. In the sendmail startup script, there was no proper
check to see if the pid present in the
/etc/mail/sendmail.pid file is that of the running
sendmail process. Due to this sendmail was not getting
started.
Resolution: When checking for the pid, we now check
whether this pid really corresponds to the sendmail
process.
SR 8606105428 / CR JAGab73480:
14. When the recipient addresses sent to the same system
as one SMTP session, summed up to 512 bytes, then the
last address in the list was getting removed. This
was happening due to the improper boundary checking.
Resolution: The boundary condition are now taken care
off.
SR 8606127266 / CR JAGac68812:
15. The man page documentation for -f option was wrong.
Resolution: The manpage is properly updated.
SR 8606136331 / CR JAGaa26967:
16. There was a request to add a new alias 'ftp-bugs',
in the default aliases file.
Resolution: Added a new alias 'ftp-bugs' aliased to
root in the default alias file.
SR 8606105137 / CR JAGab73015:
17. The db file created by newaliases and makemap commands
on a 'hfs' file system with 64KB block size, is huge.
Resolution: With the new DB version, the db file
generated is small.
SR 8606126031 / CR JAGac47219:
18. The gen_cf script's option 1 was setting promiscuous
relay while the option read as "generate sendmail.cf
with NO relay on".
Resolution: Added a new option for relay ON and
relay OFF and removed the ambiguity.
SR 5003396077 / CR JAGaa26922:
19. There was a request for support of LDAP functionality
in sendmail.
Resolution: LDAP is supported in this new version.
SR 8606137834 / CR JAGad06991:
20. When sending a MIME encoded message to openmail, in
some of the messages the Content-Transfer-Encoding line
is getting dropped. The line was dropped due to lack of
proper checking of the flag which decides
to put the CTE line.
Resolution: Added the proper check to the flag.
PHNE_17190:
1. When processing multi-part mime message sendmail
generates core. The problem occurs because the variable
mstate was not set properly.
2. When a mail needs to be send to an address specified in
"Errors-To:" field and if the user is at a remote host,
then the mail was not sent to the remote user. The
reason was the UseErrorsTo flag was not set properly.
3. sendmail.cw file is created by reading
/etc/resolv.conf. The existing script sometimes
wrongly parsed /etc/resolv.conf file and in those cases
the sendmail.cw file created was not proper.
4. If the address is of type userhost.com and passed to
smarthost via UUCP it was not able to send. This is
because there was no rule set to process such type of
address for smart host.
5. expand_alias script was not handling the "HELO" smtp
command. The script was modified to handle this
command too.
6. Maximum number of header lines should be configurable.
7. sendmail is optimized to accept connections efficiently.
PHNE_16852:
1. Sendmail install script should use /sbin/sh shell
which it is not using currently.
PHNE_15509:
1. The messages which go to the log should have
consistent format and follow guidelines.
2. Patch scripts should use only those commands
which are available in /usr/sbin.
PHNE_13947:
1. Functionality of /etc/hosts.smtp file is absent in
sendmail-8.8.6 which was present in sendmail-5.65.
2. A UUCP relay rule which was present in
sendmail-8.7.6 is absent in sendmail-8.8.6.
3. Sendmail sends error messages to console when it fails
to save the rejected mail.
4. Sendmail by default uses NIS for alias lookup in the
absence of /etc/nsswitch.conf file and if NIS is not
installed it gives error.
PHNE_10495:
1. Upgrade sendmail(1m) to 8.8.6.
2. The openmail-specific rules inside ruleset 0 have spaces
separating the LHS of the rules from the RHS instead of
TABS. This is syntactically incorrect.
3. When /etc/nsswitch.conf is not present on the system,
the hostname lookup and alias lookup were using files
by default. This was causing problems in a DNS or
NIS environment.
4. Sendmail depended on the transition link
"/usr/tmp->/var/tmp" and system did not contain this
transition link. This caused the savemail panic as
bounced mail could not be saved to /usr/tmp/dead.letter.
5. killsm/sendmail start does not parse ps correctly, may
kill other processes.
6. Sendmail was not using the libdbm library which comes
along with the HP-UX but was using libdbm library from
the public domain.
7. A bug in chownsafe function (conf.c) caused failure of
mail delivery to an alias defined as
<alias>: :include:<mailing-list>
8. A bug in collect function in collect.c caused ignoring
of lines after "." when sent by dtmail.
9. Lines within sendmail.cf relating to OpenMail and X.400
have become space-separated instead of tab-separated.
10. A bug in get_column function in util.c caused the
truncation of the alias of a hostname.
11. DL macro has the functionality that all mails addressed
to the domain specified by DL, should be delivered
directly even if DS is set. In public domain version of
8.8.6, DL macro has a different meaning. This patch
(PHNE_10495) retains the definition of DL as in public
domain, including the functionality of DL as in previous
versions using the Dm macro.
12. In Sendmail-8.8.6, in the absence of the E mailer flag,
the value for the mailer flag E of openmail mailer is
"\r\n" by default, whereas Openmail requires it to be
"\n".
13. killsm script (sendmail) didn't have a rval statement
and sendmail script was printing duplicate messages
which were already being printed by killsm script.
14. The /usr/sbin/killsm script that is invoked by
/sbin/init.d/sendmail to stop the sendmail daemon should
detect whether sendmail is running in a more effective
way.
15. The check_local ruleset in the supplied
/etc/mail/sendmail.cf wrongly relayed mails destined for
<username><localdomain> to the smarthost relay specified
by the DS macro. The check_local ruleset also wrongly
truncated <username><hostname>.<localdomain> to
<username><hostname>.
16. The /usr/newconfig/etc/mail/sendmail.cf supplied along
with the previous sendmail patch contains errors
in ruleset 0.
Enhancement:
No (superseded patches contained enhancements)
PHNE_10495:
This patch provides an enhancement for reading the switch
configuration for sendmail from the /etc/nsswitch.conf
file instead of from /etc/mail/service.switch.
SR:
8606314706 8606248880 8606267547 8606280817 8606280836
8606289291 8606295551 8606303975 8606189011 8606305629
8606194375 8606213171 8606172226 8606105321 1653274639
8606136180 1653301234 5003458570 8606136181 8606132690
8606124372 8606127691 8606131029 1653304592 1653241869
8606102174 8606105428 8606127266 8606136331 8606105137
8606126031 5003396077 8606137834 1653281675 1653263640
1653267187 1653257824 8606216883 8606216885 8606216886
8606216887 8606216910 8606216911 1653253575 5003405894
8606216919 8606216921 8606113128 8606110249 8606216922
8606113052 5003371567 1653217869 5003371062 5003361105
8606216925 1653219436 1653204388 1653222042 5003386193
8606216926 8606216928 5003365924 8606216930 1653234641
5003382671
Patch Files:
InternetSrvcs.INETSVCS-RUN,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
/sbin/init.d/sendmail
/usr/newconfig/etc/mail/cf/cf/examples/chez.cs.mc
/usr/newconfig/etc/mail/cf/cf/examples/clientproto.mc
/usr/newconfig/etc/mail/cf/cf/examples/cs-hpux10.mc
/usr/newconfig/etc/mail/cf/cf/examples/cs-hpux9.mc
/usr/newconfig/etc/mail/cf/cf/examples/cs-osf1.mc
/usr/newconfig/etc/mail/cf/cf/examples/cs-solaris2.mc
/usr/newconfig/etc/mail/cf/cf/examples/cs-sunos4.1.mc
/usr/newconfig/etc/mail/cf/cf/examples/cs-ultrix4.mc
/usr/newconfig/etc/mail/cf/cf/examples/cyrusproto.mc
/usr/newconfig/etc/mail/cf/cf/examples/generic-bsd4.4.mc
/usr/newconfig/etc/mail/cf/cf/examples/generic-hpux9.mc
/usr/newconfig/etc/mail/cf/cf/examples/
generic-nextstep3.3.mc
/usr/newconfig/etc/mail/cf/cf/examples/generic-osf1.mc
/usr/newconfig/etc/mail/cf/cf/examples/generic-solaris2.mc
/usr/newconfig/etc/mail/cf/cf/examples/generic-sunos4.1.mc
/usr/newconfig/etc/mail/cf/cf/examples/generic-ultrix4.mc
/usr/newconfig/etc/mail/cf/cf/examples/huginn.cs.mc
/usr/newconfig/etc/mail/cf/cf/examples/knecht.mc
/usr/newconfig/etc/mail/cf/cf/examples/mail.cs.mc
/usr/newconfig/etc/mail/cf/cf/examples/mail.eecs.mc
/usr/newconfig/etc/mail/cf/cf/examples/mailspool.cs.mc
/usr/newconfig/etc/mail/cf/cf/examples/python.cs.mc
/usr/newconfig/etc/mail/cf/cf/examples/s2k-osf1.mc
/usr/newconfig/etc/mail/cf/cf/examples/s2k-ultrix4.mc
/usr/newconfig/etc/mail/cf/cf/examples/tcpproto.mc
/usr/newconfig/etc/mail/cf/cf/examples/ucbarpa.mc
/usr/newconfig/etc/mail/cf/cf/examples/ucbvax.mc
/usr/newconfig/etc/mail/cf/cf/examples/uucpproto.mc
/usr/newconfig/etc/mail/cf/cf/examples/vangogh.cs.mc
/usr/newconfig/etc/mail/cf/cf/generic-hpux10.cf
/usr/newconfig/etc/mail/cf/cf/generic-hpux10.mc
/usr/newconfig/etc/mail/cf/cf/gen_cf
/usr/newconfig/etc/mail/cf/sh/makeinfo.sh
/usr/newconfig/etc/mail/cf/README
/usr/newconfig/etc/mail/cf/README.hpux10
/usr/newconfig/etc/mail/cf/domain/examples/Berkeley.EDU.m4
/usr/newconfig/etc/mail/cf/domain/examples/
CS.Berkeley.EDU.m4
/usr/newconfig/etc/mail/cf/domain/examples/
EECS.Berkeley.EDU.m4
/usr/newconfig/etc/mail/cf/domain/examples/
S2K.Berkeley.EDU.m4
/usr/newconfig/etc/mail/cf/domain/examples/berkeley-only.m4
/usr/newconfig/etc/mail/cf/domain/generic.m4
/usr/newconfig/etc/mail/cf/feature/allmasquerade.m4
/usr/newconfig/etc/mail/cf/feature/masquerade_envelope.m4
/usr/newconfig/etc/mail/cf/feature/smrsh.m4
/usr/newconfig/etc/mail/cf/feature/always_add_domain.m4
/usr/newconfig/etc/mail/cf/feature/nocanonify.m4
/usr/newconfig/etc/mail/cf/feature/stickyhost.m4
/usr/newconfig/etc/mail/cf/feature/bestmx_is_local.m4
/usr/newconfig/etc/mail/cf/feature/nodns.m4
/usr/newconfig/etc/mail/cf/feature/use_ct_file.m4
/usr/newconfig/etc/mail/cf/feature/bitdomain.m4
/usr/newconfig/etc/mail/cf/feature/notsticky.m4
/usr/newconfig/etc/mail/cf/feature/use_cw_file.m4
/usr/newconfig/etc/mail/cf/feature/domaintable.m4
/usr/newconfig/etc/mail/cf/feature/nouucp.m4
/usr/newconfig/etc/mail/cf/feature/uucpdomain.m4
/usr/newconfig/etc/mail/cf/feature/local_procmail.m4
/usr/newconfig/etc/mail/cf/feature/nullclient.m4
/usr/newconfig/etc/mail/cf/feature/mailertable.m4
/usr/newconfig/etc/mail/cf/feature/redirect.m4
/usr/newconfig/etc/mail/cf/feature/genericstable.m4
/usr/newconfig/etc/mail/cf/feature/limited_masquerade.m4
/usr/newconfig/etc/mail/cf/feature/
masquerade_entire_domain.m4
/usr/newconfig/etc/mail/cf/feature/virtusertable.m4
/usr/newconfig/etc/mail/cf/feature/access_db.m4
/usr/newconfig/etc/mail/cf/feature/
accept_unresolvable_domains.m4
/usr/newconfig/etc/mail/cf/feature/
accept_unqualified_senders.m4
/usr/newconfig/etc/mail/cf/feature/blacklist_recipients.m4
/usr/newconfig/etc/mail/cf/feature/local_lmtp.m4
/usr/newconfig/etc/mail/cf/feature/loose_relay_check.m4
/usr/newconfig/etc/mail/cf/feature/promiscuous_relay.m4
/usr/newconfig/etc/mail/cf/feature/relay_based_on_MX.m4
/usr/newconfig/etc/mail/cf/feature/relay_entire_domain.m4
/usr/newconfig/etc/mail/cf/feature/relay_hosts_only.m4
/usr/newconfig/etc/mail/cf/feature/relay_local_from.m4
/usr/newconfig/etc/mail/cf/feature/rbl.m4
/usr/newconfig/etc/mail/cf/ostype/hpux10.m4
/usr/newconfig/etc/mail/cf/hack/README.check
/usr/newconfig/etc/mail/cf/hack/check_mail.m4
/usr/newconfig/etc/mail/cf/hack/check_mail2.m4
/usr/newconfig/etc/mail/cf/hack/check_mail3.m4
/usr/newconfig/etc/mail/cf/hack/check_rcpt.m4
/usr/newconfig/etc/mail/cf/hack/check_rcpt2.m4
/usr/newconfig/etc/mail/cf/hack/check_rcpt3.m4
/usr/newconfig/etc/mail/cf/hack/check_rcpt4.m4
/usr/newconfig/etc/mail/cf/hack/check_relay.m4
/usr/newconfig/etc/mail/cf/hack/check_relay1.m4
/usr/newconfig/etc/mail/cf/hack/check_relay3.m4
/usr/newconfig/etc/mail/cf/hack/deniedIP.m4
/usr/newconfig/etc/mail/cf/hack/deniedNames.m4
/usr/newconfig/etc/mail/cf/hack/spamdoms.m4
/usr/newconfig/etc/mail/cf/hack/spammers.m4
/usr/newconfig/etc/mail/cf/hack/use_ip.m4
/usr/newconfig/etc/mail/cf/hack/use_names.m4
/usr/newconfig/etc/mail/cf/hack/use_relayto.m4
/usr/newconfig/etc/mail/cf/hack/examples/cssubdomain.m4
/usr/newconfig/etc/mail/cf/mailer/examples/cyrus.m4
/usr/newconfig/etc/mail/cf/mailer/examples/fax.m4
/usr/newconfig/etc/mail/cf/mailer/examples/mail11.m4
/usr/newconfig/etc/mail/cf/mailer/examples/phquery.m4
/usr/newconfig/etc/mail/cf/mailer/examples/pop.m4
/usr/newconfig/etc/mail/cf/mailer/examples/procmail.m4
/usr/newconfig/etc/mail/cf/mailer/examples/usenet.m4
/usr/newconfig/etc/mail/cf/mailer/local.m4
/usr/newconfig/etc/mail/cf/mailer/smtp.m4
/usr/newconfig/etc/mail/cf/mailer/uucp.m4
/usr/newconfig/etc/mail/cf/mailer/openmail.m4
/usr/newconfig/etc/mail/cf/siteconfig/examples/
uucp.cogsci.m4
/usr/newconfig/etc/mail/cf/siteconfig/examples/
uucp.old.arpa.m4
/usr/newconfig/etc/mail/cf/siteconfig/examples/
uucp.ucbarpa.m4
/usr/newconfig/etc/mail/cf/siteconfig/examples/
uucp.ucbvax.m4
/usr/newconfig/etc/mail/cf/m4/cf.m4
/usr/newconfig/etc/mail/cf/m4/cfhead.m4
/usr/newconfig/etc/mail/cf/m4/nullrelay.m4
/usr/newconfig/etc/mail/cf/m4/proto.m4
/usr/newconfig/etc/mail/cf/m4/openmail_relays.m4
/usr/newconfig/etc/mail/cf/m4/openmail_s0_local.m4
/usr/newconfig/etc/mail/cf/m4/openmail_s0.m4
/usr/newconfig/etc/mail/cf/m4/version.m4
/usr/newconfig/etc/mail/sendmail.cf
/usr/newconfig/etc/mail/convert_awk
/usr/newconfig/etc/mail/convert_udb
/usr/newconfig/etc/mail/aliases
/usr/newconfig/etc/mail/sendmail.cw
/usr/sbin/sendmail
/usr/sbin/mailstats
/usr/sbin/makemap
/usr/sbin/expand_alias
/usr/sbin/mtail
/usr/sbin/smrsh
/usr/sbin/killsm
/usr/sbin/idlookup
/usr/sbin/itest
/usr/sbin/owners
/usr/bin/praliases
/usr/lbin/identd
/usr/share/lib/sendmail.hf
/usr/share/doc/sendmail8-8_delta.txt
/usr/share/doc/sendmail8-9_delta.txt
/usr/share/doc/sendmail8-9_release.txt
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
/usr/share/man/man1.Z/idlookup.1
/usr/share/man/man1.Z/mailq.1
/usr/share/man/man1.Z/mailstats.1
/usr/share/man/man1.Z/praliases.1
/usr/share/man/man1m.Z/convert_awk.1m
/usr/share/man/man1m.Z/identd.1m
/usr/share/man/man1m.Z/killsm.1m
/usr/share/man/man1m.Z/makemap.1m
/usr/share/man/man1m.Z/mtail.1m
/usr/share/man/man1m.Z/newaliases.1m
/usr/share/man/man1m.Z/owners.1m
/usr/share/man/man1m.Z/sendmail.1m
/usr/share/man/man1m.Z/smrsh.1m
/usr/share/man/man5.Z/aliases.5
what(1) Output:
InternetSrvcs.INETSVCS-RUN,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
/sbin/init.d/sendmail:
None
/usr/newconfig/etc/mail/cf/cf/examples/chez.cs.mc:
chez.cs.mc 8.11 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/clientproto.mc:
clientproto.mc 8.12 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/cs-hpux10.mc:
cs-hpux10.mc 8.10 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/cs-hpux9.mc:
cs-hpux9.mc 8.11 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/cs-osf1.mc:
cs-osf1.mc 8.10 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/cs-solaris2.mc:
cs-solaris2.mc 8.9 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/cs-sunos4.1.mc:
cs-sunos4.1.mc 8.10 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/cs-ultrix4.mc:
cs-ultrix4.mc 8.10 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/cyrusproto.mc:
cyrusproto.mc 8.3 (Carnegie Mellon) (#)cyrusproto
.mc 8.3')
/usr/newconfig/etc/mail/cf/cf/examples/generic-bsd4.4.mc:
generic-bsd4.4.mc 8.7 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/generic-hpux9.mc:
generic-hpux9.mc 8.8 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/
generic-nextstep3.3.mc:
generic-nextstep3.3.mc 8.7 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/generic-osf1.mc:
generic-osf1.mc 8.8 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/generic-solaris2.mc:
generic-solaris2.mc 8.8 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/generic-sunos4.1.mc:
generic-sunos4.1.mc 8.8 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/generic-ultrix4.mc:
generic-ultrix4.mc 8.8 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/huginn.cs.mc:
huginn.cs.mc 8.12 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/knecht.mc:
knecht.mc 8.31 (Berkeley) 1/30/1999')
/usr/newconfig/etc/mail/cf/cf/examples/mail.cs.mc:
mail.cs.mc 8.15 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/mail.eecs.mc:
mail.eecs.mc 8.15 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/mailspool.cs.mc:
mailspool.cs.mc 8.9 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/python.cs.mc:
python.cs.mc 8.9 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/s2k-osf1.mc:
s2k-osf1.mc 8.10 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/s2k-ultrix4.mc:
s2k-ultrix4.mc 8.10 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/tcpproto.mc:
tcpproto.mc 8.10 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/ucbarpa.mc:
ucbarpa.mc 8.9 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/ucbvax.mc:
ucbvax.mc 8.11 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/uucpproto.mc:
uucpproto.mc 8.12 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/examples/vangogh.cs.mc:
vangogh.cs.mc 8.10 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/generic-hpux10.cf:
cfhead.m4 8.23 (Berkeley) 3/3/2003 #####
cf.m4 8.29 (Berkeley) 5/19/1998 #####
generic-hpux10.mc 8.8 (Berkeley) 5/19/1998 ##
###
hpux10.m4 8.14 (Berkeley) 10/6/1998 #####
generic.m4 8.9 (Berkeley) 5/19/1998 #####
redirect.m4 8.10 (Berkeley) 5/19/1998 #####
use_cw_file.m4 8.6 (Berkeley) 5/19/1998 #####
domaintable.m4 8.9 (Berkeley) 10/6/1998 #####
mailertable.m4 8.10 (Berkeley) 10/6/1998 #####
genericstable.m4 8.8 (Berkeley) 10/6/1998 ##
###
virtusertable.m4 8.8 (Berkeley) 10/6/1998 ##
###
always_add_domain.m4 8.6 (Berkeley) 5/19/1998 ##
###
proto.m4 8.243 (Berkeley) 3/3/2003 #####
local.m4 8.30 (Berkeley) 6/30/1998 #####
smtp.m4 8.38 (Berkeley) 5/19/1998 #####
uucp.m4 8.30 (Berkeley) 5/19/1998 #####
/usr/newconfig/etc/mail/cf/cf/generic-hpux10.mc:
generic-hpux10.mc 8.8 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/cf/gen_cf:
None
/usr/newconfig/etc/mail/cf/sh/makeinfo.sh:
makeinfo.sh 8.11 (Berkeley) 5/19/1998
/usr/newconfig/etc/mail/cf/README:
README 8.186 (Berkeley) 3/3/2003
/usr/newconfig/etc/mail/cf/README.hpux10:
None
/usr/newconfig/etc/mail/cf/domain/examples/Berkeley.EDU.m4:
Berkeley.EDU.m4 8.14 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/domain/examples/
CS.Berkeley.EDU.m4:
CS.Berkeley.EDU.m4 8.7 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/domain/examples/
EECS.Berkeley.EDU.m4:
EECS.Berkeley.EDU.m4 8.7 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/domain/examples/
S2K.Berkeley.EDU.m4:
S2K.Berkeley.EDU.m4 8.7 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/domain/examples/berkeley-only.m4:
unspecified-domain.m4 8.7 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/domain/generic.m4:
generic.m4 8.9 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/allmasquerade.m4:
allmasquerade.m4 8.7 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/always_add_domain.m4:
always_add_domain.m4 8.6 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/bestmx_is_local.m4:
bestmx_is_local.m4 8.14 (Berkeley) 1/25/1999')
/usr/newconfig/etc/mail/cf/feature/bitdomain.m4:
bitdomain.m4 8.14 (Berkeley) 10/6/1998')
/usr/newconfig/etc/mail/cf/feature/domaintable.m4:
domaintable.m4 8.9 (Berkeley) 10/6/1998')
/usr/newconfig/etc/mail/cf/feature/genericstable.m4:
genericstable.m4 8.8 (Berkeley) 10/6/1998')
/usr/newconfig/etc/mail/cf/feature/limited_masquerade.m4:
limited_masquerade.m4 8.6 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/local_procmail.m4:
local_procmail.m4 8.11 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/mailertable.m4:
mailertable.m4 8.10 (Berkeley) 10/6/1998')
/usr/newconfig/etc/mail/cf/feature/
masquerade_entire_domain.m4:
masquerade_entire_domain.m4 8.6 (Berkeley) 5/19/
1998')
/usr/newconfig/etc/mail/cf/feature/masquerade_envelope.m4:
masquerade_envelope.m4 8.6 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/nocanonify.m4:
nocanonify.m4 8.6 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/nodns.m4:
nodns.m4 8.9 (Berkeley) 10/6/1998')
/usr/newconfig/etc/mail/cf/feature/notsticky.m4:
notsticky.m4 8.8 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/nouucp.m4:
nouucp.m4 8.6 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/nullclient.m4:
nullclient.m4 8.12 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/redirect.m4:
redirect.m4 8.10 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/smrsh.m4:
smrsh.m4 8.8 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/stickyhost.m4:
stickyhost.m4 8.6 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/use_ct_file.m4:
use_ct_file.m4 8.6 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/use_cw_file.m4:
use_cw_file.m4 8.6 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/uucpdomain.m4:
uucpdomain.m4 8.14 (Berkeley) 10/6/1998')
/usr/newconfig/etc/mail/cf/feature/virtusertable.m4:
virtusertable.m4 8.8 (Berkeley) 10/6/1998')
/usr/newconfig/etc/mail/cf/feature/rbl.m4:
rbl.m4 8.8 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/relay_local_from.m4:
relay_local_from.m4 8.2 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/relay_hosts_only.m4:
relay_hosts_only.m4 8.7 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/relay_entire_domain.m4:
relay_entire_domain.m4 8.7 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/relay_based_on_MX.m4:
relay_based_on_MX.m4 8.7 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/promiscuous_relay.m4:
promiscuous_relay.m4 8.7 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/loose_relay_check.m4:
loose_relay_check.m4 8.3 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/local_lmtp.m4:
local_lmtp.m4 8.5 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/blacklist_recipients.m4:
blacklist_recipients.m4 8.9 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/feature/
accept_unqualified_senders.m4:
accept_unqualified_senders.m4 8.3 (Berkeley) 5/19/
1998')
/usr/newconfig/etc/mail/cf/feature/
accept_unresolvable_domains.m4:
accept_unresolvable_domains.m4 8.7 (Berkeley) 5/19/
1998')
/usr/newconfig/etc/mail/cf/feature/access_db.m4:
access_db.m4 8.8 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/ostype/hpux10.m4:
hpux10.m4 8.14 (Berkeley) 10/6/1998')
/usr/newconfig/etc/mail/cf/hack/examples/cssubdomain.m4:
cssubdomain.m4 8.6 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/hack/README.check:
None
/usr/newconfig/etc/mail/cf/hack/check_mail.m4:
check_mail.m4 1.1 (Claus Assmann) 1997-03-09')
/usr/newconfig/etc/mail/cf/hack/check_mail2.m4:
check_mail.m4 2.1 (Claus Assmann) 1997-03-30')
/usr/newconfig/etc/mail/cf/hack/check_mail3.m4:
check_mail.m4 3.0 (Claus Assmann) 1997-06-01')
/usr/newconfig/etc/mail/cf/hack/check_rcpt.m4:
check_rcpt.m4 1.0 (Claus Assmann) 1996-11-23')
/usr/newconfig/etc/mail/cf/hack/check_rcpt2.m4:
check_rcpt2.m4 2.0 (Claus Assmann) 1997-03-01')
/usr/newconfig/etc/mail/cf/hack/check_rcpt3.m4:
check_rcpt3.m4 2.2 (Claus Assmann) 1997-03-09')
/usr/newconfig/etc/mail/cf/hack/check_rcpt4.m4:
check_rcpt4.m4 2.3 (Claus Assmann) 1997-03-16')
/usr/newconfig/etc/mail/cf/hack/check_relay.m4:
check_relay.m4 1.1 (Claus Assmann) 1997-03-09')
/usr/newconfig/etc/mail/cf/hack/check_relay1.m4:
check_relay.m4 2.0 (Claus Assmann) 1997-05-25')
/usr/newconfig/etc/mail/cf/hack/check_relay3.m4:
check_relay.m4 3.0 (Claus Assmann) 1997-06-01')
/usr/newconfig/etc/mail/cf/hack/deniedIP.m4:
deniedIP.m4 1.0 (Claus Assmann) 1996-11-23')
/usr/newconfig/etc/mail/cf/hack/deniedNames.m4:
deniedNames.m4 1.0 (Claus Assmann) 1996-11-23')
/usr/newconfig/etc/mail/cf/hack/spamdoms.m4:
spamdoms.m4 1.0 (Claus Assmann) 1996-11-23')
/usr/newconfig/etc/mail/cf/hack/spammers.m4:
spammers.m4 1.0 (Claus Assmann) 1996-11-23')
/usr/newconfig/etc/mail/cf/hack/use_ip.m4:
use_ip.m4 1.0 (Claus Assmann) 1996-11-23')
/usr/newconfig/etc/mail/cf/hack/use_names.m4:
use_names.m4 1.0 (Claus Assmann) 1996-11-23')
/usr/newconfig/etc/mail/cf/hack/use_relayto.m4:
use_relayto.m4 1.0 (Claus Assmann) 1996-11-23')
/usr/newconfig/etc/mail/cf/mailer/examples/cyrus.m4:
cyrus.m4 8.9 (Carnegie Mellon) 5/19/1998')
/usr/newconfig/etc/mail/cf/mailer/examples/fax.m4:
fax.m4 8.11 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/mailer/examples/mail11.m4:
mail11.m4 8.8 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/mailer/examples/phquery.m4:
phquery.m4 8.6 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/mailer/examples/pop.m4:
pop.m4 8.11 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/mailer/examples/procmail.m4:
procmail.m4 8.11 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/mailer/examples/usenet.m4:
usenet.m4 8.10 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/mailer/local.m4:
local.m4 8.30 (Berkeley) 6/30/1998')
/usr/newconfig/etc/mail/cf/mailer/openmail.m4:
None
/usr/newconfig/etc/mail/cf/mailer/smtp.m4:
smtp.m4 8.38 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/mailer/uucp.m4:
uucp.m4 8.30 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/siteconfig/examples/
uucp.cogsci.m4:
None
/usr/newconfig/etc/mail/cf/siteconfig/examples/
uucp.old.arpa.m4:
None
/usr/newconfig/etc/mail/cf/siteconfig/examples/
uucp.ucbarpa.m4:
None
/usr/newconfig/etc/mail/cf/siteconfig/examples/
uucp.ucbvax.m4:
None
/usr/newconfig/etc/mail/cf/m4/cf.m4:
cf.m4 8.29 (Berkeley) 5/19/1998')')
/usr/newconfig/etc/mail/cf/m4/cfhead.m4:
cfhead.m4 8.23 (Berkeley) 3/3/2003')
/usr/newconfig/etc/mail/cf/m4/nullrelay.m4:
nullrelay.m4 8.19 (Berkeley) 5/19/1998')
/usr/newconfig/etc/mail/cf/m4/openmail_relays.m4:
None
/usr/newconfig/etc/mail/cf/m4/openmail_s0.m4:
None
/usr/newconfig/etc/mail/cf/m4/openmail_s0_local.m4:
None
/usr/newconfig/etc/mail/cf/m4/proto.m4:
proto.m4 8.243 (Berkeley) 3/3/2003')
/usr/newconfig/etc/mail/cf/m4/version.m4:
version.m4 8.9.3.1 (Berkeley) 2/4/1999')
/usr/newconfig/etc/mail/sendmail.cf:
cfhead.m4 8.23 (Berkeley) 3/3/2003 #####
cf.m4 8.29 (Berkeley) 5/19/1998 #####
generic-hpux10.mc 8.8 (Berkeley) 5/19/1998 ##
###
hpux10.m4 8.14 (Berkeley) 10/6/1998 #####
generic.m4 8.9 (Berkeley) 5/19/1998 #####
redirect.m4 8.10 (Berkeley) 5/19/1998 #####
use_cw_file.m4 8.6 (Berkeley) 5/19/1998 #####
domaintable.m4 8.9 (Berkeley) 10/6/1998 #####
mailertable.m4 8.10 (Berkeley) 10/6/1998 #####
genericstable.m4 8.8 (Berkeley) 10/6/1998 ##
###
virtusertable.m4 8.8 (Berkeley) 10/6/1998 ##
###
always_add_domain.m4 8.6 (Berkeley) 5/19/1998 ##
###
proto.m4 8.243 (Berkeley) 3/3/2003 #####
local.m4 8.30 (Berkeley) 6/30/1998 #####
smtp.m4 8.38 (Berkeley) 5/19/1998 #####
uucp.m4 8.30 (Berkeley) 5/19/1998 #####
/usr/newconfig/etc/mail/convert_awk:
None
/usr/newconfig/etc/mail/convert_udb:
None
/usr/newconfig/etc/mail/aliases:
aliases $Revision: 1.1.212.1 $ $Date: 99/09/13 15:13
:16 $
/usr/newconfig/etc/mail/sendmail.cw:
None
/usr/sbin/expand_alias:
None
/usr/sbin/idlookup:
None
/usr/sbin/itest:
None
/usr/sbin/killsm:
killsm 03/21/2003 PHNE_28809
/usr/sbin/mailstats:
mailstats.c 8.29 (Berkeley) 3/21/2003 (PHNE_2880
9)
Copyright (c) 1988, 1993
/usr/sbin/makemap:
makemap.c 8.71 (Berkeley) 03/21/2003 (PHNE_288
09)
/usr/sbin/mtail:
None
/usr/sbin/owners:
None
/usr/sbin/sendmail:
Copyright (c) 1998 HEWLETT PACKARD COMPANY and its l
icensors,
including Sendmail, Inc., and the Regents of the
University of California. All rights reserved.
version.c 8.9.3.1 (Berkeley) 05/05/2003 (PHNE_
28809)
/usr/sbin/smrsh:
smrsh.c 8.11 (Berkeley) 5/19/1998
/usr/bin/praliases:
praliases.c 8.21 (Berkeley) 12/27/1998
Copyright (c) 1988, 1993
/usr/lbin/identd:
None
/usr/share/doc/sendmail8-8_delta.txt:
None
/usr/share/doc/sendmail8-9_delta.txt:
None
/usr/share/doc/sendmail8-9_release.txt:
None
/usr/share/lib/sendmail.hf:
sendmail.hf 8.18 (Berkeley) 11/19/1998
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
/usr/share/man/man1.Z/idlookup.1:
None
/usr/share/man/man1.Z/mailq.1:
None
/usr/share/man/man1.Z/mailstats.1:
None
/usr/share/man/man1.Z/praliases.1:
None
/usr/share/man/man1m.Z/convert_awk.1m:
None
/usr/share/man/man1m.Z/identd.1m:
None
/usr/share/man/man1m.Z/killsm.1m:
None
/usr/share/man/man1m.Z/makemap.1m:
None
/usr/share/man/man1m.Z/mtail.1m:
None
/usr/share/man/man1m.Z/newaliases.1m:
None
/usr/share/man/man1m.Z/owners.1m:
None
/usr/share/man/man1m.Z/sendmail.1m:
None
/usr/share/man/man1m.Z/smrsh.1m:
None
/usr/share/man/man5.Z/aliases.5:
None
cksum(1) Output:
InternetSrvcs.INETSVCS-RUN,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
1760146909 3670 /sbin/init.d/sendmail
267762509 1061 /usr/newconfig/etc/mail/cf/cf/examples/
chez.cs.mc
251899011 1172 /usr/newconfig/etc/mail/cf/cf/examples/
clientproto.mc
1488241504 1033 /usr/newconfig/etc/mail/cf/cf/examples/
cs-hpux10.mc
3950761318 1031 /usr/newconfig/etc/mail/cf/cf/examples/
cs-hpux9.mc
2094119169 976 /usr/newconfig/etc/mail/cf/cf/examples/
cs-osf1.mc
1784364563 989 /usr/newconfig/etc/mail/cf/cf/examples/
cs-solaris2.mc
2134344461 990 /usr/newconfig/etc/mail/cf/cf/examples/
cs-sunos4.1.mc
2390053282 987 /usr/newconfig/etc/mail/cf/cf/examples/
cs-ultrix4.mc
1002599505 1503 /usr/newconfig/etc/mail/cf/cf/examples/
cyrusproto.mc
3930645504 825 /usr/newconfig/etc/mail/cf/cf/examples/
generic-bsd4.4.mc
2178306141 761 /usr/newconfig/etc/mail/cf/cf/examples/
generic-hpux9.mc
4012103649 781 /usr/newconfig/etc/mail/cf/cf/examples/
generic-nextstep3.3.mc
1666684937 755 /usr/newconfig/etc/mail/cf/cf/examples/
generic-osf1.mc
2527890179 787 /usr/newconfig/etc/mail/cf/cf/examples/
generic-solaris2.mc
923478670 769 /usr/newconfig/etc/mail/cf/cf/examples/
generic-sunos4.1.mc
3245866493 766 /usr/newconfig/etc/mail/cf/cf/examples/
generic-ultrix4.mc
1428772163 1162 /usr/newconfig/etc/mail/cf/cf/examples/
huginn.cs.mc
84202287 2027 /usr/newconfig/etc/mail/cf/cf/examples/
knecht.mc
1181368076 1250 /usr/newconfig/etc/mail/cf/cf/examples/
mail.cs.mc
2607515544 1295 /usr/newconfig/etc/mail/cf/cf/examples/
mail.eecs.mc
2327718032 1016 /usr/newconfig/etc/mail/cf/cf/examples/
mailspool.cs.mc
1166100154 1294 /usr/newconfig/etc/mail/cf/cf/examples/
python.cs.mc
1203687112 973 /usr/newconfig/etc/mail/cf/cf/examples/
s2k-osf1.mc
213280064 984 /usr/newconfig/etc/mail/cf/cf/examples/
s2k-ultrix4.mc
2721718810 1072 /usr/newconfig/etc/mail/cf/cf/examples/
tcpproto.mc
3016150426 911 /usr/newconfig/etc/mail/cf/cf/examples/
ucbarpa.mc
2262788232 2781 /usr/newconfig/etc/mail/cf/cf/examples/
ucbvax.mc
2245144638 1132 /usr/newconfig/etc/mail/cf/cf/examples/
uucpproto.mc
1181256990 1000 /usr/newconfig/etc/mail/cf/cf/examples/
vangogh.cs.mc
3315501723 94478 /usr/newconfig/etc/mail/cf/cf/
generic-hpux10.cf
2054792231 1603 /usr/newconfig/etc/mail/cf/cf/
generic-hpux10.mc
33091609 18405 /usr/newconfig/etc/mail/cf/cf/gen_cf
2154838084 1085 /usr/newconfig/etc/mail/cf/sh/makeinfo.sh
4168274239 90806 /usr/newconfig/etc/mail/cf/README
3906406566 1939 /usr/newconfig/etc/mail/cf/README.hpux10
3968689964 808 /usr/newconfig/etc/mail/cf/domain/examples/
Berkeley.EDU.m4
2496004847 605 /usr/newconfig/etc/mail/cf/domain/examples/
CS.Berkeley.EDU.m4
807105368 525 /usr/newconfig/etc/mail/cf/domain/examples/
EECS.Berkeley.EDU.m4
2472132303 531 /usr/newconfig/etc/mail/cf/domain/examples/
S2K.Berkeley.EDU.m4
876453561 753 /usr/newconfig/etc/mail/cf/domain/examples/
berkeley-only.m4
2702216170 890 /usr/newconfig/etc/mail/cf/domain/generic.m4
3304955377 505 /usr/newconfig/etc/mail/cf/feature/
allmasquerade.m4
3124111415 511 /usr/newconfig/etc/mail/cf/feature/
always_add_domain.m4
291437703 1552 /usr/newconfig/etc/mail/cf/feature/
bestmx_is_local.m4
311492889 669 /usr/newconfig/etc/mail/cf/feature/
bitdomain.m4
583624415 673 /usr/newconfig/etc/mail/cf/feature/
domaintable.m4
3922827854 674 /usr/newconfig/etc/mail/cf/feature/
genericstable.m4
2937213553 513 /usr/newconfig/etc/mail/cf/feature/
limited_masquerade.m4
4237257655 715 /usr/newconfig/etc/mail/cf/feature/
local_procmail.m4
2449325761 673 /usr/newconfig/etc/mail/cf/feature/
mailertable.m4
992338378 525 /usr/newconfig/etc/mail/cf/feature/
masquerade_entire_domain.m4
412899473 515 /usr/newconfig/etc/mail/cf/feature/
masquerade_envelope.m4
201563856 498 /usr/newconfig/etc/mail/cf/feature/
nocanonify.m4
2713749745 734 /usr/newconfig/etc/mail/cf/feature/nodns.m4
1742778774 572 /usr/newconfig/etc/mail/cf/feature/
notsticky.m4
1572858421 490 /usr/newconfig/etc/mail/cf/feature/nouucp.m4
1618356003 1631 /usr/newconfig/etc/mail/cf/feature/
nullclient.m4
455593662 812 /usr/newconfig/etc/mail/cf/feature/redirect.m4
958813391 674 /usr/newconfig/etc/mail/cf/feature/smrsh.m4
4096409728 506 /usr/newconfig/etc/mail/cf/feature/
stickyhost.m4
3968957053 708 /usr/newconfig/etc/mail/cf/feature/
use_ct_file.m4
3034523323 716 /usr/newconfig/etc/mail/cf/feature/
use_cw_file.m4
3097377833 662 /usr/newconfig/etc/mail/cf/feature/
uucpdomain.m4
2259709759 674 /usr/newconfig/etc/mail/cf/feature/
virtusertable.m4
24201951 376 /usr/newconfig/etc/mail/cf/feature/rbl.m4
1159029469 354 /usr/newconfig/etc/mail/cf/feature/
relay_local_from.m4
47301025 354 /usr/newconfig/etc/mail/cf/feature/
relay_hosts_only.m4
1540096691 360 /usr/newconfig/etc/mail/cf/feature/
relay_entire_domain.m4
4186251641 354 /usr/newconfig/etc/mail/cf/feature/
relay_based_on_MX.m4
25453140 356 /usr/newconfig/etc/mail/cf/feature/
promiscuous_relay.m4
337960720 356 /usr/newconfig/etc/mail/cf/feature/
loose_relay_check.m4
166933546 524 /usr/newconfig/etc/mail/cf/feature/
local_lmtp.m4
3469467325 468 /usr/newconfig/etc/mail/cf/feature/
blacklist_recipients.m4
1587660530 374 /usr/newconfig/etc/mail/cf/feature/
accept_unqualified_senders.m4
2069105444 376 /usr/newconfig/etc/mail/cf/feature/
accept_unresolvable_domains.m4
697415333 415 /usr/newconfig/etc/mail/cf/feature/
access_db.m4
1114730887 1555 /usr/newconfig/etc/mail/cf/ostype/hpux10.m4
3004038440 800 /usr/newconfig/etc/mail/cf/hack/examples/
cssubdomain.m4
479519935 5218 /usr/newconfig/etc/mail/cf/hack/README.check
4184762790 2428 /usr/newconfig/etc/mail/cf/hack/
check_mail.m4
3767260844 2697 /usr/newconfig/etc/mail/cf/hack/
check_mail2.m4
1202789081 2825 /usr/newconfig/etc/mail/cf/hack/
check_mail3.m4
2715208529 1799 /usr/newconfig/etc/mail/cf/hack/
check_rcpt.m4
2823506407 1981 /usr/newconfig/etc/mail/cf/hack/
check_rcpt2.m4
1605065517 1829 /usr/newconfig/etc/mail/cf/hack/
check_rcpt3.m4
787456471 2237 /usr/newconfig/etc/mail/cf/hack/
check_rcpt4.m4
3936599351 1483 /usr/newconfig/etc/mail/cf/hack/
check_relay.m4
3332536664 1890 /usr/newconfig/etc/mail/cf/hack/
check_relay1.m4
113528187 1977 /usr/newconfig/etc/mail/cf/hack/
check_relay3.m4
2968439879 1229 /usr/newconfig/etc/mail/cf/hack/deniedIP.m4
2265798934 1260 /usr/newconfig/etc/mail/cf/hack/
deniedNames.m4
972928728 1212 /usr/newconfig/etc/mail/cf/hack/spamdoms.m4
2682102871 1243 /usr/newconfig/etc/mail/cf/hack/spammers.m4
1566289833 1270 /usr/newconfig/etc/mail/cf/hack/use_ip.m4
1398313288 1247 /usr/newconfig/etc/mail/cf/hack/use_names.m4
986762267 1197 /usr/newconfig/etc/mail/cf/hack/
use_relayto.m4
1265672141 2621 /usr/newconfig/etc/mail/cf/mailer/examples/
cyrus.m4
4138429300 1017 /usr/newconfig/etc/mail/cf/mailer/examples/
fax.m4
1582861847 1870 /usr/newconfig/etc/mail/cf/mailer/examples/
mail11.m4
1478061756 934 /usr/newconfig/etc/mail/cf/mailer/examples/
phquery.m4
953843916 947 /usr/newconfig/etc/mail/cf/mailer/examples/
pop.m4
4192306626 1127 /usr/newconfig/etc/mail/cf/mailer/examples/
procmail.m4
2282126892 971 /usr/newconfig/etc/mail/cf/mailer/examples/
usenet.m4
2419516475 2851 /usr/newconfig/etc/mail/cf/mailer/local.m4
2852494950 1077 /usr/newconfig/etc/mail/cf/mailer/
openmail.m4
680817347 3867 /usr/newconfig/etc/mail/cf/mailer/smtp.m4
4209894318 4996 /usr/newconfig/etc/mail/cf/mailer/uucp.m4
3205063794 77 /usr/newconfig/etc/mail/cf/siteconfig/
examples/uucp.cogsci.m4
1416125378 57 /usr/newconfig/etc/mail/cf/siteconfig/
examples/uucp.old.arpa.m4
3515105045 1 /usr/newconfig/etc/mail/cf/siteconfig/examples/
uucp.ucbarpa.m4
1861495610 977 /usr/newconfig/etc/mail/cf/siteconfig/
examples/uucp.ucbvax.m4
1532130353 796 /usr/newconfig/etc/mail/cf/m4/cf.m4
3317740041 49231 /usr/newconfig/etc/mail/cf/m4/cfhead.m4
1700068461 3439 /usr/newconfig/etc/mail/cf/m4/nullrelay.m4
156471656 215 /usr/newconfig/etc/mail/cf/m4/
openmail_relays.m4
1463617883 1595 /usr/newconfig/etc/mail/cf/m4/openmail_s0.m4
858598581 2598 /usr/newconfig/etc/mail/cf/m4/
openmail_s0_local.m4
4180849235 57950 /usr/newconfig/etc/mail/cf/m4/proto.m4
533846403 543 /usr/newconfig/etc/mail/cf/m4/version.m4
3315501723 94478 /usr/newconfig/etc/mail/sendmail.cf
848421388 2197 /usr/newconfig/etc/mail/convert_awk
3209622866 281 /usr/newconfig/etc/mail/convert_udb
1003701682 870 /usr/newconfig/etc/mail/aliases
342790006 666 /usr/newconfig/etc/mail/sendmail.cw
2467658493 9878 /usr/sbin/expand_alias
2892931508 20480 /usr/sbin/idlookup
2626079863 20480 /usr/sbin/itest
2766308705 1052 /usr/sbin/killsm
3348403837 20480 /usr/sbin/mailstats
6963538 413696 /usr/sbin/makemap
2881756235 184 /usr/sbin/mtail
1797097046 42 /usr/sbin/owners
3217721439 831488 /usr/sbin/sendmail
4201722267 20480 /usr/sbin/smrsh
95899489 401408 /usr/bin/praliases
533564322 32768 /usr/lbin/identd
586165240 31110 /usr/share/doc/sendmail8-8_delta.txt
634107438 33858 /usr/share/doc/sendmail8-9_delta.txt
2537071912 24352 /usr/share/doc/sendmail8-9_release.txt
2542668846 5420 /usr/share/lib/sendmail.hf
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
4202473574 890 /usr/share/man/man1.Z/idlookup.1
3878697966 2324 /usr/share/man/man1.Z/mailq.1
927523491 2401 /usr/share/man/man1.Z/mailstats.1
3924566826 1652 /usr/share/man/man1.Z/praliases.1
2128558780 703 /usr/share/man/man1m.Z/convert_awk.1m
1520281684 3347 /usr/share/man/man1m.Z/identd.1m
510252392 975 /usr/share/man/man1m.Z/killsm.1m
3546234040 2780 /usr/share/man/man1m.Z/makemap.1m
3891225637 554 /usr/share/man/man1m.Z/mtail.1m
1560281364 2195 /usr/share/man/man1m.Z/newaliases.1m
491636279 521 /usr/share/man/man1m.Z/owners.1m
1311084351 12207 /usr/share/man/man1m.Z/sendmail.1m
1537261846 2498 /usr/share/man/man1m.Z/smrsh.1m
3398809601 4057 /usr/share/man/man5.Z/aliases.5
Patch Conflicts: None
Patch Dependencies:
s700: 11.00: PHNE_24715
s800: 11.00: PHNE_24715
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_10495 PHNE_13947 PHNE_15509 PHNE_16852 PHNE_17190 PHNE_18546
PHNE_24419 PHNE_26304
Equivalent Patches:
PHNE_28810:
s700: 11.11
s800: 11.11
PHNE_28409:
s700: 11.22
s800: 11.22
Patch Package Size: 1340 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHNE_28809
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_28809.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_28809. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHNE_28809.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_28809.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_28809.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
This patch installs Sendmail-8.9.3 on HP-UX 11.00.
Sendmail-8.9.3 information is documented in the file
/usr/share/doc/sendmail8-9_release.txt. Please refer to this
document for the new/changed features of Sendmail-8.9.3.
To comply with industry-standard Sendmail(1M) practices,
after the installation of PHNE_26304, or any superseding
patches, the following behavior will be observed:
1. Non-root users will not be able to print system-wide
Sendmail aliases using the praliases(1) command.
2. Non-root users will not be able to print mail traffic
statistics using the mailstats(1) command.
3. Non-root users will not be able to send signals to
Sendmail processes, including their own processes.
4. Sendmail reacts more appropriately to signals,
which may introduce some delay in terminating and
restarting Sendmail daemon.
The behaviors one and two mentioned above may
remain even after the removal of the patch.
This patch delivers a new copy of the sendmail
configuration file /etc/mail/sendmail.cf as
/usr/newconfig/etc/mail/sendmail.cf. You need to
merge your site-specific customizations with this
new sendmail.cf file. Then, stop and start the
sendmail daemon by using the following commands:
/sbin/init.d/sendmail stop
/sbin/init.d/sendmail start
REMARK: If you have previously upgraded to sendmail 8.9.3
by installing patch PHNE_18546 or a superseding
patch, then the following instructions do not
apply.
Note: Sendmail-8.9.3 uses a new db, db-3.0.55. The
underlying database file formats are changed from the
previous version of DB to db-3.0.55. Therefore, you need
to recreate all the used database files. The new
/etc/mail/aliases.db is created while installing the patch.
This patch contains the implementation for an enhancement
request for reading the switch configuration for sendmail
from the /etc/nsswitch.conf file instead of from
/etc/mail/service.switch. If /etc/nsswitch.conf is not
present then sendmail uses the following switch
configuration:
hosts: dns nis files
aliases: files
If NIS is used for aliases, update /etc/nsswitch.conf as:
aliases: files nis
OR
add nis:mail.aliases for the AliasFile option in the
/etc/mail/sendmail.cf as:
O AliasFile=/etc/mail/aliases,nis:mail.aliases
This patch contains a fully documented sendmail.cf located
at /usr/newconfig/etc/mail/. This file contains anti-
spamming rulesets that can be used to prevent unauthorized
relaying access to the mail server. It is strongly
recommended that this file be used as the base sendmail
configuration with site-specific modifications as required.
The sendmail.cf supplied with the previous version of
sendmail(8.7) is compatible with sendmail-8.9.3 installed
by this patch except for interoperability with Openmail.
See the WARNING below for details.
IMPORTANT WARNING:
=================
1. Installing this patch will have implications for Openmail
due to the change in default end-of-string for all SMTP
commands in sendmail-8.9.3. The default end-of-string for
SMTP commands is \r\n for all delivery agents that speak
SMTP in 8.9.3, whereas it was \n in previous version of
sendmail.
In order to make sendmail-8.9.3 interoperate with
Openmail, please ensure you have the E=\n, in the mailer
definition for Openmail in sendmail.cf as given below:
Mopenmail, P=/opt/openmail/bin/unix.in, F=DFLMXmnu,
E=\n, S=15, R=25, A=unix.in
2. sendmail 8.9.3 includes a new configuration script
'gen_cf' to enable most of the sendmail-8.9.3 specific
features in the sendmail.cf configuration file.
DO NOT use this script after making OpenMail changes
or running 'omsendin' to include new features as
OpenMail changes made to configuration file will be lost.
-----End of Document ID: PHNE_28809------------------------------------------
Document ID: PHNE_28449
Date Loaded: 20030708
Title: s700_800 11.00 Bind 4.9.7 components
Patch Name: PHNE_28449
Patch Description: s700_800 11.00 Bind 4.9.7 components
Creation Date: 03/06/16
Post Date: 03/07/08
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
InternetSrvcs.INETSVCS-RUN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_28449
Symptoms:
PHNE_28449:
1. JAGad57510 / SR8606188302:
The output of the "ls <domain>" command in nslookup
4.9.7 may not contain all the resource records.
2. JAGae33084 / SR8606268849:
Problem with nslookup in BIND.
3. JAGae38578 / SR8606274501:
Problem with nslookup in BIND.
4. JAGae54341 / SR8606290432:
named does not cache the SIG record properly.
5. JAGae54339 / SR8606290430:
named does not function properly.
6. JAGae63828 / SR8606300359:
The installation of the patch bundle containing a BIND
patch gets delayed on a name server.
PHNE_23274:
1. JAGac79099 / SR8606128299:
"nslookup" cannot resolve hostnames properly
when there is wild card entry in DNS data files
and a search list having multiple entries in
resolv.conf.
2. JAGad09228 / SR8606139905:
DNS and symbolic link problem.
3. JAGad23810 / SR8606154493:
"nslookup" sets timeout value to 5000 seconds when
name server host is specified at the command line.
4. JAGab53671 / SR1653307470:
"hosts_to_named" does not validate entries in
/etc/hosts.
5. JAGad41828/8606172568:
named loops with some record queries.
6. JAGad38231/8606168953:
Disable version query feature on BIND 4.9.7.
7. JAGad48072/8606178847:
Incorrect error messages generated by named for
malformed DNS queries.
8. JAGad25757/8606156419:
PHNE_20619 downgrades bind 8.1.2 to 4.9.7
PHNE_20619:
1. JAGac40451:
Address CERT Advisory CA-99-14.
2. JAGaa57264:
named fails to resolve some of the names.
3. JAGaa94851:
Incorrect message being displayed while installing
patch PHNE_14618.
4. JAGaa27075:
nslookup does not always work.
5. JAGab69094:
BIND 4.9.7 and 8.1.2 resolver code not searching
and stopping with FQDN.
6. JAGab84583:
In NCPM environment, BIND 4.9.7 consumes more memory.
7. JAGab21142:
Disable XSTATS on named.
8. JAGab25088: nslookup(1) default behaviour
does not match switch(4) default behaviour.
PHNE_14618:
1. The pid log of named is different in PHNE_12957.
2. Performance problem with bind.
PHNE_12957:
1. Upgrade to Bind 4.9.7
2. DNS has problem when directed to use a forwarder.
3. Bug in named 4.9.3 causes named to stop working
after 3 or 4 days and has to be restarted.
4. Problem with named.
Defect Description:
PHNE_28449:
1. JAGad57510 / SR 8606188302:
Whenever the reply for "ls <domain>" command from some
dns-bind 8.1.2 servers contains an invalid record,
nslookup does not print the remaining valid records.
Resolution:
nslookup now skips only the invalid records recieved
from the server and prints all the valid ones till it
reaches the end of records.
2. JAGae33084 / SR8606268849:
Under certain circumstances the DNS nslookup resolver
incorrectly calculates the available buffer size.
Resolution :
The buffer size is now calculated properly.
3. JAGae38578 / SR8606274501:
Under certain circumstances, large size packets
received by nslookup were not handled properly.
Resolution:
nslookup now properly handles packets of all sizes.
4. JAGae54341 / SR8606290432:
named does not cache the SIG record properly.
Resolution :
named has been modified to cache the SIG record properly.
5. JAGae54339 / SR8606290430:
named does not handle SIG record properly.
Resolution :
named has been modified to handle SIG record properly.
6. JAGae63828 / SR8606300359:
The BIND preinstallation script stops the name server
while installing the patch, and the name server is
restarted only in the postinstallation script. During
this time duration, the resolver experiences a delay
before it falls back to an alternative switch policy,
when the BIND patch is bundled with other patches.
Resolution:
The problem has now been resolved by both stopping and
restarting the name server in the postinstallation
script.
PHNE_23274:
1. JAGac79099/8606128299:
nslookup does not go through alternative domain
entries in the search list when the nameserver
returns a non-authoritative record with no answers.
Resolution:
nslookup now goes through alternative entries in the
search list when it receives a non-authoritative record
with no answers.
2. JAGad09228/8606139905:
DNS and symbolic link problem.
Resolution:
DNS now compatible with symbolic links.
3. JAGad23810 / SR8606154493:
nslookup takes a very long time in responding
due to the retransmission value being set to
millisecs by libc. As nslookup assumes the
value to be in seconds there was a long delay for
responses to non-existent records.
Resolution:
nslookup resets timeout value in seconds if the value
has been set in milliseconds by libc.
4. JAGab53671 / SR1653307470:
hosts_to_named fails to validate entries in /etc/hosts.
Also this script takes a very long time to execute
when /etc/hosts contains a large number of entries.
Resolution:
hosts_to_named now checks for non-numeric values in
IP addresses of /etc/hosts entries. It also avoids
calling a function multiple times thereby reducing
the time taken to execute this program.
5. JAGad41828/8606172568:
With some specific SRV records, named may loop.
Resolution:
Proper initialization of pointers resolved and avoided
the unnecessary loops of named.
6. JAGad38231/8606168953:
An ER was requested to disable version query thru
nslookup.
Resolution:
Bind version query thru nslookup has been disabled.
7. JAGad48072/8606178847:
When named encountered malformed DNS queries, it
generated wrong error messages.
Resolution:
named has been fixed to report proper error messages.
8. JAGad25757/8606156419:
Bind version was not verified before installing the
patch.
Resolution:
Checkinstall script has been included to ensure that
correct version of patch is being installed.
PHNE_20619:
1. JAGac40451:
BIND 4.9.7 is affected by few of the vulnerabilities
reported by CERT.
Resolution:
The vulnerabilities have been addressed.
2. JAGaa57264:
BIND 4.9.7 running as internal nameserver
and forwarding queries to external nameserver
fails when the lookup address has a CNAME
record with a higher TTL than its corresponding
A record.
Resolution:
The query packet header was not properly framed.
Now a proper header is sent in the query packet.
3. JAGaa94851:
When named is not running on the system, preinstall
script logs message "Name server stopped" which
is not correct.
Resolution:
Now the script does not log wrong message.
4. JAGaa27075:
If the switch policy for host lookup is as below
hosts: dns [NOTFOUND=continue] files
nslookup fails to find hosts that are in files only.
Resolution:
nslookup has been fixed to behave as advocated
by switch policy.
5. JAGab69094:
If the name being queried has at least one dot,
nslookup appends domain name instead of
trying it as it is, at the very first query.
Resolution:
If the name has atleast one dot in it, nslookup
looks up the name as it is at the very first time.
6. JAGab84583:
In NCPM environment, BIND 4.9.7 keeps on
consuming memory and after few days
it would run out of memory and eventually exit.
Resolution:
Memory management by named in NCPM
environment was not proper. Now it manages
properly.
7. JAGab21142:
ER by customer to disable XSTAT
information logged to syslog.
Resolution:
The "-X" command line option is provided
to disable XSTATS information that is logged
to syslog.
8. JAGab25088:
The default behaviour of nslookup
does not match default switch policy
mentioned in nsswitch.conf(4).
Resolution:
nslookup now conforms to default
switch policy for host lookup. The man page
for nslookup is also updated.
PHNE_14618:
1. The pid log of named is different in PHNE_12957.
2. Under a heavy load the DNS server is slow to respond
to DNS requests.
PHNE_12957:
1. Upgrade to Bind 4.9.7
2. Bug in forwarders implementation causes name resolution
to fail when forwarders are used.
3. named 4.9.3 bug: cache can drop root nameserver's
data and cannot recover.
4. Problem with named in Bind 4.9.6 code.
Enhancement:
No (superseded patches contained enhancements)
PHNE_20619:
This patch delivers an enhancement to disable XSTATS
on named (disabled through -X).
PHNE_12957:
This patch upgrades BIND from 4.9.3 to 4.9.7. Further
information on this new version of BIND can be found
in "/usr/share/doc/bind496.txt", which also includes
pointers to other sources of information regarding this
patch.
SR:
8606188302 8606268849 8606274501 8606290432 8606290430
8606300359 8606128299 8606139905 8606154493 1653307470
8606172568 8606168953 8606178847 8606156419 8606125060
5003446138 8606145226 1653257998 8606135784 8606112269
1653306647 1653308866 8606298830 5003425322 8606298838
1653240986 4701350181 4701387779
Patch Files:
InternetSrvcs.INETSVCS-RUN,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
/usr/sbin/named
/usr/sbin/named-xfer
/usr/bin/nslookup
/usr/share/doc/bind496.txt
/usr/share/doc/bog.txt.Z
/usr/share/doc/bog.ps.Z
/usr/sbin/hosts_to_named
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
/usr/share/man/man1m.Z/named.1m
/usr/share/man/man1.Z/nslookup.1
what(1) Output:
InternetSrvcs.INETSVCS-RUN,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
/usr/sbin/named:
Copyright (c) 1986, 1989, 1990 The Regents of the Un
iversity of California.
named 4.9.7 Thu Mar 13 09:52:01 GMT 2003 PHNE_28449
/usr/sbin/named-xfer:
Copyright (c) 1988, 1990 The Regents of the Universi
ty of California.
named 4.9.7 Thu Mar 13 09:52:01 GMT 2003 PHNE_28449
/usr/bin/nslookup:
Copyright (c) 1985,1989 Regents of the University of
California.
nslookup $Revision: 1.1.214.4 $ Thu Mar 13 09:52:35
GMT 2003 PHNE_28449
/usr/share/doc/bind496.txt:
None
/usr/share/doc/bog.txt.Z:
None
/usr/share/doc/bog.ps.Z:
None
/usr/sbin/hosts_to_named:
None
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
/usr/share/man/man1m.Z/named.1m:
None
/usr/share/man/man1.Z/nslookup.1:
None
cksum(1) Output:
InternetSrvcs.INETSVCS-RUN,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
3888024535 221184 /usr/sbin/named
1412031555 81920 /usr/sbin/named-xfer
3453484836 131072 /usr/bin/nslookup
2882227719 4313 /usr/share/doc/bind496.txt
1715827123 41278 /usr/share/doc/bog.txt.Z
3899687399 79421 /usr/share/doc/bog.ps.Z
484907866 47818 /usr/sbin/hosts_to_named
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
2788100613 8463 /usr/share/man/man1m.Z/named.1m
1861763 6984 /usr/share/man/man1.Z/nslookup.1
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_12957 PHNE_14618 PHNE_20619 PHNE_23274
Equivalent Patches:
PHNE_28448:
s700: 10.20
s800: 10.20
Patch Package Size: 420 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHNE_28449
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_28449.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_28449. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHNE_28449.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_28449.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_28449.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHNE_28449------------------------------------------
Document ID: PHCO_28845
Date Loaded: 20030708
Title: s700_800 11.11 ioinitrc(1M) cumulative patch
Patch Name: PHCO_28845
Patch Description: s700_800 11.11 ioinitrc(1M) cumulative patch
Creation Date: 03/04/03
Post Date: 03/07/08
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_28845
Symptoms:
PHCO_28845:
1.( SR: 8606296840 CR: JAGae60392 )
During boot process of a system, unauthorized user may get
into single user mode under some circumstances.
PHCO_27185:
1.( SR: 8606248408 CR: JAGae14808 )
Modify ioinitrc to allow VxVM to be the root volume
manager.
Defect Description:
PHCO_28845:
1.( SR: 8606296840 CR: JAGae60392 )
During boot process of a system, unauthorized user may
get into single user mode under some circumstances.
Resolution:
Now, the boot process is made more robust to always
check user authorization before starting up a shell
if the boot authentication mechanism is enabled on
the system.
PHCO_27185:
1.( SR: 8606248408 CR: JAGae14808 )
Modify ioinitrc to allow VxVM to be the root volume
manager
Resolution:
ioinitrc script is changed to check for VxVM
filesystem and if found, lvlnboot command is skipped.
Enhancement:
No
SR:
8606248408 8606296840
Patch Files:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/ioinitrc
what(1) Output:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/ioinitrc:
None
cksum(1) Output:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
2282210070 7773 /sbin/ioinitrc
Patch Conflicts: None
Patch Dependencies:
s700: 11.11: PHCO_27884
s800: 11.11: PHCO_27884
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHCO_27185
Equivalent Patches: None
Patch Package Size: 30 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHCO_28845
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_28845.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_28845. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHCO_28845.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_28845.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_28845.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_28845------------------------------------------
Document ID: PHCO_28830
Date Loaded: 20030708
Title: s700_800 11.11 security(4) man page cumulative patch
Patch Name: PHCO_28830
Patch Description: s700_800 11.11 security(4) man page cumulative patch
Creation Date: 03/03/28
Post Date: 03/07/08
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.ADMN-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.CORE-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
ProgSupport.PAUX-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
SecurityMon.SEC-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_28830
Symptoms:
PHCO_28830:
( SR:8606250483 CR:JAGae16858 )
No symptom. This is an enhancement request. This patch
is a member of a set of product updates needed to
enable the optional HP-UX Boot Authentication feature
in non-trusted mode. Upon installation, the HP-UX
Boot Authenticator bundle (BOOTAUTH11i) will install
the full set of product updates (including this patch)
to enable the boot authentication feature in non-trusted
mode.
If the HP-UX Boot Authenticator product is not installed,
this patch will have no impact on your system.
PHCO_27909:
( SR:8606221280 CR:JAGad90414 )
This patch is a member of a set of product updates needed
to enable the optional HP-UX shadow password feature.
Upon installation, the HP-UX shadow password bundle
(ShadowPassword) will install the full set of products
(including this patch) to enable the shadow password
feature.
If the HP-UX shadow password product is not installed,
this patch will have no impact on your system.
PHCO_27797:
( SR:8606269172 CR:JAGae33407 )
Applications that rely upon the ability to su to another
user and pass along certain environment variables,
including but not limited to SHLIB_PATH, do not work.
Defect Description:
PHCO_28830:
( SR:8606250483 CR:JAGae16858 )
This patch contains minor enhancements required to enable
the HP-UX Boot Authenticator for non-trusted mode.
Resolution:
Enhancements added to enable Boot Authenticator for
non-trusted mode when this product is configured.
PHCO_27909:
( SR:8606221280 CR:JAGad90414 )
Enhancement request: HP-UX 11.11 does not support shadow
passwords.
Resolution:
This module has been made aware of shadow passwords and
will take the appropriate actions when the HP-UX shadow
password bundle is installed.
PHCO_27797:
( SR:8606269172 CR:JAGae33407 )
By default, the su command does not export the environment
variables LD_LIBRARY_PATH, SHLIB_PATH or LD_PRELOAD to its
children.
Resolution:
security(4) man page has been updated to include a
description for the new optional parameter SU_KEEP_ENV_VARS
which can be used to override the default behavior.
Enhancement:
Yes
PHCO_28830:
A site's security policies may require a user
to authenticate before they can boot the system
into single-user mode. Previously, this feature
was only available on a system that has been
converted to trusted mode. This patch is one
of the several pre-enablement patches that
enable this feature on a system without
converting it to trusted mode.
PHCO_27909:
This patch is one of many pre-enablement patches
for the shadow password feature.
SR:
8606221280 8606250483 8606269172
Patch Files:
OS-Core.ADMN-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/share/man/man1m.Z/pwck.1m
/usr/share/man/man4.Z/passwd.4
OS-Core.CORE-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/share/man/man1.Z/passwd.1
/usr/share/man/man4.Z/security.4
ProgSupport.PAUX-ENG-A-MAN,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/share/man/man3.Z/getspent.3c
SecurityMon.SEC-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/share/man/man1m.Z/pwconv.1m
what(1) Output:
OS-Core.ADMN-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/share/man/man1m.Z/pwck.1m:
None
/usr/share/man/man4.Z/passwd.4:
None
OS-Core.CORE-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/share/man/man1.Z/passwd.1:
None
/usr/share/man/man4.Z/security.4:
None
ProgSupport.PAUX-ENG-A-MAN,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/share/man/man3.Z/getspent.3c:
None
SecurityMon.SEC-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/share/man/man1m.Z/pwconv.1m:
None
cksum(1) Output:
OS-Core.ADMN-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
4057849793 2022 /usr/share/man/man1m.Z/pwck.1m
3545144520 6422 /usr/share/man/man4.Z/passwd.4
OS-Core.CORE-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
3402234985 8307 /usr/share/man/man1.Z/passwd.1
4276792087 5297 /usr/share/man/man4.Z/security.4
ProgSupport.PAUX-ENG-A-MAN,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
2624740820 3397 /usr/share/man/man3.Z/getspent.3c
SecurityMon.SEC-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
2826893491 1979 /usr/share/man/man1m.Z/pwconv.1m
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHCO_27909 PHCO_27797
Equivalent Patches: None
Patch Package Size: 70 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHCO_28830
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_28830.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_28830. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHCO_28830.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_28830.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_28830.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_28830------------------------------------------
Document ID: PHCO_28798
Date Loaded: 20030708
Title: s700_800 11.11 init(1M) cumulative patch
Patch Name: PHCO_28798
Patch Description: s700_800 11.11 init(1M) cumulative patch
Creation Date: 03/04/07
Post Date: 03/07/08
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.ADMN-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
No (superseded patches were critical)
PHCO_27011: HANG
Category Tags:
defect_repair enhancement general_release critical
halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_28798
Symptoms:
PHCO_28798:
( SR:8606250483 CR:JAGae16858 )
No symptom. This is an enhancement request. This patch
is a member of a set of product updates needed to
enable the optional HP-UX Boot Authentication feature
in non-trusted mode. Upon installation, the HP-UX
Boot Authenticator bundle (BOOTAUTH11i) will install
the full set of product updates (including this patch)
to enable the boot authentication feature in non-trusted
mode.
If the HP-UX Boot Authenticator product is not installed,
this patch will have no impact on your system.
PHCO_27011:
( SR:8606204653 CR:JAGad73835 )
init(1m) hangs when two or more processes started
by init die (call exit, etc) at very nearly exactly
the same time.
( SR:8606224172 CR:JAGad93268 )
Console window hangs when the system returns to
multiuser run level 3, from single user mode.
( SR:8606227506 CR:JAGad96564 )
init(1m) behaves unpredictably because of
incorrect use of pwd_shell.
( SR:8606272797 CR:JAGae36904 )
init(1m) is entering SINGLE USER state instead of
initdefault state, without giving proper error
message.
Defect Description:
PHCO_28798:
( SR:8606250483 CR:JAGae16858 )
This patch contains enhancements required to enable
the HP-UX Boot Authenticator for non-trusted mode.
Resolution:
Enhancements added to enable Boot Authenticator for
non-trusted mode when this product is installed and
configured.
PHCO_27011:
( SR:8606204653 CR:JAGad73835 )
init(1m) hangs when two or more processes started
by init die (call exit, etc) at very nearly exactly
the same time. This problem can be reproduced by
making two or more init started processes to die at
same time. This is a problem of race condition, and
lot depends on the current happenings/load, hence
can not be consistently reproduced.
This was because, In case of a race condition( like
two processes dying at same time ) an uninitialized
pointer was getting accessed.
Resolution:
Now the code is changed to address this issue.
It is taken care that, the pointer is properly
initialized before being accessed.
( SR:8606224172 CR:JAGad93268 )
The console window hangs when the system returns to
multiuser of run level 3(init 3) from single user mode.
The problem can be reproduced as follows:
1.Get the console window(win1) on your work station.
2.Get one more root window(win2) of the same system.
3.On root window(win2) type "init s"(to go to single
user mode).
4.Console window displays sysconf file is getting
transferred to root window pty(win2) and hangs
(expected).
5.Root window(win2) will get sysconf file.
6.Type 'init 3' from root window(win2).
7.sysconf file should return back to console window
and back to normal operational mode, however console
window never comes back to normal from HANG
mode(unexpected).
This was because, signal(SIGWINCH) was assigned to
run level 3, so whenever 'init 3' was called,
SIGWINCH is sent to init, but the init was
expecting SIGTRAP to move to run level 3.
Resolution:
Now the condition is changed to check for SIGWINCH
and not SIGTRAP.
( SR:8606227506 CR:JAGad96564 )
init(1m) was behaving unpredictably when the pw_shell
entry for root in /etc/passwd was null or some invalid
shell name with length less than 8.
The problem can be reproduced as follows:
1.Modify the entry for root in /etc/passwd file with
entry corresponding to pw_shell being made null or
some invalid shell name - the length of the shell
path being less than 8.
2.Reboot the system.
3.Bring the system in single user mode.
4.The system should come up properly flahing a warning
about corrupted shell entry. But the system doesn't
behave in expected manner.
When the pw_shell( current shell) entry in /etc/passwd
is null, pw_shell shell was not assigned any memory.
If the pw_shell entry is null or some invalid shell,
init tries to copy the contents of SH2 to pwd_entry
causing a data corruption.
Resolution:
Now the code is changed to make pw_shell point to SH2
in case it is null or some invalid shell.
( SR:8606272797 CR:JAGae36904 )
init(1m) is entering SINGLE USER state, instead of
initdefault state, without giving proper error
message.
init(1m) checks for root entry in /etc/passwd file
while initialization. getspwnam() was called after
getpwnam() without taking the backup of the output
from getpwnam(). The return value of getpwnam() was
used later to check the root entry in /etc/passwd
file. The data was getting corrupted as getspwnam()
internally calls getpwnam() and getpwnam() uses a
static memory. As the data is corrupted, init(1m)
was entering SINGLE USER mode. But error messages
were not there in code to be displayed in this
cases.
The problem can be reproduced as follows:
1. Enter trusted mode ( Use tsconvert )
2. Change the u_pswduser field in
/tcb/files/auth/system/default to any existing or
non-existent user other than root
3. Reboot the system, the init(1m) process will place
the system in single user mode without any message.
The output that gets displayed on the console is as
follows:
-----------------------------------------------------
Memory Information:
physical page size = 4096 bytes,
logical page size = 4096 bytes
Physical: 6291456 Kbytes, lockable:
5784556 Kbytes, available: 5782220 Kbyts
/sbin/ioinitrc:
/sbin/krs_sysinit:
INIT: SINGLE USER MODE
INIT: Running /sbin/sh
#
#
<System is in single user mode>
-----------------------------------------------------
Resolution:
The code of init(1m) is changed to call getspwnam() first
and then getpwnam(). Hence the root entry data is not
corrupted. Also proper error messages are added to be
displayed.
Enhancement:
Yes
PHCO_28798:
A site's security policies may require a user
to authenticate before they can boot the system
into single-user mode. Previously, this feature
was only available on a system that has been
converted to trusted mode. This patch is one
of the several pre-enablement patches that
enable this feature on a system without
converting it to trusted mode.
SR:
8606204653 8606224172 8606227506 8606250483 8606272797
Patch Files:
OS-Core.ADMN-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/share/man/man1m.Z/init.1m
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/init
what(1) Output:
OS-Core.ADMN-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
/usr/share/man/man1m.Z/init.1m:
None
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/init:
init.c $Date: 2003/03/17 04:37:22 $Revision: r11.11/
4 PATCH_11.11 (PHCO_28798)
proctable.c $Date: 2002/10/08 04:09:34 $Revision: r1
1.11/2 PATCH_11.11 (PHCO_27011)
$Revision: (#) init.sbin CUP11.11_BL2003_0407_1 PAT
CH_11.11 PHCO_28798
Mon Apr 7 01:26:20 PDT 2003 $
$ Version_11.11 Mar 31 2003 09:02:37 $
cksum(1) Output:
OS-Core.ADMN-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,
v=HP:
3314332635 6775 /usr/share/man/man1m.Z/init.1m
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
2122257897 311296 /sbin/init
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHCO_27011
Equivalent Patches: None
Patch Package Size: 350 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHCO_28798
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_28798.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_28798. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHCO_28798.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_28798.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_28798.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_28798------------------------------------------
Document ID: PHCO_28797
Date Loaded: 20030708
Title: s700_800 11.11 /sbin/fs/hfs/bcheckrc patch
Patch Name: PHCO_28797
Patch Description: s700_800 11.11 /sbin/fs/hfs/bcheckrc patch
Creation Date: 03/03/31
Post Date: 03/07/08
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_28797
Symptoms:
PHCO_28797:
( SR:8606296840 CR:JAGae60392 )
Unauthorized user may get into single user mode under
some circumstances.
Defect Description:
PHCO_28797:
( SR:8606296840 CR:JAGae60392 )
Unauthorized user may get into single user mode under
some circumstances.
Resolution:
The boot process now is made more robust to always
check users' authorization before starting up a shell
if the boot authentication mechanism is turned on.
Enhancement:
No
SR:
8606296840
Patch Files:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/fs/hfs/bcheckrc
what(1) Output:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/fs/hfs/bcheckrc:
bcheckrc_hfs $Date: 2003/03/17 04:05:41 $Revision: r
11.11/1 PATCH_11.11 (PHCO_28797)
cksum(1) Output:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
1533644334 5862 /sbin/fs/hfs/bcheckrc
Patch Conflicts: None
Patch Dependencies:
s700: 11.11: PHCO_27884
s800: 11.11: PHCO_27884
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 30 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHCO_28797
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_28797.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_28797. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHCO_28797.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_28797.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_28797.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_28797------------------------------------------
Document ID: PHCO_27884
Date Loaded: 20030708
Title: s700_800 11.11 /sbin/initcond cumulative patch
Patch Name: PHCO_27884
Patch Description: s700_800 11.11 /sbin/initcond cumulative patch
Creation Date: 03/03/28
Post Date: 03/07/08
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
SecurityMon.SECURITY,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_27884
Symptoms:
PHCO_27884:
( SR:8606250483 CR:JAGae16858 )
No symptom. This is an enhancement request. This patch
is a member of a set of product updates needed to
enable the optional HP-UX Boot Authentication feature
in non-trusted mode. Upon installation, the HP-UX
Boot Authenticator bundle (BOOTAUTH11i) will install
the full set of product updates (including this patch)
to enable the boot authentication feature in non-trusted
mode.
If the HP-UX Boot Authenticator product is not installed,
this patch will have no impact on your system.
( SR:8606296840 CR:JAGae60392 )
Unauthorized user may get into single user mode under
some circumstances.
Defect Description:
PHCO_27884:
( SR:8606250483 CR:JAGae16858 )
This patch contains minor enhancements required to enable
the HP-UX Boot Authenticator product for non-trusted mode.
Resolution:
Enhancements added to enable Boot Authenticator for
non-trusted mode when this product is installed and
configured.
( SR:8606296840 CR:JAGae60392 )
Unauthorized user may get into single user mode under
some circumstances.
Resolution:
The boot process now is made more robust to always
check users' authorization before starting up a shell
if the boot authentication mechanism is turned on.
Enhancement:
Yes
PHCO_27884:
A site's security policies may require a user
to authenticate before they can boot the system
into single-user mode. Previously, this feature
was only available on a system that has been
converted to trusted mode. This patch is one
of the several pre-enablement patches that
enable this feature on a system without
converting it to trusted mode.
SR:
8606250483 8606296840
Patch Files:
SecurityMon.SECURITY,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/initcond
what(1) Output:
SecurityMon.SECURITY,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/initcond:
initcond.c $Date: 2003/03/27 14:41:21 $Revision: r11
.11/1 PATCH_11.11 (PHCO_27884)
$Revision: (#) initcond.sbin CUP11.11_BL2003_0328_7
PATCH_11.11 PHCO_27884
Fri Mar 28 15:52:44 PST 2003 $
$ Version_11.11 Mar 11 2003 22:50:06 $
cksum(1) Output:
SecurityMon.SECURITY,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
2760542334 282624 /sbin/initcond
Patch Conflicts: None
Patch Dependencies:
s700: 11.11: PHCO_28797 PHCO_28845
s800: 11.11: PHCO_28797 PHCO_28845
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 300 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHCO_27884
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_27884.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_27884. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHCO_27884.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_27884.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_27884.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_27884------------------------------------------
Document ID: PHCO_29229
Date Loaded: 20030707
Title: s700_800 11.00 Cumulative tar(1) patch
Patch Name: PHCO_29229Patch Description: s700_800 11.00 Cumulative tar(1) patchCreation Date: 03/06/20Post Date: 03/07/07Hardware Platforms - OS Releases: s700: 11.00 s800: 11.00Products: N/AFilesets: OS-Core.CORE-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HPAutomatic Reboot?: NoStatus: General ReleaseCritical: No (superseded patches were critical) PHCO_24633: ABORTCategory Tags: defect_repair enhancement general_release critical halts_systemPath Name: /hp-ux_patches/s700_800/11.X/PHCO_29229
Cust View After Date: 19970101
Category: ITRC
ITRC // HP-UX Software / HP-UX System Administration / sw commands
Patch Name: PHCO_29229Patch Description: s700_800 11.00 Cumulative tar(1) patchCreation Date: 03/06/20Post Date: 03/07/07Hardware Platforms - OS Releases: s700: 11.00 s800: 11.00Products: N/AFilesets: OS-Core.CORE-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HPAutomatic Reboot?: NoStatus: General ReleaseCritical: No (superseded patches were critical) PHCO_24633: ABORTCategory Tags: defect_repair enhancement general_release critical halts_systemPath Name: /hp-ux_patches/s700_800/11.X/PHCO_29229Symptoms: PHCO_29229: ( SR: 8606309652 DTS:JAGae72527 ) Enhancement Request:tar has been enhanced to support backup of files upto 8GB from the earlier 2GB ( SR: 8606312485 DTS: JAGae75301 ) The tar(1) large user-id/group-id enhancements do not work correctly in certain circumstances. Restored files appear to have group ids equivalent to their sizes This problem occurs if: o the archive was created with files that have owners/gro!
ups present in the /etc/passwd and /etc/group files AND o the owner/group ids have numeric values greater than or equal to 2048k AND o the group entry no longer exists in the /etc/group file when the restore operation is performed PHCO_24633: Tar command cannot restore data. Error message is "directory checksum error". PHCO_20028: Enhancements to tar(1) to function with JFS ACLs. PHCO_13542: tar returns an exit code of 0 when it should return nonzero. This is for the case where a nonfatal error occurs, after which tar continues processing the remaining files.Defect Description: PHCO_29229: ( SR: 8606309652 DTS:JAGae72527 ) Enhancement Request: enhance tar(1) to support the archival of files upto 8GB from the current 2GB. Resolution: Modify tar(1) to support large files upto 8GB. ( SR: 8606312485 DTS: JAGae75301 ) tar(1) restores files with incorrect gid. Resolution: When archiving, if the gid value is greater than or equal to 2048k tar used an incorrect format to st!
ore the gid value in the header. The modified tar command uses the cor
rect format to store the gid value in the header. PHCO_24633: ( SR: 8606199103 DTS: JAGad68290 ) Checksum of a file which name has some special characters (e.g., Japanese/Chinese/Korean) might be negative and 11 octal digits long. This could cause over-writing the typeflag (1 byte) and 3 bytes of the linkname in the header of the tar archive. This would modify the header, and the checksum calculated from the modified header does not match the checksum recorded in the archive. This causes the tar command to abort with "directory checksum error". Resolution: We use following methods for this problem: 1) We will use the unsigned file name to calculate the checksum in the tar command. This will prevent the value of checksum from becoming negative and guarantees that archives will not be created containing this error. (2) Try to list/extract the files from the archives containing this error to the greatest degree possible, subject to the following: -- As the mode got from stat(!
2) in the header only recorded 5 octal digits long for old version, if the file is a symbolic link, we cannot differ it from a character device file in some cases. -- As the typeflag has been over-written, if the file is a hard link, we cannot differ it from a regular file in some cases. -- As the linkname has been over-written in the first 3 characters, if the file is a hard or symbolic link, we cannot link it to the target file when extracting. -- We could list/extract fifo, dir and blk types of files from the error archive. PHCO_20028: Enhancements to tar(1) to function with JFS ACLs. PHCO_13542: If tar encounters a nonfatal error while processing a file, it prints an error message and continues processing the remaining files. If at least one such nonfatal error occurs, tar should return a nonzero exit code.Enhancement: Yes PHCO_29229: This product update makes tar(1M) backup files upto 8GBSR: 8606309652 8606312485 8606199103 5003311746 5003396739Patch Files: OS-Core.CO!
RE-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64, v=HP: /usr/share/man/
man1.Z/tar.1 OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: /usr/lib/nls/msg/C/tar.cat /sbin/tar /usr/bin/tarwhat(1) Output: OS-Core.CORE-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64, v=HP: /usr/share/man/man1.Z/tar.1: None OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: /usr/lib/nls/msg/C/tar.cat: None OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: /sbin/tar: $Revision: 82.4.1.6 $ $ PATCH/11.00:PHCO_27731 Oct 11 2002 12:59:13 $ PATCH_11_00: tar.o 03/06/20 OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: /usr/bin/tar: $Revision: 82.4.1.6 $ PATCH_11_00: tar.o 03/06/20cksum(1) Output: OS-Core.CORE-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64, v=HP: 581249620 7186 /usr/share/man/man1.Z/tar.1 OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: 3234233992 3694 /usr/lib/nls/msg/C/tar.cat OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: 1421258265 323584 /sbin/tar OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: 2152316396 !
49152 /usr/bin/tarPatch Conflicts: NonePatch Dependencies: s700: 11.00: PHCO_19491 PHKL_19991 s800: 11.00: PHCO_19491 PHKL_19991Hardware Dependencies: NoneOther Dependencies: NoneSupersedes: PHCO_13542 PHCO_20028 PHCO_24633Equivalent Patches: PHCO_28992: s700: 11.11 s800: 11.11Patch Package Size: 240 KBytesInstallation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHCO_29229 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHCO_29229.depot By default swinstall will!
archive the original software in /var/adm/sw/save/PHCO_29229. If you
do not wish to retain a copy of the original software, include the patch_save_files option in the swinstall command above: -x patch_save_files=false WARNING: If patch_save_files is false when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. For future reference, the contents of the PHCO_29229.text file is available in the product readme: swlist -l product -a readme -d /tmp/PHCO_29229.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHCO_29229.depot of=/dev/rmt/0m bs=2kSpecial Installation Instructions: None
-----End of Document ID: PHCO_29229------------------------------------------
Document ID: PHCO_29108
Date Loaded: 20030707
Title: s700_800 11.00 Pthread library cumulative patch
Patch Name: PHCO_29108
Patch Description: s700_800 11.00 Pthread library cumulative patch
Creation Date: 03/06/26
Post Date: 03/07/07
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
OS-Core.C-MIN-32ALIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
OS-Core.C-MIN-64ALIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
OS-Core.CORE-64SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
OS-Core.CORE-SHLIBS,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
Yes
PHCO_29108: HANG
PHCO_26960: ABORT
PHKL_17935: ABORT
This defect could result in an application core
dump.
PHKL_17709: ABORT
This defect could result in an application hang.
Category Tags:
defect_repair enhancement general_release critical
halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_29108
Symptoms:
PHCO_29108:
( SR:8606307008 CR:JAGae70043 )
Java processes can hang occasionally.
( SR:8606294128 CR:JAGae57868 )
Thread can get cancelled even though cancellation is
disabled.
( SR:8606314230 CR:JAGae77005 )
The pthread library does not export two functions that are
useful to the Java virtual machine.
PHCO_26960:
( SR:8606245135 CR:JAGae11610 )
Application fails with internal error in pthread library
when the kernel patch that implements a new light weight
syscall is not applied.
( SR:8606249251 CR:JAGae15645 )
Application aborts when a detached thread forks child
process.
( SR:8606232793 CR:JAGae02021 )
Private mutex lock throughput not acceptable for some
applications with heavy mutex contention.
( SR:8606255251 CR:JAGae19578 )
pthread_cancel() fails to cancel a thread in certain
conditions.
( SR:8606259437 CR:JAGae23755 )
pthread_mutex_destroy() intermittently returns EBUSY
even when there are no threads accessing the mutex.
PHCO_26000:
( SR:8606186056 CR:JAGad55261 )
Software providers may observe performance deficiencies in
applications which heavily use shared mutexes. Performance
of a PTHREAD_PROCESS_SHARED mutex unlock operation is slower
than that of a PTHREAD_PROCESS_PRIVATE mutex, even in the
non-contended (i.e., no waiters) case.
PHCO_23792:
libpthread didn't support initialized TLS variables.
PHCO_19666:
Libc was unable to use thread callbacks, which are needed
for multithreaded performance enhancements.
JAGab19980
PHKL_17935:
SR: 1653296962 CR: JAGaa94129
An application that calls pthread_create() can terminate
with the following error when running on a system with heavy
memory usage:
Pthread internal error: message: __alloc_stack()
PHKL_17709:
When calling pthread_[cond,mutex,rwlock]_init(), subsequent
use of these objects can cause the process or thread to hang
if the error is not properly checked, or structures
associated with these routines are not properly initialized.
PHKL_17294:
If you have installed Patch PHKL_17390 and you use java and
the pthread asynchronous cancellation feature you may
experience incorrect program behavior -- possible program
aborts, hangs, etc.
If you do not use the pthreads asynchronous cancellation
feature, this patch is not required.
PHKL_16239:
SCHED_TIMESHARE thread priorities degrade over time and with
cpu usage. SCHED_NOAGE provides a scheduling policy where
the priority does not degrade.
In order to utilize the SCHED_NOAGE feature, patch
PHKL_16236 must be installed along with PHKL_16239. The
order of installation is not important. If this feature
will not be used, PHKL_16236 is not necessary.
PHKL_16368:
System peformance degrades when thread spinlock contention
occurs.
libpthread enhancement to improve thread spinlock
performance and overall system performance by lowering the
amount of bus traffic during spinlock contention.
Defect Description:
PHCO_29108:
( SR:8606307008 CR:JAGae70043 )
During normal operation, the Java Virtual Machine may
suspend a thread. When a thread gets suspended, it
could be holding internal pthread resources. This can
cause a deadlock.
Resolution:
Solution is to ensure target does not get suspended while
holding internal pthread resources.
( SR:8606294128 CR:JAGae57868 )
The cancellation operation (pthread_cancel) can race with
cancel enable/disable (pthread_setcancelstate).
Resolution:
While cancelling a thread, detect that the thread has now
disabled cancellation.
( SR:8606314230 CR:JAGae77005 )
The pthread library does not export two functions that are
useful to the Java virtual machine.
Resolution:
libpthread will now export the two symbols
PHCO_26960:
( SR:8606245135 CR:JAGae11610 )
If SIGSYS is ignored by the application, the sigtimedwait()
system call finds no pending SIGSYS after the check for
new light weight system call fails with ENOSYS. This
results in pthread internal error because SIGSYS was
expected.
Resolution:
The check for new syscall is aptly handled so that
internal error doesn't occur.
( SR:8606249251 CR:JAGae15645 )
In the child process forked from a detached thread, the
first thread in the exit path references a stale pointer.
This results in application aborting in pthread library.
Resolution:
The stale pointer is reset in the child fork cleanup path.
( SR:8606232793 CR:JAGae02021 )
When large number of threads contend for a mutex, it
results in contention for the internal lock of the
mutex, thereby exacerbating the mutex contention seen by
the application.
Resolution:
The pthread mutex unlock path has been modified to release
internal lock before waking up a waiting thread, and thus
reducing contention for the internal lock and improving
performance.
The performance changes can take effect only if the POSIX
real-time restrictions on threads waiting on a mutex are
relaxed. This is done by disabling the mutex handoff
mode for real-time threads and can be done using
pthread_mutex_disable_handoff_np() or
pthread_mutexattr_disable_handoff_np() or by setting the
environment variable PTHREAD_DISABLE_HANDOFF=ON. By
default these performance changes are disabled.
The first API pthread_mutex_disable_handoff_np() is for
process wide disabling of handoff mode in all mutexes.
So is the environment variable PTHREAD_DISABLE_HANDOFF.
The pthread_mutexattr_disable_handoff_np() takes an
argument pointer to pthread_mutexattr_t and can be used
to disable handoff mode for a particular mutex.
The pthread_mutex_disable_handoff_np() has no arguments
and has to be called by the main thread before any new
threads are created.
"Handoff mode" is used to strictly adhere to POSIX
real-time characteristics, when real-time threads
waiting on a mutex are woken up. If the application
does not have any real-time threads acquiring mutex
locks, or if the application does not rely on strict
real-time behavior of real-time threads waiting on
a mutex, the mutex handoff mode can be disabled, to
take advantage of these performance changes.
( SR:8606255251 CR:JAGae19578 )
There is a race condition in thread cancellation path in
pthread library, because of which pthread_cancel() fails
to cancel a thread.
Resolution:
The race condition in the cancellation path is removed
by protecting the internal cancellation structure with
a spinlock.
( SR:8606259437 CR:JAGae23755 )
The problem with pthread_mutex_destroy() is attributed
to the fact that, pthread_mutex_unlock() does not keep
track of the number of waiters accurately. The mutex
cannot be destroyed when there are waiters, and hence
EBUSY is returned by pthread_mutex_destroy().
Resolution:
The change introduced in this patch will accurately
keep track of all the waiters.
PHCO_26000:
( SR:8606186056 CR:JAGad55261 )
In the PTHREAD_PROCESS_SHARED mutex case, the unlock
operation always makes a system call to synchronize with
threads in other processes which may be waiting for the
mutex. This makes the code path significantly longer.
Resolution:
Change pthread_mutex_unlock(), in the case of a shared
mutex, to call a new light weight system call rather than
the existing system call. If that new system call is not
available, then use the regular system call instead.
(Patch PHKL_25998, also required for this enhancement,
adapts the existing system call which handles waiters of
shared mutexes to coordinate with the light weight unlock
system call. Patch PHKL_25999, also required for this
enhancement, provides the new light weight system call
for shared mutex unlock.)
PHCO_23792:
Initialized TLS variable support.
PHCO_19666:
Multithreaded performance enhancement
JAGab19980
PHKL_17935:
SR: 1653296962 CR: JAGaa94129
The pthread_create() path uses mmap() to allocate a stack.
pthread_create() checks for a NULL return. However, mmap()
returns MAP_FAILED if it cannot perform the allocation.
Typically what happens is that the subsequent mprotect()
will fail to setup the guard page, then munmap() fails when
trying to clean up on the error return path, generating an
"INTERNAL ERROR" message and a core dump from the library.
Also, since the mmap() failure check passes even if it fails
(we're not looking for the correct return value),
pthread_create() doesn't return an error. Instead, it
terminates with "INTERNAL ERROR."
Resolution:
pthread_create() now checks for MAP_FAILED and returns the
error instead of failing with "INTERNAL ERROR.".
PHKL_17709:
Structures associated with
pthread_[cond,mutex,rwlock]_init() are not being initialized
correctly. This causes a call to these routines to return
EBUSY.
Resolution:
We no longer check for "cookie" values to validate these
objects. We unconditionally initialize them.
PHKL_17294:
A kernel interface change required that we save a register
in a new location when the application enters the kernel via
the trap path. The kernel change was made in patch
PHKL_17390.
Resolution: The pthreads library must now look in the new
location for the register value in this case.
PHKL_16239:
The SCHED_NOAGE scheduling policy has approximately the same
priority range as SCHED_TIMESHARE. However, the priority
does not degrade with time or cpu usage. It provides an
alternative to real time processes which always run first
and have the possibility of taking over the system.
PHKL_16368:
The thread library spinlock did not take advantage of the
cached lock value. In addition, it performed an unnecessary
fetch each time through the 'spin' loop while waiting for
the lock to be free. These conditions caused a large amount
of unnecessary bus traffic.
Enhancement:
No (superseded patches contained enhancements)
PHCO_29108:
Enhancements were delivered in a patch this one has
superseded. Please review the Defect Description
text for more information.
SR:
1653294868 1653296962 4701401240 5003360446 5003451591
8606184540 8606186056 8606232793 8606245135 8606249251
8606255251 8606259437 8606294128 8606307008 8606314230
Patch Files:
OS-Core.C-MIN-32ALIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/libpthread.a
/usr/lib/libpthread_tr.a
OS-Core.C-MIN-64ALIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/pa20_64/libpthread.a
/usr/lib/pa20_64/libpthread_tr.a
OS-Core.CORE-64SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/pa20_64/libpthread.1
/usr/lib/pa20_64/libpthread_tr.1
OS-Core.CORE-SHLIBS,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/libpthread.1
/usr/lib/libpthread_tr.1
what(1) Output:
OS-Core.C-MIN-32ALIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/libpthread.a:
libpthread.c $Date: 2003/03/17 22:55:08 $Revision: r
11ros/10 PATCH_11.00 (PHCO_28792)
Pthread Interfaces
libpthread HP-UX (Release B.11.00): Thu Jul 5 15:26
:11 PDT 2001
/usr/lib/libpthread_tr.a:
libpthread.c $Date: 2003/03/17 22:55:08 $Revision: r
11ros/10 PATCH_11.00 (PHCO_28792)
Pthread Interfaces
libpthread HP-UX (Release B.11.00): Thu Jul 5 15:26
:46 PDT 2001
OS-Core.C-MIN-64ALIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/pa20_64/libpthread.a:
libpthread.c $Date: 2003/03/17 22:55:08 $Revision: r
11ros/10 PATCH_11.00 (PHCO_28792)
Pthread Interfaces
libpthread HP-UX (Release B.11.00): Thu Jun 7 11:32
:26 PDT 2001
/usr/lib/pa20_64/libpthread_tr.a:
libpthread.c $Date: 2003/03/17 22:55:08 $Revision: r
11ros/10 PATCH_11.00 (PHCO_28792)
Pthread Interfaces
libpthread HP-UX (Release B.11.00): Thu Jun 7 11:33
:01 PDT 2001
OS-Core.CORE-64SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/pa20_64/libpthread.1:
Pthread Interfaces
libpthread HP-UX (Release B.11.00): Thu Jun 7 11:32
:39 PDT 2001
libpthread.c $Date: 2003/03/17 22:55:08 $Revision: r
11ros/10 PATCH_11.00 (PHCO_28792)
/usr/lib/pa20_64/libpthread_tr.1:
Pthread Interfaces
libpthread HP-UX (Release B.11.00): Thu Jun 7 11:33
:13 PDT 2001
libpthread.c $Date: 2003/03/17 22:55:08 $Revision: r
11ros/10 PATCH_11.00 (PHCO_28792)
OS-Core.CORE-SHLIBS,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/libpthread.1:
libpthread.c $Date: 2003/03/17 22:55:08 $Revision: r
11ros/10 PATCH_11.00 (PHCO_28792)
Pthread Interfaces
libpthread HP-UX (Release B.11.00): Thu Jul 5 15:26
:27 PDT 2001
/usr/lib/libpthread_tr.1:
libpthread.c $Date: 2003/03/17 22:55:08 $Revision: r
11ros/10 PATCH_11.00 (PHCO_28792)
Pthread Interfaces
libpthread HP-UX (Release B.11.00): Thu Jul 5 15:26
:57 PDT 2001
cksum(1) Output:
OS-Core.C-MIN-32ALIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
2619357963 229706 /usr/lib/libpthread.a
504375935 259502 /usr/lib/libpthread_tr.a
OS-Core.C-MIN-64ALIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
592423104 379110 /usr/lib/pa20_64/libpthread.a
3078287244 432316 /usr/lib/pa20_64/libpthread_tr.a
OS-Core.CORE-64SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
132451524 135760 /usr/lib/pa20_64/libpthread.1
950904832 165064 /usr/lib/pa20_64/libpthread_tr.1
OS-Core.CORE-SHLIBS,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
1753090745 143360 /usr/lib/libpthread.1
285260085 167936 /usr/lib/libpthread_tr.1
Patch Conflicts: None
Patch Dependencies:
s700: 11.00: PHKL_17390
s800: 11.00: PHKL_17390
Hardware Dependencies: None
Other Dependencies:
PHCO_26000: To enable the pthread shared mutex performance
enhancement, three patches (PHKL_25998, PHKL_25999, and
PHCO_26000) are required. To enable the TLS feature, the
following patches should also be installed: PHCO_24148 libc
cumulative patch PHSS_23440 linker cumulative patch
PHSS_23785 linker startup patch PHSS_23953 Fortran90 B.11.01
patch
Supersedes:
PHKL_17935 PHKL_17709 PHKL_17294 PHKL_16368 PHKL_16239 PHCO_26960
PHCO_26000 PHCO_23792 PHCO_19666
Equivalent Patches:
PHCO_29109:
s700: 11.11
s800: 11.11
Patch Package Size: 1920 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHCO_29108
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_29108.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_29108. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHCO_29108.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_29108.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_29108.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_29108------------------------------------------
Document ID: PHNE_28993
Date Loaded: 20030707
Title: s700_800 11.22 intl100 driver patch
Patch Name: PHNE_28993
Patch Description: s700_800 11.22 intl100 driver patch
Creation Date: 03/06/09
Post Date: 03/07/07
Hardware Platforms - OS Releases:
s700: 11.22
s800: 11.22
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_28993
Symptoms:
PHNE_28993:
( SR:8606280822 CR:JAGae44791 )
Setting the speed/duplex value of intl100 driver and the
switch to 100FD or 10FD, results in poor link performance.
( SR:8606298261 CR:JAGae61761 )
Applications like EMS monitors are unable to get the
interface name for intl100 interfaces.
( SR:8606267305 CR:JAGae31547 )
lanadmin(1M) shows different MAC addresses in
command line interface mode and menu mode for intl100
interface, when its MAC address is changed using SAM or
lanadmin(1M).
PHNE_28789:
( SR:8606280822 CR:JAGae44791 )
Setting the speed/duplex value of intl100 driver and the
switch to 100FD or 10FD, results in poor link performance.
( SR:8606298261 CR:JAGae61761 )
Applications like EMS monitors are unable to get the
interface name for intl100 interfaces.
( SR:8606267305 CR:JAGae31547 )
lanadmin(1M) shows different MAC addresses in
command line interface mode and menu mode for intl100
interface, when its MAC address is changed using SAM or
lanadmin(1M).
Defect Description:
PHNE_28993:
( SR:8606280822 CR:JAGae44791 )
The driver did a PHY reset immediately after setting the
speed/duplex value. This resulted in the PHY returning to
auto-negotiation mode and losing the new speed/duplex
setting. So when the switch and interface card were set
to 100FD or 10FD, the interface operated as if in
half-duplex mode. This resulted in poor link performance.
Resolution:
Code has been modified to change the way the PHY reset is
done, so that the new speed/duplex value is preserved.
( SR:8606298261 CR:JAGae61761 )
The intl100 driver did not store the interface name
in the ifDescr field of its MIB structure.
Hence, applications like EMS monitors could not get the
intl100 driver's interface name.
Resolution:
The ifDescr field in intl100 driver's MIB structure is
updated with the interface name.
( SR:8606267305 CR:JAGae31547 )
When the MAC address is changed through SAM or lanadmin(1M),
the intl100 driver updates only its internal structure
and does not update its MIB structure with the new MAC
address. The lanadmin(1M) in command line interface mode
gets the MAC address from driver's internal structure
and the lanadmin(1M) in menu mode gets the MAC address
from the driver's MIB structure. Hence the lanadmin(1M) in
menu mode and command line interface mode shows different
MAC addresses.
Resolution:
The intl100 driver code is modified to update both its
internal structure and its MIB structure with the new
MAC address, whenever the MAC address is changed.
PHNE_28789:
( SR:8606280822 CR:JAGae44791 )
The driver did a PHY reset immediately after setting the
speed/duplex value. This resulted in the PHY returning to
auto-negotiation mode and losing the new speed/duplex
setting. So when the switch and interface card were set
to 100FD or 10FD, the interface operated as if in
half-duplex mode. This resulted in poor link performance.
Resolution:
Code has been modified to change the way the PHY reset is
done, so that the new speed/duplex value is preserved.
( SR:8606298261 CR:JAGae61761 )
The intl100 driver did not store the interface name
in the ifDescr field of its MIB structure.
Hence, applications like EMS monitors could not get the
intl100 driver's interface name.
Resolution:
The ifDescr field in intl100 driver's MIB structure is
updated with the interface name.
( SR:8606267305 CR:JAGae31547 )
When the MAC address is changed through SAM or lanadmin(1M),
the intl100 driver updates only its internal structure
and does not update its MIB structure with the new MAC
address. The lanadmin(1M) in command line interface mode
gets the MAC address from driver's internal structure
and the lanadmin(1M) in menu mode gets the MAC address
from the driver's MIB structure. Hence the lanadmin(1M) in
menu mode and command line interface mode shows different
MAC addresses.
Resolution:
The intl100 driver code is modified to update both its
internal structure and its MIB structure with the new
MAC address, whenever the MAC address is changed.
Enhancement:
No
SR:
8606267305 8606280822 8606298261
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
/usr/conf/lib/libintl100.a
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
/usr/conf/lib/libintl100.a:
intl100.c $Date: 2003/04/16 22:10:03 $Revision: r11.
22/2 PATCH_11.22 (PHNE_28993)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
1555942814 204660 /usr/conf/lib/libintl100.a
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_28789
Equivalent Patches: None
Patch Package Size: 90 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHNE_28993
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_28993.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_28993. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHNE_28993.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_28993.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_28993.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHNE_28993------------------------------------------
Document ID: PHNE_29032
Date Loaded: 20030707
Title: s700_800 11.00 FTAM9000 E.06.01 patch
Patch Name: PHNE_29032
Patch Description: s700_800 11.00 FTAM9000 E.06.01 patch
Creation Date: 03/06/15
Post Date: 03/07/07
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
FTAM9000 E.06.01
Filesets:
FTAM9000.FTAM,fr=E.06.01,fa=HP-UX_B.11.00_32/64,v=HP
FTAM9000.FTAM_64,fr=E.06.01,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
Yes
PHNE_29032: MEMORY_LEAK ABORT HANG
Category Tags:
defect_repair general_release critical halts_system
memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_29032
Symptoms:
PHNE_29032:
1.JAGae64015 (SR8606300546)
FTAM performance is low.
2.JAGae37830 (SR8606273742)
FTAM resp leaks memory when NetTL is enabled.
3.JAGae16872 (SR8606250497)
FTAM resp dies due to AP_AGAIN error returned by
ap_set_env() API.
4.JAGad95212 (SR8606226141)
FTAM Applications fail due to total number of
opened file reached the maximum limit.
5.JAGad57081 (SR8606187872)
Incorrect NetTL message logged when FTAM Service
provider is unavailable.
6.JAGad54632 (SR8606185439)
ft_fmove() dumps core when API trace is enabled.
7.JAGad54642 (SR8606185449)
ft_frattributes() dumps core when API trace is enabled.
8.JAGad54485 (SR8606185283)
ft_frattributes_aet() dumps core when API trace is
enabled.
9.JAGad54054 (SR8606184848)
ft_fmove_aet() dumps core when API trace is enabled.
10.JAGad37961 (SR8606168683)
"fcp loginremote:/file -X loginmachine:/file -X"
command gives the following error
"Abnormal termination.
Message from machine:
Could not decode PDU (log_instance:XXXX,
FTAM error_id 1006 = "Unsupported parameter types")"
11.JAGad95235 (SR8606226164)
FTAM Applications using only synchronous low level
APIs fail with PROTOCOL ERROR.
12.JAGad46194 (SR8606176959)
FTAM hangs when sending ACSE AARQ-PDU which has
optional field calling-AE-invocation-identifier.
13.JAGad49767 (SR8606180546)
FTAM application returns without any error in DATA
transfer regime.
Defect Description:
PHNE_29032:
1.JAGae64015 (SR8606300546)
FTAM resp performance is low due to the sleep(1) in
AP_recv_prim() when ap_rcv() returns AP_AGAIN.
Resolution:
Now whenever ap_rcv() fails with AP_AGAIN error,
AP_recv_prim() poll on the file descriptor using
ap_poll() for a few milliseconds, which is configurable
using "/etc/opt/ftam/conf/ftam_conf".
AP_POLL_TIME - Amount of time(ms) to poll.
AP_POLL_RTRYC - Number of times to poll.
If ap_poll() doesn't succeed with data availability,
AP_recv_prim() goes for sleep(). The sleep time is also
configurable using "/etc/opt/ftam/conf/ftam_conf"
AP_RCV_USLP - Upper mark value of seconds for sleep.
AP_RCV_LSP - Lower mark value of seconds for sleep.
The configurable parameters mentioned above should only
be modified by HP representative.
2.JAGae37830 (SR8606273742)
When NetTL is enabled the buffer allocated to hold the
PDU is not freed.
Resolution:
The code has been modified to free the buffer.
3.JAGae16872 (SR8606250497)
When ap_set_env() returns AP_AGAIN error, FTAM code
has to retry the ap_set_env() again. The code is killing
ftam_resp daemon if FTAM resp gets AP_AGAIN error from
ap_set_env(). Ideally FTAM code should have retried
the same ap_set_env().
Resolution:
The code has been modified to retry ap_set_env().
4.JAGad95212 (SR8606226141)
vi_conc_print_debug() function opens a file in FTAM.
The opened file is not properly closed by
vi_conc_print_debug().
Resolution:
The code has been modified to close the opened file.
5.JAGad57081 (SR8606187872)
When FTAM service provider is not available, the NetTL
message logged by FTAM is:
"(MSGE_NO_ADDRS) Unable to create an IPC call socket
address because the call socket directory
'/usr/spool/sockets/osi' does not exist. Create the
call socket directory with the following permissions.
/usr bin bin 555
/usr/spool bin bin 555
/usr/spool/sockets bin bin 555
/usr/spool/sockets/osi bin bin 777"
The paths described in this error message are not
relevant to HP-UX greater than 9.x. The correct paths
are:
/var/opt bin bin 555
/var/opt/ftam bin bin 555
/var/opt/ftam/spool bin bin 555
/var/opt/ftam/spool/sockets bin bin 777
Resolution:
The error message has been changed to
"(MSGE_NO_ADDRS) Unable to create an IPC call socket
address because the call socket directory
'/var/opt/ftam/spool/sockets' does not exist. Create the
call socket directory with the following permissions.
/var/opt/ bin bin 555
/var/opt/ftam bin bin 555
/var/opt/ftam/spool bin bin 555
/var/opt/ftam/spool/sockets bin bin 777"
6.JAGad54632 (SR8606185439)
If API trace is enabled, then the parameter passed to
print_file_passwords() by ft_fmove() API is not
correct.
The print_file_passwords() dumps core when it tries to
access the incorrect parameter passed to it.
Resolution:
The code has been changed to pass the correct parameter
to print_file_passwords().
7.JAGad54642 (SR8606185449)
If API trace is enabled, ft_frattributes() API uses
fprintf() to print Octet string. Ideally it should have
used print_single_file_pw() function to print the
Octet string.
Resolution:
The code has been changed to use print_single_file_pw()
to print the string.
8.JAGad54485 (SR8606185283)
If API trace is enabled, ft_frattributes_aet() API uses
fprintf() to print Octet string. Ideally it should have
used print_single_file_pw() function to print the
Octet string.
Resolution:
The code has been changed to use print_single_file_pw()
to print the string.
9.JAGad54054 (SR8606184848)
If API trace is enabled, then the parameter passed to
print_file_passwords() by ft_fmove_aet() API is not
correct.
The print_file_passwords() dumps core when it tries to
access the incorrect parameter passed to it.
Resolution:
The code has been changed to pass the correct parameter
to print_file_passwords().
10.JAGad37961 (SR8606168683)
FTAM INIT has a global variable containing the document
types requested on a connect request. When FTAM INIT
gets connect response, this variable is used to compare
with the connect response's document types.
The variable is not filled; if it is a second connect
request. If the response has more document type than
requested, the code which checks for document type
compatibility gives error.
Resolution:
The code has been modified to maintain a list of
connection-id/document type masks. When a connect
request/response is made, a new node is added/removed to
the list.
11.JAGad95235 (SR8606226164)
While processing the close request, FTAM responder
calls f_close_ind twice. The second invocation of
f_close_ind() puts the FTAM Responder in inconsistent
state and generates the protocol error.
Resolution:
The code has been modified to remove the second
invocation of f_close_ind().
12.JAGad46194 (SR8606176959)
Some implementaions of FTAM does not support
calling-AE-invocation-identifier field since it is
optional. Because of this interoperable issue, FTAM
hangs.
Resolution:
A new flag CALLING_AE_INV_ID_FLAG has been added in
ftam_conf file. If the flag is set/unset, then FTAM
would enable/disable calling-AE-invocation-identifier
field in ACSE AARQ-PDU.
13.JAGad49767 (SR8606180546)
If a FTAM application is in DATA transfer regime and
OTS is stopped on remote system, then FTAM returns
without any error.
Resolution :
The code has been modified to return error.
Enhancement:
No
SR:
8606300546 8606273742 8606250497 8606226141 8606187872
8606185439 8606185449 8606185283 8606184848 8606168683
8606226164 8606176959 8606180546
Patch Files:
FTAM9000.FTAM,fr=E.06.01,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/ftam/lbin/ftam_init
/opt/ftam/lbin/ftam_resp
/etc/opt/ftam/conf/ftam_conf
/opt/ftam/lib/nls/C/fmt124f.cat
/opt/ftam/shlib/libfmt124f.sl
/opt/ftam/lib/libmapftam.a
/opt/ftam/shlib/libmapftam.3
/opt/ftam/bin/ftam
/opt/ftam/README.FTAM.E.06.01
FTAM9000.FTAM_64,fr=E.06.01,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/ftam/shlib/pa20_64/libmapftam.0
/opt/ftam/lib/pa20_64/libmapftam.a
what(1) Output:
FTAM9000.FTAM,fr=E.06.01,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/ftam/lbin/ftam_init:
FTAM: PHNE_29032 03/06/17 s800 ftam_init
/opt/ftam/lbin/ftam_resp:
FTAM: PHNE_29032 03/06/17 s800 ftam_resp
/etc/opt/ftam/conf/ftam_conf:
FTAM Configuration file
/opt/ftam/lib/nls/C/fmt124f.cat:
MAP30: C.X5.01 $Date: 94/03/28 19:13:31 $
/opt/ftam/shlib/libfmt124f.sl:
MAP30: C.X5.01 $Date: 94/03/28 19:13:31 $
/opt/ftam/lib/libmapftam.a:
FTAM: PHNE_29032 03/06/17 s800 libmapftam.a
/opt/ftam/shlib/libmapftam.3:
FTAM: PHNE_29032 03/06/17 s800 libmapftam.sl
/opt/ftam/bin/ftam:
FTAM: PHNE_29032 03/06/17 s800 ftam
FTAM: PHNE_29032 03/06/17 s800 libmapftam.a
/opt/ftam/README.FTAM.E.06.01:
None
FTAM9000.FTAM_64,fr=E.06.01,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/ftam/shlib/pa20_64/libmapftam.0:
FTAM: PHNE_29032 03/06/17 s800 libmapftam.sl
/opt/ftam/lib/pa20_64/libmapftam.a:
FTAM: PHNE_29032 03/06/17 s800 libmapftam.a
cksum(1) Output:
FTAM9000.FTAM,fr=E.06.01,fa=HP-UX_B.11.00_32/64,v=HP:
1793242209 1216512 /opt/ftam/lbin/ftam_init
1236000673 1101824 /opt/ftam/lbin/ftam_resp
2809738387 5464 /etc/opt/ftam/conf/ftam_conf
2337109310 25767 /opt/ftam/lib/nls/C/fmt124f.cat
3147527071 98304 /opt/ftam/shlib/libfmt124f.sl
4098855404 611228 /opt/ftam/lib/libmapftam.a
2304484738 786432 /opt/ftam/shlib/libmapftam.3
3929455468 696320 /opt/ftam/bin/ftam
1139273083 1257 /opt/ftam/README.FTAM.E.06.01
FTAM9000.FTAM_64,fr=E.06.01,fa=HP-UX_B.11.00_32/64,v=HP:
3831655951 504424 /opt/ftam/shlib/pa20_64/libmapftam.0
3408725050 978348 /opt/ftam/lib/pa20_64/libmapftam.a
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 1610 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHNE_29032
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_29032.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_29032. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHNE_29032.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_29032.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_29032.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHNE_29032------------------------------------------
Document ID: PHNE_29033
Date Loaded: 20030707
Title: s700_800 11.11 FTAM9000 E.07.00 cumulative patch
Patch Name: PHNE_29033
Patch Description: s700_800 11.11 FTAM9000 E.07.00 cumulative patch
Creation Date: 03/06/12
Post Date: 03/07/07
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products:
FTAM9000 E.07.00
Filesets:
FTAM9000.FTAM,fr=E.07.00,fa=HP-UX_B.11.11_32/64,v=HP
FTAM9000.FTAM_64,fr=E.07.00,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
Yes
PHNE_29033: MEMORY_LEAK ABORT
Category Tags:
defect_repair general_release critical halts_system
memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_29033
Symptoms:
PHNE_29033:
1. JAGae64015 (SR8606300546):
FTAM performance is low.
2. JAGae37830 (SR8606273742):
FTAM resp leaks memory when NetTL is enabled.
3. JAGae16872 (SR8606250497):
FTAM resp dies due to AP_AGAIN error returned by
ap_set_env() API.
4. JAGad95212 (SR8606226141)
FTAM Applications fail due to total number of
opened file reached the maximum limit.
5. JAGad95235 (SR8606226164)
FTAM Applications using only synchronous low level
APIs fail with PROTOCOL ERROR.
6. JAGad57081 (SR8606187872):
Incorrect NetTL message logged when FTAM Service
provider is unavailable.
7. JAGad54632 (SR8606185439):
ft_fmove() dumps core when API trace is enabled.
8. JAGad54642 (SR8606185449):
ft_frattributes() dumps core when API trace is enabled.
9. JAGad54485 (SR8606185283):
ft_frattributes_aet() dumps core when API trace is
enabled.
10.JAGad54054 (SR8606184848):
ft_fmove_aet() dumps core when API trace is enabled.
11.JAGad49767 (SR8606180546)
FTAM application returns without any error in DATA
transfer regime.
Defect Description:
PHNE_29033:
1. JAGae64015 (SR8606300546):
FTAM resp performance is low due to the sleep(1) in
AP_recv_prim() when ap_rcv() returns AP_AGAIN.
Resolution:
Now whenever ap_rcv() fails with AP_AGAIN error,
AP_recv_prim() poll on the file descriptor using
ap_poll() for a few milliseconds, which is configurable
using "/etc/opt/ftam/conf/ftam_conf".
AP_POLL_TIME - Amount of time(ms) to poll.
AP_POLL_RTRYC - Number of times to poll.
If ap_poll() doesn't succeed with data availability,
AP_recv_prim() goes for sleep(). The sleep time is also
configurable using "/etc/opt/ftam/conf/ftam_conf"
AP_RCV_USLP - Upper mark value of seconds for sleep.
AP_RCV_LSP - Lower mark value of seconds for sleep.
The configurable parameters mentioned above should only
be modified by HP representative.
2. JAGae37830 (SR8606273742):
When NetTL is enabled the buffer allocated to hold the
PDU is not freed.
Resolution:
The code has been modified to free the buffer.
3. JAGae16872 (SR8606250497):
When ap_set_env() returns AP_AGAIN error, FTAM code
has to retry the ap_set_env() again. The code is killing
ftam_resp daemon if FTAM resp gets AP_AGAIN error from
ap_set_env(). Ideally FTAM code should have retried
the same ap_set_env().
Resolution:
The code has been modified to retry ap_set_env().
4. JAGad95212 (SR8606226141):
vi_conc_print_debug() function opens a file in FTAM.
The opened file is not properly closed by
vi_conc_print_debug().
Resolution:
The code has been modified to close the opened file.
5. JAGad95235 (SR8606226164)
While processing the close request, FTAM responder calls
f_close_ind twice. The second invocation of f_close_ind()
puts the FTAM Responder in inconsistent state and
generates the protocol error.
Resoultion:
The code has been modified to remove the second
invocation of f_close_ind().
6. JAGad57081 (SR8606187872):
When FTAM service provider is not available, the NetTL
message logged by FTAM is:
"(MSGE_NO_ADDRS) Unable to create an IPC call socket
address because the call socket directory
'/usr/spool/sockets/osi' does not exist. Create the
call socket directory with the following permissions.
/usr bin bin 555
/usr/spool bin bin 555
/usr/spool/sockets bin bin 555
/usr/spool/sockets/osi bin bin 777"
The paths described in this error message are not
relevant to HP-UX greater than 9.x. The correct paths
are:
/var/opt bin bin 555
/var/opt/ftam bin bin 555
/var/opt/ftam/spool bin bin 555
/var/opt/ftam/spool/sockets bin bin 777
Resolution:
The error message has been changed to
"(MSGE_NO_ADDRS) Unable to create an IPC call socket
address because the call socket directory
'/var/opt/ftam/spool/sockets' does not exist. Create the
call socket directory with the following permissions.
/var/opt/ bin bin 555
/var/opt/ftam bin bin 555
/var/opt/ftam/spool bin bin 555
/var/opt/ftam/spool/sockets bin bin 777"
7. JAGad54632 (SR8606185439):
If API trace is enabled, then the parameter passed to
print_file_passwords() by ft_fmove() API is not
correct.
The print_file_passwords() dumps core when it tries to
access the incorrect parameter passed to it.
Resolution:
The code has been changed to pass the correct parameter
to print_file_passwords().
8. JAGad54642 (SR8606185449):
If API trace is enabled, ft_frattributes() API uses
fprintf() to print Octet string. Ideally it should have
used print_single_file_pw() function to print the
Octet string.
Resolution:
The code has been changed to use print_single_file_pw()
to print the string.
9. JAGad54485 (SR8606185283):
If API trace is enabled, ft_frattributes_aet() API uses
fprintf() to print Octet string. Ideally it should have
used print_single_file_pw() function to print the
Octet string.
Resolution:
The code has been changed to use print_single_file_pw()
to print the string.
10.JAGad54054 (SR8606184848):
If API trace is enabled, then the parameter passed to
print_file_passwords() by ft_fmove_aet() API is not
correct.
The print_file_passwords() dumps core when it tries to
access the incorrect parameter passed to it.
Resolution:
The code has been changed to pass the correct parameter
to print_file_passwords().
11.JAGad49767 (SR8606180546)
If a FTAM application is in DATA transfer regime
and OTS is stopped on remote system, then FTAM
returns without any error.
Resolution:
The code has been modified to return error.
Enhancement:
No
SR:
8606300546 8606273742 8606250497 8606226141 8606226164
8606187872 8606185439 8606185449 8606185283 8606184848
8606180546
Patch Files:
FTAM9000.FTAM,fr=E.07.00,fa=HP-UX_B.11.11_32/64,v=HP:
/opt/ftam/lbin/ftam_init
/opt/ftam/lib/nls/C/fmt124f.cat
/opt/ftam/lib/libmapftam.a
/opt/ftam/shlib/libfmt124f.sl
/opt/ftam/bin/ftam
/opt/ftam/shlib/libmapftam.4
/opt/ftam/lbin/ftam_resp
/etc/opt/ftam/conf/ftam_conf
FTAM9000.FTAM_64,fr=E.07.00,fa=HP-UX_B.11.11_32/64,v=HP:
/opt/ftam/lib/pa20_64/libmapftam.a
/opt/ftam/shlib/pa20_64/libmapftam.1
what(1) Output:
FTAM9000.FTAM,fr=E.07.00,fa=HP-UX_B.11.11_32/64,v=HP:
/opt/ftam/lbin/ftam_init:
FTAM: PHNE_29033 03/06/16 s800 ftam_init
/opt/ftam/lbin/ftam_resp:
FTAM: PHNE_29033 03/06/16 s800 ftam_resp
/opt/ftam/bin/ftam:
FTAM: PHNE_29033 03/06/16 s800 ftam
FTAM: PHNE_29033 03/06/16 s800 libmapftam.a
/opt/ftam/lib/libmapftam.a:
FTAM: PHNE_29033 03/06/16 s800 libmapftam.a
/opt/ftam/lib/nls/C/fmt124f.cat:
MAP30: C.X5.01 $Date: 94/03/28 19:13:31 $
/opt/ftam/shlib/libfmt124f.sl:
MAP30: C.X5.01 $Date: 94/03/28 19:13:31 $
/opt/ftam/shlib/libmapftam.4:
FTAM: PHNE_29033 03/06/16 s800 libmapftam.sl
/etc/opt/ftam/conf/ftam_conf:
FTAM Configuration file
FTAM9000.FTAM_64,fr=E.07.00,fa=HP-UX_B.11.11_32/64,v=HP:
/opt/ftam/lib/pa20_64/libmapftam.a:
FTAM: PHNE_29033 03/06/16 s800 libmapftam.a
/opt/ftam/shlib/pa20_64/libmapftam.1:
FTAM: PHNE_29033 03/06/16 s800 libmapftam.sl
cksum(1) Output:
FTAM9000.FTAM,fr=E.07.00,fa=HP-UX_B.11.11_32/64,v=HP:
3351914008 1241088 /opt/ftam/lbin/ftam_init
2337109310 25767 /opt/ftam/lib/nls/C/fmt124f.cat
3209586412 590996 /opt/ftam/lib/libmapftam.a
3525809166 98304 /opt/ftam/shlib/libfmt124f.sl
918172792 704512 /opt/ftam/bin/ftam
296297148 798720 /opt/ftam/shlib/libmapftam.4
2242671567 1126400 /opt/ftam/lbin/ftam_resp
2809738387 5464 /etc/opt/ftam/conf/ftam_conf
FTAM9000.FTAM_64,fr=E.07.00,fa=HP-UX_B.11.11_32/64,v=HP:
3726413146 1056644 /opt/ftam/lib/pa20_64/libmapftam.a
3453789964 563672 /opt/ftam/shlib/pa20_64/libmapftam.1
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 1650 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHNE_29033
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_29033.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_29033. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHNE_29033.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_29033.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_29033.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHNE_29033------------------------------------------
Document ID: PHSS_28959
Date Loaded: 20030707
Title: s700_800 11.X OV ITO7.1X HP-UX 10.x Agent Patch A.07.20
Patch Name: PHSS_28959
Patch Description: s700_800 11.X OV ITO7.1X HP-UX 10.x Agent Patch A.07.20
Creation Date: 03/07/02
Post Date: 03/07/07
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
OpenView Operations 7.1
Filesets:
OVOPC-CLT.OVOPC-UX10-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-CLT.OVOPC-UX10-CLT,fr=A.07.10,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28959
Symptoms:
PHSS_28959:
- SR: B555015785
opcecaas may report that it runs out of free process
slots and therefore can't start anymore process.
- SR: B555008674
The opcagt and the opcragt commands have a new option
'-version'. In both man pages, this was not documented.
The new option was not part of the usage strings of
opcagt and opcragt.
- SR: 8606189243
Utility for checking basic types of communication
between OVO server and agents is missing.
- SR: H555009399
opcmona cores if invalid string is tried to be converted.
- SR: B555015479
When executing opcagt -kill there sometimes still
remains an entry for the Control Agent (opcctla) in the
pids file. This should not happen because the opcctla
isn't running anymore.
- SR: B555015626
opcif_read() doesn't return data if the signal pipe is
empty, but there is still more data in the queue file.
This can for example happen if the maximum pipe size of
8192 bytes was reached and therefore no more signal
bytes could be written into the signal pipe.
- SR: B555015496
Queue file handling was inefficient for larger queue
files.
- SR: 8606290675
Agent should report 'agent start' into the opcerror file.
- SR: R555018185
If the agent is started in Simplified Chinese codeset,
monitor agent, logfile encapsulator and message
interceptor processes will fail.
- SR: B555015449
Monitor agent may abort while receiving
templates/policies.
- SR: B555015155
Errors in the opcerror file are not written to the trace
file. This makes it difficult to find the place in the
trace file where the error occured.
- SR: B555015047
opcecaas (Annotation Server) might log error
"Illegal NULL parameter (function ) (OpC10-11)"
with many similar lines.
- SR: B555015557
The current implementation of the control agent does not
allow to restart aborted sub agent processes
automatically.
- SR: B555015199
If OPC_IP_ADDRESS (nodeinfo) and OPC_NAMESRV_LOCAL_NAME
(opcinfo) were used in combination the entry in
OPC_IP_ADDRESS was not used in the right way.
- SR: 8606282247
Logfile Encapsulator does not perform variable
replacement for all Message Defaults fields.
- SR: B555015331
The monitor agent, opcmona, may report wrong results of
executed monitor scripts or programs when using many
'advanced monitors' such as OVPERF. In some of these
cases opcmona might even abort.
- SR: B555015712
The trap/event interceptor forwards traps with the source
address 127.0.0.1 unchanged, therefore they are discarded
by the management server due to the unknown source
address.
- SR: B555015758
opcmsgi aborts if one of the set attributes has an
unmatched '<'.
- SR: 8606232431
VPO tries to resolve node names that only contain blanks
because of typo in template definition or variable
assignment. This leads to a lot of unnecessary DNS
traffic.
- SR: B555013121
When distributing agent software after the installation
of an agent patch, all agent components (opc_pkg.Z,
comm_pkg.Z and perf_pkg.Z) are distributed and installed,
although only one of the components was changed.
- SR: B555015349
The monitor agent might abort while using
templates/policies that have an external source
specified.
- SR: B555015325
opcmsga wrongly generates a message OpC30-3002 'opcctla
not running on node localhost.' when receiving a
reconfigure signal, or at exit time.
- SR: 8606300119
The logfile encapsulator does not return the last line of
a logfile immediately, if there is no carriage return in
this line.
- SR: 8606297998
The ECS engine (opcecm & opceca) might have problems
when a circuit is using global dictionaries.
(This is the case for the MessageStorm detection ECS
circuit).
PHSS_27386:
- SR: H555008602
If setting OPC_RPC_ONLY to TRUE in opcinfo, after a
while the message agent core dumps.
- SR: R555019153
When deplying policies from a Windows management server
and using the "StoreCollection" method within the Perl
or VBScript, the monitor agent might show the Policy name
instead of the given metricname or may abort.
- SR: B555014591
When the OPC_INT_MSG_FLT is set to TRUE then the filtered
message is received corrupted on the server in
a Japanese environment.
- SR: 8606275496
When installing an OVO 7.10 HP-UX Agent on a Managed
Node which already has an OVO 7.0 or 6.X agent on it,
the following Error occurs:
ERROR: Unexpected swinstall problem on system xyz. refer
to the logfile /var/adm/sw/swagent.log and
/var/adm/sw/swinstall.log on the managed node xyz for
further information on the problem.
- SR: B553003927
opcmsgi leaks memory when handling messages with custom
message attributes.
- SR: B555014942
The opcle process loops if a logfile is removed while
it is read.
- SR: H555006719
If the agent is running as a non-root user and the
management server processes are restarted, the agent
does not resume sending messages but continues to buffer
the messages.
- SR: B555017068
A.07.12 changed the behavior of opcle: Newly created
logfiles that are discovered by the dynamic logfile
discovery functionality are now read from begin. But
often this is not what is desired, for example if
using DBSPI with new instances that need to be monitored.
- SR: B555014851
opcmsga sends the same message operation (e.g. an
acknowledge request created by opcmack(1) )
again and again if the related message is not in the
cache and one of the target managers can not be reached.
- SR: B555013891
In MoM environments, opcmsga does not return action
responses to SECONDARY managers, if their name is not
resolvable.
- SR: H555008631
Customer receives a lot of OpC20-61 and OpC20-63 messages
in the error logfile when using NCS agents.
- SR: B555014574
opcagt -start/-stop/-status doesn't work correctly, if
the currently running agent can't be reached over RPC.
- SR: B555014093
opcmona may crash (UNIX) or doesn't process all SCHEDULE
templates (Windows) when using SCHEDULE templates.
- SR: 8606262299
The logfile encapsulator reports that the File to be
executed for preprocessing of a logfile template failed.
This error occurs randomly and only from time to time.
You will get an error message similar to the following:
Command 'opcfwtmp /tmp/wtmp.stat /var/adm/wtmp
/tmp/wtmp.out' configured in source 'Logins (10.x/11.x
HP-UX)' returns 1. Ignoring this logfile. (OpC30-107)
- SR: R555017956
The monitor agent is terminated if you use a session
variable within the message text of a template followed
by any other variable (for example $INSTANCE).
- SR: R555018043
Japanese characters in Perl scripts within templates
don't get converted correctly into the server code set.
If the Japanese characters are used as message text for
example these characters are corrupted.
- SR: B555014715
The Control Agent slowly grows in memory usage.
- SR: B555012869
Instead of using the trap's UUID, the trap interceptor
created a new message id for all but the first trap
template. The original message id was not set correctly
in these cases.
- SR: B555014215
The port should be configurable where opctrapi listens
for incoming traps.
- SR: B555013719
Message agent doesn't stop message buffering when the
management server is available again after a network
outage, fixed DNS problem or similar.
This can happen when the agent restarts/the machine
reboots during the network problem occurred.
- SR: 8606187183
After deploy/undeploy of opcmsg policies/templates the
suppressing times are lost. Messages that should be
suppressed after a deploy/undeploy of policies/templates
are shown.
- SR: H555008275
Message Agent can hang for no apparent reason and stop
sending all messages to the Management Server regardless
of its state.
- SR: B555014667
The first lines of a logfile are not forwarded to the
message browser when using a command to discover
logfiles and the logfile was created after the first
polling interval.
- SR: B555014873
The exit code of commands executed through an ECS
annotate node and the OVO annotation server is always 0.
- SR: B555014132
During a distribution the agent may report an error like:
ITO responsible manager configuration. (OpC30-1203)
Cannot open file \usr\OV\tmp\OpC\cfgchg.
System Error Number: 13 (d) - The data is invalid.
(OpC20-63)
- SR: B555014771
The opcqchk support utility dumps message operations
(e.g. acknowledge requests from opcmack) only as hex dump
so it would be nice to have some readable output.
- SR: B555013548
The manual agent installation script opc_inst expects
compressed packages. So if you run it a second time
nothing happens because the packages are already
uncompressed.
- SR: B555009284
The authorization verification for remote start and stop
requests of the agent was sometimes unreliable. Possibly
this allowed more OVO servers to start or stop the agent,
than specified in the MoM configuration.
- SR: 8606242614
Messages are incorrectly suppressed by the logfile
encapsulator if "suppress identical output messages" is
specified and the messages differ only in the values of
<$LOGFILE> and/or <$LOGPATH>.
- SR: B555013620
Support for pmd's "u" option needed in opctrapi: use the
UDP packet's address as source of the trap.
- SR: B555014759
When enabling/disabling policies you might discover a
memory leak in the agent processes.
- SR: H555008529
If a process dies immediately after being started by the
Control Agent, it is possible that OpC30-1094 messages
start appearing in the error logfile.
Defect Description:
PHSS_28959:
- SR: B555015785
One possible cause for opcecaas to report that there are
no more free process slots is, that all slots are in use
by applications that are running very long or might even
hang. In order to have control on this, the opcecaas
retrieves the timeout set for the "Annotate Node" in the
ECS circuit and kills the process in case it is beyond
this timeout.
- SR: B555008674
The man pages for opcagt and opcragt now document the new
option '-version'. The message catalog was updated to
show the '-version' option in the usage string of the
opcagt and opcragt commands.
- SR: 8606189243
The support tool /opt/OV/contrib/OpC/opcnetchk was
introduced to allow a basic ICMP check, TCP check and
SNMP check.
- SR: B555015496
So far a queue file garbage collection was done, if more
than 256 Kbyte were unused. Now the unused space has to
be more than 256 Kbyte and more than a quarter of the
queue file size. This drastically reduces file I/O when
handling large queue files.
- SR: R555018185
Simplified Chinese codeset is now mapped as a valid
codeset.
- SR: B555015155
Whenever an error is added to the internal error list,
a trace line with the DEBUG area ERRLIST is written to
the trace file.
When the error list is written to opcerror, another
trace line with the DEBUG area ERROR is written.
ERROR and ERRLIST are distinguished, since some errors
are added to the error list, but then later ignored
and therefore never appear in the opcerror file.
- SR: B555015557
The control agent has been changed in order to make the
restart of an aborted sub agent process configurable.
The control agent can be configured to restart aborted
sub agent processes. Furthermore it can be defined how
often a process should be restarted in a certain time
interval.
To configure this, you can use the following variables
in the opcinfo file:
OPC_RESTART_SUBAGENT
If set to TRUE, the control agent tries
to restart aborted sub agent processes.
The restart is done a defined number of
times (OPC_RESTART_COUNT) in a specified
period of time (OPC_RESTART_MINIMUM_RUN_TIME).
In case the process aborts more often,
it wont be restarted again.
Type/Unit : TRUE|FALSE
Default : TRUE
OPC_RESTART_COUNT
Defines how often an aborted sub agent process
should be restarted within the specified
minimum runtime. In case a process stops more often
it wont be restarted.
(See OPC_RESTART_SUBAGENT)
Type/Unit : integer
Default : 5
OPC_RESTART_DELAY
Defines the time the control agent waits
before it restarts an aborted sub agent
process. The time is specified in seconds.
Type/Unit : integer
Default : 10
OPC_RESTART_MINIMUM_RUN_TIME
Defines the time frame a sub agent process
should run without being restarted more
than specified by OPC_RESTART_COUNT.
The time is specified in minutes.
Type/Unit : integer (minutes)
Default : 60
- SR: 8606282247
Variable replacement is now performed for all Message
Defaults fields.
- SR: B555015331
opcmona holds a central table for all subprocess related
information. Advanced monitors are executed in separate
threads and could access this table in parallel, thus
overwriting each other's data. The table accesses are now
serialized by a mutex.
- SR: B555015712
In order to be able to correctly handle traps that have a
source address 127.0.0.1 the trap/event interceptor is
now able to replace the localhost address (127.0.0.1)
with the IP address of the node processing the trap.
In order to enable this, you need to add the following
line to the opcinfo file on your managed node:
OPC_RESOLVE_TRAP_LOCALHOST TRUE
- SR: 8606232431
VPO now ignores node names that contain only white space
characters without contacting the name service.
- SR: B555013121
A new tool has been introduced, that will be called
when an agent patch is installed to set the software
flag in the database for all nodes of that platform to
MODIFIED (node needs new agent software). Thus, it is
no longer necessary to use force update to install the
agent software to nodes of that platform.
The second change will check what component versions are
already installed on the agent and only distribute and
install the newer agent packages, if force update is NOT
used.
- SR: B555015349
The monitor agent aborts when using templates/policies
with external sources as soon as it receives a value
from the external source during checking for the
threshold with a previously received value. In this case
the received value is stored temporary and as soon as
the monitor agent tries to process this value it aborts.
The root cause is that the monitor agent tries to free
up already freed memory.
- SR: B555015325
During startup a timing issue prevented a connection from
opcmsga to opcctla, which generated the message. This
message was not immediately reported, but only after
receiving a signal. Retries will now prevent the
connection failure. If it still fails because opcctla is
really not running, the error will be reported
immediately.
PHSS_27386:
- SR: H555008602
When using OPC_RPC_ONLY, ICMP handling is not
initialized, but the message agent will call
opc_pb_ping_reset() after a successful server checkalive
cycle. This causes an invalid (NULL) pointer to be
dereferenced and causes a core dump.
opc_pb_ping_reset() now has a check to see if ICMP
handling has been initialized and if not, immediately
returns from the function.
- SR: B555014591
The defect was caused by the double conversion from the
server code set to the internal code set, once on the
agents side when it sent the internal message to opcmsga
and once by opcmsgi when it forwarded the message again.
Now, the message is converted back from the internal code
set to the server code set in opcmsga before sending the
message to the opcmsgi queue. The management server will
get the message through opcmsga in the internal code set,
and it will convert it into the server code set.
The conversion is made only if the internal code set is
different from the server code set.
- SR: H555006719
When a communication to a message receiver fails, the
message agent starts buffering messages. It periodically
checks if a server is alive by sending it ICMP packets.
If the server cannot be reached with ICMP packets, no RPC
communication is attempted. Sending ICMP packets is not
possible when the agent is running as a non-root user, so
the sending function cannot actually send anything.
Therefore we also never receive any replies and the
message agent will buffer messages forever. To fix this,
the internal state of the message agent is updated after
we tried to send an ICMP packet if the agent is running
as a non-root user.
- SR: B555017068
The default behavior is now again the bahavior of
A.07.10:
If a new logfile is returned by the logfile discovery
program, only new lines of the new logfile are processed.
If you want, that all lines of newly added logfiles are
processed, add following line to the opcinfo file:
OPC_NEW_LOGFILE_FROM_BEGIN TRUE
- SR: B555014851
opcmsga maintains an internal cache to find out the
target managers per message ID. The cache expires
after 1 hour (can be changed with the opcsvinfo variable
OPC_STORE_TIME_FOR_MGR_INFO) and then it runs into a
problem in its algorithm so that a message operation on
a non-cached message is sent again and again until the
last target manager in an internal list can be reached.
- SR: B555013891
Even if the IP address of the management server was
specified in the mgrconf file, it was not used except for
the primary manager. This behavior was changed to give
the mgrconf file precedence over name resolution.
- SR: H555008631
NCS agent open() and stat() calls did not handle EINTR,
so a check/loop was implemented to handle it.
- SR: B555014574
With this changes the opcctla is now be able to deal with
a running opcctla that is not reachable via RPC:
opcagt -status will display a warning if the currently
running opcctla is not reachable over RPC, but then it
will display the status according to the pids file.
opcagt -stop will also kill the unresponsive opcctla and
try to start a new one.
If opcctla is not reachable over RPC, opcagt -start will
kill all running agent processes and then start a new
opcctla which starts the agent processes.
But of course, the agent won't be able to start if RPC
is still not available at that time.
- SR: B555014093
opcmona may crash (UNIX) or doesn't process all SCHEDULE
templates (Windows) when using SCHEDULE templates.
This can occur when there are only spaces in
one of the schedule fields (Minute, Hour, Day of the
Month, Month, Year, Day of the Week).
You can verify this by going to the conf/OpC directory on
the node and doing an opcdcode monitor. When
there are entries like WEEKDAY " " the problem can occur.
Now the monitor agent treats sequences of spaces like
an empty string that is a wildcard and uses all valid
values in the possible range.
For WEEKDAY this is 0-6.
- SR: B555014215
Using the new opcinfo variable SNMP_TRAP_PORT <port_num>
opctrapi can now be configured to listen on another port
than 162. This is only effective, if traps are not
received through the NNM pmd.
- SR: B555013719
Message agent remains in buffering mode even when
the management server is available again.
The reason is that the agent wasn't able to resolve
the management server name to an IP address at startup
and the agent doesn't try again during runtime.
This has been fixed by checking for a resolvable name
every time a message should be buffered till the name can
be resolved, after this the normal checkalive mechanism
which handles buffered message takes place.
- SR: 8606187183
The opcmsg interceptor restarts after a deploy/undeploy
of policies/templates. During this process all the
policy/template information is cleaned and read again
from a temporary file. Because suppressing times are not
stored in this temporary file, this times are lost.
Now the suppressing times are taken over to the new data.
- SR: H555008275
Signal handler for SIGIO was installed before the socket
on which we receive ICMP replies was set to non-blocking
mode. An unsolicited SIGIO would trigger the signal
handler which would wait indefinitely on the socket for
data, which would never arrive. Since NCS agent is
single-threaded, all communication would stop.
The fix is in setting the non-blocking mode before
installing the signal handler, so it would not wait
forever.
- SR: B555014873
The exit code of commands executed through an ECS
annotate node and the OVO annotation server is always 0.
The reason is an hardcoded return value in the OVO
annotation server. With this patch the annotation server
passes the received exit code to ECS.
- SR: B555014132
During a distribution the agent may report error number
OPC30-1203/OPC20-63 when trying to access the cfgchg
file.
The cause for this problem is that there are several
processes trying to get exclusive access to this file
at the same time. The problem has been fixed by doing a
retry for 10 times in case the error should occur with a
delay of one second.
- SR: B555014771
The opcqchk support utility dumps message operations
(Tag: 43, like acknowledge requests from opcmack).
This tag type was not implemented in opcqchk so you only
got the hex dump output. Now you get a more readable
output like:
Size of item 1: 76 bytes. Tag: 43
Data:
Message operation = acknowledge request
Msg id = >2878c8b8-d45e-71d6-00d3-c0a8f4220000<
- SR: B555009284
There were two different authorization algorithms which
interfered with each other. This has been consolidated
and is now checked more strictly.
- SR: 8606242614
The variables <$LOGFILE> and <$LOGPATH> were replaced
after the suppression rules were evaluated. Therefore the
comparison did not use the actual logfile name or path,
but compared the string "<$LOGFILE>" or "<$LOGPATH>".
- SR: B555013620
NNM 6.2 introduced an event option to pmd - "u". This
option specifies to prefer the IP address in an SNMPv1
trap's UDP header over the contents of the SNMPv1 trap
PDU's agent_addr field.
A new opcinfo variable OPC_USE_UDP_AS_TRAP_SOURCE was
added for opctrapi. If set to TRUE, opctrapi will use the
UDP address instead of the agent_addr.
- SR: H555008529
This is a timing issue, where internal structures are not
updated by the signal handler in time for proper values
to be written in the PIDS file.
An additional check for process presence has been
implemented before writing the PIDS file.
Enhancement:
No
SR:
R555019153 R555018267 R555018227 R555018185 R555018043
R555017956 H555009399 H555008631 H555008602 H555008546
H555008529 H555008275 H555006719 B555017068 B555016326
B555015785 B555015758 B555015712 B555015626 B555015557
B555015496 B555015479 B555015449 B555015349 B555015331
B555015325 B555015230 B555015199 B555015155 B555015047
B555014942 B555014873 B555014851 B555014771 B555014759
B555014715 B555014667 B555014591 B555014574 B555014215
B555014189 B555014132 B555014093 B555014014 B555013891
B555013719 B555013620 B555013548 B555013474 B555013121
B555012869 B555009284 B555009183 B555008674 B553003927
8606300119 8606297998 8606290675 8606286654 8606284806
8606282247 8606277183 8606275496 8606273258 8606262299
8606247907 8606242614 8606232431 8606189243 8606187183
Patch Files:
OVOPC-CLT.OVOPC-UX10-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
OVOPC-CLT.OVOPC-UX10-CLT,fr=A.07.10,fa=HP-UX_B.11.11_32/64,
v=HP:
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
hp-ux10/A.07.10/RPC_DCE_TCP/opc_pkg.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
hp-ux10/A.07.10/RPC_DCE_TCP/opc_version
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
hp-ux10/A.07.10/RPC_DCE_TCP/install/opcrinst
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
hp-ux10/A.07.10/RPC_DCE_TCP/opc_inst
what(1) Output:
OVOPC-CLT.OVOPC-UX10-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
hp-ux10/A.07.10/RPC_DCE_TCP/opc_pkg.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
hp-ux10/A.07.10/RPC_DCE_TCP/opc_version:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
hp-ux10/A.07.10/RPC_DCE_TCP/install/opcrinst:
HP OpenView Operations A.07.20 (04/09/03)
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
hp-ux10/A.07.10/RPC_DCE_TCP/opc_inst:
HP OpenView Operations A.07.20 (04/09/03)
cksum(1) Output:
OVOPC-CLT.OVOPC-UX10-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
701270558 16049257 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/s700/hp-ux10/A.07.10/RPC_DCE_TCP/opc_pkg.Z
4030162770 8 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/s700/hp-ux10/A.07.10/RPC_DCE_TCP/
opc_version
3936934096 120714 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/s700/hp-ux10/A.07.10/RPC_DCE_TCP/install/
opcrinst
4037647179 1293 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/s700/hp-ux10/A.07.10/RPC_DCE_TCP/opc_inst
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_27386
Equivalent Patches:
ITOSOL_00224:
sparcSOL: 2.7 2.8
Patch Package Size: 14860 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_28959
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28959.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28959. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_28959.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28959.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28959.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
BEFORE LOADING THIS PATCH...
(A) Patch Installation Instructions
-------------------------------
(A1) Install the patch, following the standard
installation instructions.
For backing up the system before installing
a patch, you may use opc_backup(1m)
NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
ADDRESSED BY THIS PATCH IS DISTRIBUTED
(either from the VPO Administrator's GUI
or from command line using inst.sh) WHILE
RUNNING SWINSTALL.
NOTE: This patch must be installed on the VPO Management
Server system, NOT on an VPO Managed Node directly.
Changes will take effect on managed nodes by means of
VPO Software Distribution. See chapter 2 of the VPO
Administrator's Reference manual for more information.
NOTE: The VPO Agent consists of several components that
are patched individually. This patch updates only the
Event/Action component. Therefore the software
distribution will tell, that the agent software is
updated to A.07.10, not to A.07.20. Also the version
of the ITOAgent bundle will still be A.07.10. You can
verify the installed version of the components on the
agent system using opcragt -agent_version.
For example:
opcragt -agent_version hpbbln8
Node hpbbln8.bbn.hp.com:
OPC_INSTALLED_VERSION = A.07.20
PERF_INSTALLED_VERSION = A.07.10
COMM_INSTALLED_VERSION = 2.5.3.9
Done.
(B) Patch Deinstallation Instructions
---------------------------------
(B1) To deinstall the patch PHSS_28959 run swremove:
NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
ADDRESSED BY THIS PATCH IS DISTRIBUTED (either
from the ITO Administrator's GUI or from
command line using inst.sh) WHILE RUNNING
SWREMOVE.
# swremove PHSS_28959
-----End of Document ID: PHSS_28959------------------------------------------
Document ID: PHSS_28960
Date Loaded: 20030707
Title: s700_800 11.X OV ITO7.1X HP-UX 11.X ia64 Agent A.07.20
Patch Name: PHSS_28960
Patch Description: s700_800 11.X OV ITO7.1X HP-UX 11.X ia64 Agent A.07.20
Creation Date: 03/07/02
Post Date: 03/07/07
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
OpenView Operations 7.1
Filesets:
OVOPC-CLT.OVOPC-UXIA-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-CLT.OVOPC-UXIA-CLT,fr=A.07.10,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28960
Symptoms:
PHSS_28960:
- SR: B555015785
opcecaas may report that it runs out of free process
slots and therefore can't start anymore process.
- SR: B555008674
The opcagt and the opcragt commands have a new option
'-version'. In both man pages, this was not documented.
The new option was not part of the usage strings of
opcagt and opcragt.
- SR: B555014591
When the OPC_INT_MSG_FLT is set to TRUE then the filtered
message is received corrupted on the server in
a Japanese environment.
- SR: B555017068
A.07.12 changed the behavior of opcle: Newly created
logfiles that are discovered by the dynamic logfile
discovery functionality are now read from begin. But
often this is not what is desired, for example if
using DBSPI with new instances that need to be monitored.
- SR: H555009399
opcmona cores if invalid string is tried to be converted.
- SR: B555015479
When executing opcagt -kill there sometimes still
remains an entry for the Control Agent (opcctla) in the
pids file. This should not happen because the opcctla
isn't running anymore.
- SR: H555010095
Default location for GSS API library on HP-UX 11.22 agent
is set to /opt/OV/lib instead of /opt/OV/lib/hpux32.
- SR: B555016565
The Agent APIs and the Agent API example programs on
HP-UX 11.22 do not work.
- SR: B555015626
opcif_read() doesn't return data if the signal pipe is
empty, but there is still more data in the queue file.
This can for example happen if the maximum pipe size of
8192 bytes was reached and therefore no more signal
bytes could be written into the signal pipe.
- SR: B555015496
Queue file handling was inefficient for larger queue
files.
- SR: 8606290675
Agent should report 'agent start' into the opcerror file.
- SR: R555018185
If the agent is started in Simplified Chinese codeset,
monitor agent, logfile encapsulator and message
interceptor processes will fail.
- SR: B555015449
Monitor agent may abort while receiving
templates/policies.
- SR: B555015155
Errors in the opcerror file are not written to the trace
file. This makes it difficult to find the place in the
trace file where the error occured.
- SR: B555015047
opcecaas (Annotation Server) might log error
"Illegal NULL parameter (function ) (OpC10-11)"
with many similar lines.
- SR: R555018044
The monitor scheduled command policy will be executed
only once.
- SR: B555015557
The current implementation of the control agent does not
allow to restart aborted sub agent processes
automatically.
- SR: B555015199
If OPC_IP_ADDRESS (nodeinfo) and OPC_NAMESRV_LOCAL_NAME
(opcinfo) were used in combination the entry in
OPC_IP_ADDRESS was not used in the right way.
- SR: 8606282247
Logfile Encapsulator does not perform variable
replacement for all Message Defaults fields.
- SR: B555015331
The monitor agent, opcmona, may report wrong results of
executed monitor scripts or programs when using many
'advanced monitors' such as OVPERF. In some of these
cases opcmona might even abort.
- SR: B555015712
The trap/event interceptor forwards traps with the source
address 127.0.0.1 unchanged, therefore they are discarded
by the management server due to the unknown source
address.
- SR: B555015758
opcmsgi aborts if one of the set attributes has an
unmatched '<'.
- SR: 8606232431
VPO tries to resolve node names that only contain blanks
because of typo in template definition or variable
assignment. This leads to a lot of unnecessary DNS
traffic.
- SR: B555015349
The monitor agent might abort while using
templates/policies that have an external source
specified.
- SR: B555013121
When distributing agent software after the installation
of an agent patch, all agent components (opc_pkg.Z,
comm_pkg.Z and perf_pkg.Z) are distributed and installed,
although only one of the components was changed.
- SR: B555015325
opcmsga wrongly generates a message OpC30-3002 'opcctla
not running on node localhost.' when receiving a
reconfigure signal, or at exit time.
- SR: 8606300119
The logfile encapsulator does not return the last line of
a logfile immediately, if there is no carriage return
in this line.
- SR: 8606297998
The ECS engine (opcecm & opceca) might have problems
when a circuit is using global dictionaries.
(This is the case for the MessageStorm detection ECS
circuit).
Defect Description:
PHSS_28960:
- SR: B555015785
One possible cause for opcecaas to report that there are
no more free process slots is, that all slots are in use
by applications that are running very long or might even
hang. In order to have control on this, the opcecaas
retrieves the timeout set for the "Annotate Node" in the
ECS circuit and kills the process in case it is beyond
this timeout.
- SR: B555008674
The man pages for opcagt and opcragt now document the new
option '-version'. The message catalog was updated to
show the '-version' option in the usage string of the
opcagt and opcragt commands.
- SR: B555014591
The defect was caused by the double conversion from the
server code set to the internal code set, once on the
agents side when it sent the internal message to opcmsga
and once by opcmsgi when it forwarded the message again.
Now, the message is converted back from the internal code
set to the server code set in opcmsga before sending the
message to the opcmsgi queue. The management server will
get the message through opcmsga in the internal code set,
and it will convert it into the server code set.
The conversion is made only if the internal code set is
different from the server code set.
- SR: B555017068
The default behavior is now again the bahavior of
A.07.10:
If a new logfile is returned by the logfile discovery
program, only new lines of the new logfile are processed.
If you want, that all lines of newly added logfiles are
processed, add following line to the opcinfo file:
OPC_NEW_LOGFILE_FROM_BEGIN TRUE
- SR: B555015496
So far a queue file garbage collection was done, if more
than 256 Kbyte were unused. Now the unused space has to
be more than 256 Kbyte and more than a quarter of the
queue file size. This drastically reduces file I/O when
handling large queue files.
- SR: R555018185
Simplified Chinese codeset is now mapped as a valid
codeset.
- SR: B555015155
Whenever an error is added to the internal error list,
a trace line with the DEBUG area ERRLIST is written to
the trace file.
When the error list is written to opcerror, another
trace line with the DEBUG area ERROR is written.
ERROR and ERRLIST are distinguished, since some errors
are added to the error list, but then later ignored
and therefore never appear in the opcerror file.
- SR: R555018044
Internal flag is restored after monitor schedule policy
execution.
- SR: B555015557
The control agent has been changed in order to make the
restart of an aborted sub agent process configurable.
The control agent can be configured to restart aborted
sub agent processes. Furthermore it can be defined how
often a process should be restarted in a certain time
interval.
To configure this, you can use the following variables
in the opcinfo file:
OPC_RESTART_SUBAGENT
If set to TRUE, the control agent tries
to restart aborted sub agent processes.
The restart is done a defined number of
times (OPC_RESTART_COUNT) in a specified
period of time (OPC_RESTART_MINIMUM_RUN_TIME).
In case the process aborts more often,
it wont be restarted again.
Type/Unit : TRUE|FALSE
Default : TRUE
OPC_RESTART_COUNT
Defines how often an aborted sub agent process
should be restarted within the specified
minimum runtime. In case a process stops more often
it wont be restarted.
(See OPC_RESTART_SUBAGENT)
Type/Unit : integer
Default : 5
OPC_RESTART_DELAY
Defines the time the control agent waits
before it restarts an aborted sub agent
process. The time is specified in seconds.
Type/Unit : integer
Default : 10
OPC_RESTART_MINIMUM_RUN_TIME
Defines the time frame a sub agent process
should run without being restarted more
than specified by OPC_RESTART_COUNT.
The time is specified in minutes.
Type/Unit : integer (minutes)
Default : 60
- SR: 8606282247
Variable replacement is now performed for all Message
Defaults fields.
- SR: B555015331
opcmona holds a central table for all subprocess related
information. Advanced monitors are executed in separate
threads and could access this table in parallel, thus
overwriting each other's data. The table accesses are now
serialized by a mutex.
- SR: B555015712
In order to be able to correctly handle traps that have a
source address 127.0.0.1 the trap/event interceptor is
now able to replace the localhost address (127.0.0.1)
with the IP address of the node processing the trap.
In order to enable this, you need to add the following
line to the opcinfo file on your managed node:
OPC_RESOLVE_TRAP_LOCALHOST TRUE
- SR: 8606232431
VPO now ignores node names that contain only white space
characters without contacting the name service.
- SR: B555015349
The monitor agent aborts when using templates/policies
with external sources as soon as it receives a value
from the external source during checking for the
threshold with a previously received value. In this case
the received value is stored temporary and as soon as
the monitor agent tries to process this value it aborts.
The root cause is that the monitor agent tries to free
up already freed memory.
- SR: B555013121
A new tool has been introduced, that will be called
when an agent patch is installed to set the software
flag in the database for all nodes of that platform to
MODIFIED (node needs new agent software). Thus, it is
no longer necessary to use force update to install the
agent software to nodes of that platform.
The second change will check what component versions are
already installed on the agent and only distribute and
install the newer agent packages, if force update is NOT
used.
- SR: B555015325
During startup a timing issue prevented a connection from
opcmsga to opcctla, which generated the message. This
message was not immediately reported, but only after
receiving a signal. Retries will now prevent the
connection failure. If it still fails because opcctla is
really not running, the error will be reported
immediately.
Enhancement:
No
SR:
R555018185 R555018044 H555010095 H555009399 B555017068
B555016565 B555016326 B555015785 B555015758 B555015712
B555015626 B555015557 B555015496 B555015479 B555015449
B555015349 B555015331 B555015325 B555015230 B555015199
B555015155 B555015047 B555014591 B555013474 B555013121
B555008674 8606300119 8606297998 8606290675 8606286654
8606284806 8606282247 8606232431
Patch Files:
OVOPC-CLT.OVOPC-UXIA-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
OVOPC-CLT.OVOPC-UXIA-CLT,fr=A.07.10,fa=HP-UX_B.11.11_32/64,
v=HP:
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/ia64/
hp-ux11_32/A.07.10/RPC_DCE_TCP/opc_pkg.Z
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/ia64/
hp-ux11_32/A.07.10/RPC_DCE_TCP/opc_version
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/ia64/
hp-ux11_32/A.07.10/RPC_DCE_TCP/install/opcrinst
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/ia64/
hp-ux11_32/A.07.10/RPC_DCE_TCP/opc_inst
/opt/OV/OpC/examples/progs/Makef.hpuxIA32
what(1) Output:
OVOPC-CLT.OVOPC-UXIA-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/ia64/
hp-ux11_32/A.07.10/RPC_DCE_TCP/opc_pkg.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/ia64/
hp-ux11_32/A.07.10/RPC_DCE_TCP/opc_version:
None
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/ia64/
hp-ux11_32/A.07.10/RPC_DCE_TCP/install/opcrinst:
HP OpenView Operations A.07.20 (06/10/03)
/var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/ia64/
hp-ux11_32/A.07.10/RPC_DCE_TCP/opc_inst:
HP OpenView Operations A.07.20 (06/10/03)
/opt/OV/OpC/examples/progs/Makef.hpuxIA32:
None
cksum(1) Output:
OVOPC-CLT.OVOPC-UXIA-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
1091860843 27739547 /var/opt/OV/share/databases/OpC/
mgd_node/vendor/hp/ia64/hp-ux11_32/A.07.10/
RPC_DCE_TCP/opc_pkg.Z
4030162770 8 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/ia64/hp-ux11_32/A.07.10/RPC_DCE_TCP/
opc_version
1080665434 120149 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/ia64/hp-ux11_32/A.07.10/RPC_DCE_TCP/
install/opcrinst
3270723701 1293 /var/opt/OV/share/databases/OpC/mgd_node/
vendor/hp/ia64/hp-ux11_32/A.07.10/RPC_DCE_TCP/
opc_inst
3293923830 1571 /opt/OV/OpC/examples/progs/Makef.hpuxIA32
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
ITOSOL_00225:
sparcSOL: 2.7 2.8
Patch Package Size: 26130 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_28960
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28960.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28960. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_28960.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28960.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28960.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
BEFORE LOADING THIS PATCH...
(A) Patch Installation Instructions
-------------------------------
(A1) Install the patch, following the standard
installation instructions.
For backing up the system before installing
a patch, you may use opc_backup(1m)
NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
ADDRESSED BY THIS PATCH IS DISTRIBUTED
(either from the VPO Administrator's GUI
or from command line using inst.sh) WHILE
RUNNING SWINSTALL.
NOTE: This patch must be installed on the VPO Management
Server system, NOT on an VPO Managed Node directly.
Changes will take effect on managed nodes by means of
VPO Software Distribution. See chapter 2 of the VPO
Administrator's Reference manual for more information.
NOTE: The VPO Agent consists of several components that
are patched individually. This patch updates only the
Event/Action component. Therefore the software
distribution will tell, that the agent software is
updated to A.07.10, not to A.07.20. Also the version
of the ITOAgent bundle will still be A.07.10. You can
verify the installed version of the components on the
agent system using opcragt -agent_version.
For example:
opcragt -agent_version hpbbln8
Node hpbbln8.bbn.hp.com:
OPC_INSTALLED_VERSION = A.07.20
PERF_INSTALLED_VERSION = A.07.10
COMM_INSTALLED_VERSION = 2.5.3.9
Done.
(B) Patch Deinstallation Instructions
---------------------------------
(B1) To deinstall the patch PHSS_28960 run swremove:
NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
ADDRESSED BY THIS PATCH IS DISTRIBUTED (either
from the ITO Administrator's GUI or from
command line using inst.sh) WHILE RUNNING
SWREMOVE.
# swremove PHSS_28960
-----End of Document ID: PHSS_28960------------------------------------------
Document ID: PHSS_29301
Date Loaded: 20030707
Title: s700_800 11.X OV SIP3.0 Various problems in proxy
Patch Name: PHSS_29301
Patch Description: s700_800 11.X OV SIP3.0 Various problems in proxy
Creation Date: 03/06/25
Post Date: 03/07/07
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
OpenView Service Information Portal 3.0
Filesets:
HPOVSIP.OVSIP,fr=B.01.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_29301
Symptoms:
PHSS_29301:
1. When configuring entries in the OVProxyConfig.xml file,
if the configuration is for a specific attribute within a
tag then the proxy module removes all other attributes
from the tag.
2. The applet and object tags are not proxied by the proxy
module.
3. If mime types are not configured properly on the
websever, the proxy module fails to fetch jar and class
files correctly.
PHSS_28912:
If the generic module is used to proxy an html form that
uses the HTTP GET method for submission. Then the SIP
proxy fails to pass the submitted parameters to the
backend server.
PHSS_28254:
When the generic module is used to proxy a URL that has xml
declaration in its content, the proxy does not parse the
document correctly. This causes an error when viewed
through the Internet Explorer 5.x browser.
PHSS_27769:
If one configures SIP in a distributed fashion by
modifying the SIPPath.properties file so
SIP_SHARE_CONF_DIR contains a URL, several of the graphs
and charts displayed by the OVIS integration module will
be empty.
PHSS_27756:
8606264268:
When using Japanese OVIS 4.01 with SIP3.0. The
Availability, Response Time and Service Level Violation
gauges do not show up on the Internet Services module.
8606274452:
For OVIS/SIP integration in German, the gauges do not show
up when using the Internet Services module.
PHSS_26379:
8606261412:
1. OVO messages module does not handle acknowledged OVO
messages in the same way as the OVO message browser.
Acknowledged messages that have not yet been moved to the
Historical DB table continue to display in the Active
messages list. In fact they should be in the Historical
Messages only.
2. Some messages on the message summary tools are counted
twice.
3. SIP does not pass localized customer names/passwords to
OVIS
4. Floating point metric values not displayed properly in
Spanish locale.
5. Time intervals displayed in SIP 3.0 are not consistent
with OVIS4.0
6. SIP 3.0 drill down graphs via gauges do not display
same metrics as OVIS.
7. SIP 3.0 OVIS module display of response time components
is inaccurate.
8606254824:
A Generic Module instance, with proxy enabled,
emits "Response Already Committed" error when displaying a
particular web page.
8606254832:
HTML/Javascript error occurs in a proxied web page.
8606254836:
"File not Found" error occurs in browser when trying to
access a link in a proxied web page.
8606254839:
"File not Found" error occurs in browser when trying to
access a link in a proxied web page.
8606251008:
When integrating SIP3.0 with OVIS4.0 the portal does not
display the graphs.
8606242110:
Display filter does not works as expected in OVO module.
8606237747:
When trying to modify a bookmark (from the Bookmarks -
Edit GUI), if the bookmark name, URL, or window name
contains "'", "&","<",">" or '"', then Java exceptions
will be generated and the operation cannot be
completed.
8606227699:
With SIP configured to use OVO Service Navigator, if
two or more browsers attempt a refresh simultaneously
(under certain circumstances), one of the browsers displays
a Data Unavailable message and the log contains the message
"An error in the service filter mechanism occurred". A
third browser may display a full service tree rather than a
specific subtree.
Defect Description:
PHSS_29301:
1. When parsing a tag that has an entry in the
OVProxyConfig.xml file, the proxy module only puts the
specified attribute in the output html.
2. The proxy module does not modify attributes in applet
or object tags.
3. By default the proxy module uses the text proxyer if it
cannot find the content type for incoming data. This does
not work if the incoming data is binary.
Resolution:
1. The proxyer now modifies the specified attribute and
puts out all the attributes in the output html.
2. Functionality has been added to proxy the applet and
object tags.
3. The OVProxyType.xml file allows the user to specify the
proxyer to use for a particular file type.
PHSS_28912:
The proxy disregards any new/modified query string attached
to the URL when an HTTP GET request is used to submit a
form.
Resolution:
The proxy code has been fixed so that it does not
disregard the query part of the URL.
PHSS_28254:
XML declaration tags are not handled correctly by the HTML
proxy class.
Resolution:
The HTML proxy has been modified to handle XML declarations.
PHSS_27769:
SIP_SHARE_CONF_DIR is being treated as a file, not a URL,
by the OVIS integration.
Resolution:
Code modified to handle URL or file spec in
SIP_SHARE_CONF_DIR.
PHSS_27756:
8606264268:
1. SIP is failing to parse the version information
returned by Insight.
2. The logic which checks the version of RepIOps is
incorrect.
8606274452:
OVIS 4.0 returned gauge values in the locale that the
client (SIP) is running on. There were certain instances
where OVIS would think that SIP is running in German
locale while SIP is actually running under English locale.
This would cause SIP to misinterpret the gauge values.
Resolution:
8606264268:
1. SIP now reads version information in UTF8, thus it is
able to parse the xml correctly.
2. The code which checks for RepIops version has been
changed, so that it works correctly for versions higher
than 4.0.6.
8606274452:
OVIS now returns gauge values in English locale. Also, SIP
has been modified to always expect the gauge values to be
in US.English locale.
PHSS_26379:
8606254824:
Code defect in constructing proxy IDs.
8606254832:
SIP mishandles comments that wrap javascript, inserting a
line break after the comment open characters.
8606254836:
SIP failed to proxy a URL reference (ending in '.htm')in
javascript
8606254839:
SIP failed to proxy a URL reference in the VALUE attribute
of a FORM's SELECT OPTION tag.
8606242110:
NodeSelection elements were assigned to a local variable,
hence not available to other methods in the class.
8606237747:
The bookmark code parses the bookmarks fields during the
modify action, but the value attributes for name, url, and
window name were not xml-encoded when the values were
saved. Though quoted, they failed to pass the parser's
more restrictive requirements for valid values.
8606227699:
An uncaught exception causes misbehavior. The exception is
compounded due to some synchronization problems.
Resolution:
8606254824:
Proxy IDs are now constructed properly.
8606254832:
SIP no longer inserts the line break.
8606254836:
<SIP_HOME_DIR>/conf/share/proxy/OVProxyConfig.xml now
specifies URL suffixes to be searched for within script.
By default, these suffixes
are ".jsp", ".asp", ".gif", ".jpg", ".htm" and ".html" and
their uppercase counterparts. See the documentation
within OVProxyConfig.xml for details.
8606254839:
<SIP_HOME_DIR>/conf/share/proxy/OVProxyConfig.xml allows
the customer to provide URL hints for specific
tag/attribute combinations. See the documentation within
OVProxyConfig.xml for details.
8606242110:
NodeSelection elements are now assigned to a field in the
class.
8606237747:
Strings are now xml-encoded.
8606227699:
Catch the exception and attempt to gracefully recover. Add
'synchronized' statements to avoid inappropriate access.
Enhancement:
No
SR:
8606311348 8606293338 8606282799 8606266087 8606264268
8606274452 8606251008 8606254832 8606254824 8606254836
8606237747 8606254839 8606242110 8606261412 8606227699
Patch Files:
HPOVSIP.OVSIP,fr=B.01.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/SIP/conf/styles/VPISModule_html.xsl
/opt/OV/SIP/conf/share/modules/ovis/InsightTemplate.dtd
/opt/OV/SIP/conf/share/modules/ovis/Graphs.xml
/opt/OV/SIP/conf/share/proxy/OVProxyType.dtd
/opt/OV/SIP/conf/share/proxy/OVProxyType.xml
/opt/OV/SIP/conf/share/proxy/OVProxyConfig.xml
/opt/OV/SIP/conf/share/proxy/OVProxyConfig.dtd
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/filter/SimpleCustomerModel.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/util/OVURLEncoder.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/proxy/OVHTMLProxyer.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/proxy/OVProxyParser.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/proxy/OVProxyParser$ProxyException.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/proxy/OVProxyParameters.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/proxy/OVProxyType.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/proxy/OVProxyAttributes.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/proxy/OVProxyConfig.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/servlet/ImageServlet.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/service/SvcServiceConfigDoc.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/service/SvcServerConfigDoc.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/service/SvcGraphServlet.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/bookmarks/Bookmark.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/bookmarks/Bookmark$BookmarkObj.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/ovo/MessageCategory.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/ovo/SummaryView.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/ovo/DetailView.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/ovo/ListView.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/ovo/DBConnection.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/vpis/VpisManager.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/vpis/VpisCollector.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/vpis/StateInfo.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/vpis/OvisSystemState.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/vpis/VpisServlet.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/ovgeneric/GmGeneric.class
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/ovgeneric/ParmHandler.class
what(1) Output:
HPOVSIP.OVSIP,fr=B.01.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/SIP/conf/styles/VPISModule_html.xsl:
None
/opt/OV/SIP/conf/share/modules/ovis/InsightTemplate.dtd:
None
/opt/OV/SIP/conf/share/modules/ovis/Graphs.xml:
None
/opt/OV/SIP/conf/share/proxy/OVProxyType.dtd:
None
/opt/OV/SIP/conf/share/proxy/OVProxyType.xml:
None
/opt/OV/SIP/conf/share/proxy/OVProxyConfig.xml:
None
/opt/OV/SIP/conf/share/proxy/OVProxyConfig.dtd:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/filter/SimpleCustomerModel.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/util/OVURLEncoder.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/proxy/OVHTMLProxyer.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/proxy/OVProxyParser.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/proxy/OVProxyParser$ProxyException.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/proxy/OVProxyParameters.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/proxy/OVProxyType.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/proxy/OVProxyAttributes.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/proxy/OVProxyConfig.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/servlet/ImageServlet.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/service/SvcServiceConfigDoc.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/service/SvcServerConfigDoc.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/service/SvcGraphServlet.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/bookmarks/Bookmark.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/bookmarks/Bookmark$BookmarkObj.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/ovo/MessageCategory.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/ovo/SummaryView.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/ovo/DetailView.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/ovo/ListView.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/ovo/DBConnection.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/vpis/VpisManager.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/vpis/VpisCollector.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/vpis/StateInfo.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/vpis/OvisSystemState.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/vpis/VpisServlet.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/ovgeneric/GmGeneric.class:
None
/opt/OV/SIP/webapps/ovportal/WEB-INF/classes/com/hp/ov/
portal/modules/ovgeneric/ParmHandler.class:
None
cksum(1) Output:
HPOVSIP.OVSIP,fr=B.01.00,fa=HP-UX_B.11.00_32/64,v=HP:
2370527457 19713 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/modules/ovgeneric/
GmGeneric.class
2439260779 3933 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/modules/ovgeneric/
ParmHandler.class
2897673003 18600 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/modules/vpis/
VpisManager.class
349652922 13978 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/modules/vpis/
VpisCollector.class
1503887792 408 /opt/OV/SIP/webapps/ovportal/WEB-INF/classes/
com/hp/ov/portal/modules/vpis/StateInfo.class
4037335016 2407 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/modules/vpis/
OvisSystemState.class
751738097 15145 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/modules/vpis/
VpisServlet.class
1432256221 6377 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/modules/ovo/
MessageCategory.class
2458822490 16339 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/modules/ovo/
SummaryView.class
4222866830 20161 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/modules/ovo/
DetailView.class
463087929 9394 /opt/OV/SIP/webapps/ovportal/WEB-INF/classes/
com/hp/ov/portal/modules/ovo/ListView.class
22323111 8784 /opt/OV/SIP/webapps/ovportal/WEB-INF/classes/
com/hp/ov/portal/modules/ovo/DBConnection.class
2872158610 17334 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/modules/bookmarks/
Bookmark.class
1464406487 1506 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/modules/bookmarks/Bookmark$
BookmarkObj.class
347478617 6547 /opt/OV/SIP/webapps/ovportal/WEB-INF/classes/
com/hp/ov/portal/modules/service/
SvcServiceConfigDoc.class
709061919 5647 /opt/OV/SIP/webapps/ovportal/WEB-INF/classes/
com/hp/ov/portal/modules/service/
SvcServerConfigDoc.class
2562552470 16378 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/modules/service/
SvcGraphServlet.class
1001206916 6598 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/servlet/ImageServlet.class
3566957897 16234 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/proxy/OVHTMLProxyer.class
2768798991 10634 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/proxy/OVProxyParser.class
3031996903 536 /opt/OV/SIP/webapps/ovportal/WEB-INF/classes/
com/hp/ov/portal/proxy/OVProxyParser$
ProxyException.class
625371335 2935 /opt/OV/SIP/webapps/ovportal/WEB-INF/classes/
com/hp/ov/portal/proxy/OVProxyParameters.class
2232085911 2277 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/proxy/OVProxyType.class
971837268 5378 /opt/OV/SIP/webapps/ovportal/WEB-INF/classes/
com/hp/ov/portal/proxy/OVProxyAttributes.class
909101479 3997 /opt/OV/SIP/webapps/ovportal/WEB-INF/classes/
com/hp/ov/portal/proxy/OVProxyConfig.class
2211164045 2260 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/util/OVURLEncoder.class
2267453811 14090 /opt/OV/SIP/webapps/ovportal/WEB-INF/
classes/com/hp/ov/portal/filter/
SimpleCustomerModel.class
810159400 1136 /opt/OV/SIP/conf/share/proxy/OVProxyType.dtd
3769470080 235 /opt/OV/SIP/conf/share/proxy/OVProxyType.xml
1154187484 3869 /opt/OV/SIP/conf/share/proxy/
OVProxyConfig.xml
2288115471 4048 /opt/OV/SIP/conf/share/proxy/
OVProxyConfig.dtd
2681899074 1034 /opt/OV/SIP/conf/share/modules/ovis/
InsightTemplate.dtd
3761603802 7276 /opt/OV/SIP/conf/share/modules/ovis/
Graphs.xml
1100284449 40014 /opt/OV/SIP/conf/styles/VPISModule_html.xsl
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_28912 PHSS_28254 PHSS_27769 PHSS_27756 PHSS_26379
Equivalent Patches:
OVSIPSOL_00027:
sparcSOL: 2.6 2.7 2.8
OVSIPNT_00026:
intelWIN2000: 1.00
Patch Package Size: 210 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_29301
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_29301.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_29301. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_29301.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_29301.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_29301.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
========================================================
BEFORE LOADING THIS PATCH...
- Stop the Tomcat server.
- If you want to reinstall SIP, then you will have to
remove the patch. Once the re-install is over you
can apply the patch again.
NOTE : Tomcat is not started after the patch is loaded
You will need to manually start it.
Also, in order to keep a history of the patches
installed on your system the post-install script
will attempt to copy the PHSS_29301.text file
to /opt/OV/SIP/patches. Please make
sure this file is in /tmp before installation.
========================================================
PHSS_29301:
The patch IS_00002 for OVIS4.0 should be installed on the
OVIS box for the fix 8606274452 to work.
-----End of Document ID: PHSS_29301------------------------------------------
Document ID: PHCO_29109
Date Loaded: 20030707
Title: s700_800 11.11 Pthread enhancement and fixes
Patch Name: PHCO_29109
Patch Description: s700_800 11.11 Pthread enhancement and fixes
Creation Date: 03/06/27
Post Date: 03/07/07
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.C-MIN-32ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.C-MIN-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.CORE-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.CORE-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
ProgSupport.PAUX-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
Yes
PHCO_29109: HANG
Some customers reported seeing the hang every few
hours of operation.
PHCO_27632: HANG
PHCO_25751: ABORT
PHCO_25226: OTHER
Performance degradation and sudden increase in
CPU utilization due to mutex contention.
Category Tags:
defect_repair enhancement general_release critical
halts_system manual_dependencies
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_29109
Symptoms:
PHCO_29109:
( SR:8606287920 CR:JAGae51853 )
Java processes can hang occasionally.
( SR:8606307157 CR:JAGae70190 )
Thread can get cancelled even though cancellation is
disabled.
( SR:8606307489 CR:JAGae70522 )
The pthread library does not export two functions that are
useful to the Java virtual machine.
PHCO_27632:
( SR:8606259440 CR:JAGae23758 )
Unexpected failure of thread cancellation may cause
application to hang.
( SR:8606269542 CR:JAGae33777 )
Enhancement:This product update is a member of a set
needed to enable a new mutex type which can be
unlocked by a thread other than the owner. The full
list of product updates required for the feature are
PHCO_27632 and PHCO_27633.
These product updates can be installed in any order.
If any of these product updates are not installed,
this product update will have no impact on your
system.
( SR:8606269545 CR:JAGae33780 )
pthread_mutex_destroy() takes longer to destroy a
mutex, when the mutex is operating in handoff
disabled mode.
PHCO_26466:
( SR:8606226668 CR:JAGad95731 )
pthread_mutex_destroy() intermittently returns
EBUSY even when there are no threads accessing the mutex.
( SR:8606231620 CR:JAGae00858 )
Enhancement: This product update is a member of a set
needed to enable "Release mode" functionality for
PTHREAD_PROCESS_SHARED mutexes.
The full list of product updates required for this feature
are: PHKL_26467, PHKL_26468, PHKL_26469 and PHCO_26466.
If any member of this set of product updates is not
installed, this product update will have no impact on
your system.
PHCO_25751:
( SR:8606226436 CR:JAGad95505 )
Pthread internal error is reported and core is dumped
Error message : "__pthread_startup: can't enable gang
scheduling".
( SR:8606232147 CR:JAGae01383 )
Software providers may observe performance deficiencies in
applications which heavily use shared mutexes. Performance
of a PTHREAD_PROCESS_SHARED mutex unlock operation is slower
than that of a PTHREAD_PROCESS_PRIVATE mutex, even in the
non-contended (i.e., no waiters) case.
The full list of product updates required for this feature
are: PHKL_26316, PHKL_26240, and PHCO_25751.
If any member of this set of product updates is not
installed, this product update will have no impact on your
system.
PHCO_25226:
( SR:8606186378 CR:JAGad55582 )
Heavy mutex contention seen when large number of
threads try to acquire a single mutex lock, leading
to performance degradation and sudden jump in CPU
utilization.
PHCO_24584:
( SR:8606200799 CR:JAGad69975 )
This patch is a member of a set of patches needed to enable
the HP-UX Processor Sets product (PROCSETS). When PROCSETS
product is installed, it will install the full set of
required patches for that product, including this patch.
If the HP-UX Processor Sets product is not installed, this
change will have no impact on your system.
PHCO_23846:
( SR:8606184540 CR:JAGad53747 )
This enhancement is to support initialized tls support for
Fortran OpenMP. Changes are made in pthread library.
Defect Description:
PHCO_29109:
( SR:8606287920 CR:JAGae51853 )
During normal operation, the Java Virtual Machine may
suspend a thread. When a thread gets suspended, it
could be holding internal pthread resources. This can
cause a deadlock.
Resolution:
Solution is to ensure target does not get suspended while
holding internal pthread resources
( SR:8606307157 CR:JAGae70190 )
The cancellation operation (pthread_cancel) can race with
cancel enable/disable (pthread_setcancelstate).
Resolution:
While cancelling a thread, detect that the thread has now
disabled cancellation.
( SR:8606307489 CR:JAGae70522 )
The pthread library does not export two functions that are
useful to the Java virtual machine.
Resolution:
libpthread will now export the two symbols
PHCO_27632:
( SR:8606259440 CR:JAGae23758 )
There is a race condition in thread cancellation path in
pthread library. This may cause an application to fail to
cancel a thread.
Resolution:
The race condition in the thread cancellation path is
removed by appropriate protection of the internal
cancellation structure.
( SR:8606269542 CR:JAGae33777 )
This enhancement provides a way to restart mutex
operation when a process owning a mutex terminates
abnormally.
Resolution:
This enhancement provides a new mutex type
PTHREAD_MUTEX_NO_OWNER_NP, which can be unlocked by a
thread other than the owner.
( SR:8606269545 CR:JAGae33780 )
There is a race in mutex destroy and mutex unlock
operation, which may occassionally result in
pthread_mutex_destroy() returning EBUSY on first
try.
Resolution:
The race condition in mutex unlock and mutex destroy
operation is eliminated by better handling of waiter
count updation.
PHCO_26466:
( SR:8606226668 CR:JAGad95731 )
The problem with pthread_mutex_destroy() is attributed
to the fact that, pthread_mutex_unlock() does not keep
track of the number of waiters accurately. The mutex
cannot be destroyed when there are waiters,
and hence EBUSY is returned by pthread_mutex_destroy().
Resolution:
The change introduced in this patch update will
accurately keep track of all the waiters.
( SR:8606231620 CR:JAGae00858 )
This product update enables enable
"Release mode" functionality for PTHREAD_PROCESS_SHARED
mutexes. "Release mode" for PTHREAD_PROCESS_SHARED
mutexes is a feature that can be used to increase the
performance of the mutex in some cases where
there is high contention for the mutex.
Previously all shared mutexes use a "handoff"
mechanism to operate on mutexes whereby a mutex
lock is never really released, but rather handed
over to the highest priority waiter, if any.
This was done to adhere to standards whereby a
low priority thread shall not acquire the mutex
when there is a higher priority POSIX realtime
thread waiting for the same mutex. This made
the protocol less efficient in some cases since
another running thread could acquire and release
the mutex interim, hence making progress. This
enhancement still uses the original "handoff"
mechanism as the default case, but allows the
selection of "Release mode" to turn off the
"handoff" mechanism if it is desired.
Resolution:
This product update employs the kernel
support delivered in PHKL_26467, PHKL_26468 and PHKL_26469
for enabling release mode for PTHREAD_PROCESS_SHARED
mutexes. The changes can be enabled either by using
the API (pthread_mutex_disable_handoff_np() or
pthread_mutexattr_disable_handoff_np()) or by
setting the environment variable
PTHREAD_DISABLE_HANDOFF=ON. Applications will not
adhere to real-time semantics if this functionality
is enabled, however it can avail the performance
benefits provided by this product update.
PHCO_25751:
( SR:8606226436 CR:JAGad95505 )
The gang scheduler is currently supported only in Default
pset,so the request to enable gang scheduling for a process
in non-default pset would fail. The pthread library does not
recognize this scenario, and it fails the startup of new
application.
Resolution:
The pthread_startup() function needs to bypass the gang
scheduling requests for processes in non-default psets.
( SR:8606232147 CR:JAGae01383 )
In the PTHREAD_PROCESS_SHARED mutex case, the unlock
operation always makes a system call to synchronize with
threads in other processes which may be waiting for the
mutex. This makes the code path significantly longer.
Resolution:
Change pthread_mutex_unlock(), in the case of a shared
mutex, to call a new light weight system call rather than
the existing system call. If that new system call is not
available, then use the regular system call instead.
(PHKL_26316, also required for this enhancement,
adapts the existing system call which handles waiters of
shared mutexes to coordinate with the light weight unlock
system call. PHKL_26240, also required for this
enhancement, provides the new light weight system call
for shared mutex unlock.)
PHCO_25226:
( SR:8606186378 CR:JAGad55582 )
When large number of threads contend for a single
mutex, there is lot of contention for the internal
locks used in the library. This results in
unnecessary yielding and sleeping by the waiters
preventing the lock owner to complete the job.
Resolution:
Modified existing implementation to reduce contention
and dependency on the internal lock.
PHCO_24584:
( SR:8606200799 CR:JAGad69975 )
This patch contains minor enhancements in pthreads library
to support the HP-UX Processor Sets product.
Resolution:
Enhancements added to support new pthread_pset_bind_np()
interface in pthreads library when Processor Sets product
is enabled.
PHCO_23846:
( SR:8606184540 CR:JAGad53747 )
This is an enhancement for Initialized Thread local storage
support for Fortran OpenMP.
Resolution:
Libpthread allocates memory for TLS and it is initialized
to zero. With new enhancement the allocated TLS memory will
be initialized with the initialization image for each load
module the pointer to which is passed by libc/linker.
Enhancement:
No (superseded patches contained enhancements)
PHCO_27632:
The new mutex type PTHREAD_MUTEX_NO_OWNER_NP.
Additional enhancements were delivered in a patch
this one has superseded. Please review the Defect
Description text for more information.
SR:
8606184540 8606186378 8606200799 8606226436 8606226668
8606231620 8606232147 8606259440 8606269542 8606269545
8606287920 8606307157 8606307489
Patch Files:
OS-Core.C-MIN-32ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libpthread.a
/usr/lib/libpthread_tr.a
OS-Core.C-MIN-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libpthread.a
/usr/lib/pa20_64/libpthread_tr.a
OS-Core.CORE-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libpthread.1
/usr/lib/pa20_64/libpthread_tr.1
OS-Core.CORE-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libpthread.1
/usr/lib/libpthread_tr.1
ProgSupport.PAUX-ENG-A-MAN,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/share/man/man3.Z/pthread_ldom_bind_np.3t
/usr/share/man/man3.Z/pthread_ldom_id_np.3t
/usr/share/man/man3.Z/pthread_num_ldomprocs_np.3t
/usr/share/man/man3.Z/pthread_num_ldoms_np.3t
/usr/share/man/man3.Z/pthread_num_processors_np.3t
/usr/share/man/man3.Z/pthread_processor_bind_np.3t
/usr/share/man/man3.Z/pthread_processor_id_np.3t
/usr/share/man/man3.Z/pthread_pset_bind_np.3t
/usr/share/man/man3.Z/pthread_spu_to_ldom_np.3t
what(1) Output:
OS-Core.C-MIN-32ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libpthread.a:
Pthread Interfaces
$Revision: libpthread.a: (#) depot-32pa CUP11.11
_BL2003_0627_2 PATCH_11.11 PHCO_29109 Fri Ju
n 27 18:01:32 PDT 2003 $
/usr/lib/libpthread_tr.a:
Pthread Interfaces
$Revision: libpthread_tr.a: (#) depot-32pa CUP11
.11_BL2003_0627_2 PATCH_11.11 PHCO_29109 Fri
Jun 27 18:02:10 PDT 2003 $
OS-Core.C-MIN-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libpthread.a:
Pthread Interfaces
$Revision: libpthread.a: (#) depot-64pa CUP11.11
_BL2003_0627_2 PATCH_11.11 PHCO_29109 Fri Ju
n 27 18:07:56 PDT 2003 $
/usr/lib/pa20_64/libpthread_tr.a:
Pthread Interfaces
$Revision: libpthread_tr.a: (#) depot-64pa CUP11
.11_BL2003_0627_2 PATCH_11.11 PHCO_29109 Fri
Jun 27 18:08:42 PDT 2003 $
OS-Core.CORE-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libpthread.1:
Pthread Interfaces
$Revision: libpthread.1: (#) depot-64pa CUP11.11
_BL2003_0627_2 PATCH_11.11 PHCO_29109 Fri Ju
n 27 18:04:37 PDT 2003 $
/usr/lib/pa20_64/libpthread_tr.1:
Pthread Interfaces
$Revision: libpthread_tr.1: (#) depot-64pa CUP11
.11_BL2003_0627_2 PATCH_11.11 PHCO_29109 Fri
Jun 27 18:05:22 PDT 2003 $
OS-Core.CORE-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libpthread.1:
Pthread Interfaces
$Revision: libpthread.1: (#) depot-32pa CUP11.11
_BL2003_0627_2 PATCH_11.11 PHCO_29109 Fri Ju
n 27 17:58:17 PDT 2003 $
/usr/lib/libpthread_tr.1:
Pthread Interfaces
$Revision: libpthread_tr.1: (#) depot-32pa CUP11
.11_BL2003_0627_2 PATCH_11.11 PHCO_29109 Fri
Jun 27 17:58:58 PDT 2003 $
ProgSupport.PAUX-ENG-A-MAN,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/share/man/man3.Z/pthread_ldom_bind_np.3t:
None
/usr/share/man/man3.Z/pthread_ldom_id_np.3t:
None
/usr/share/man/man3.Z/pthread_num_ldomprocs_np.3t:
None
/usr/share/man/man3.Z/pthread_num_ldoms_np.3t:
None
/usr/share/man/man3.Z/pthread_num_processors_np.3t:
None
/usr/share/man/man3.Z/pthread_processor_bind_np.3t:
None
/usr/share/man/man3.Z/pthread_processor_id_np.3t:
None
/usr/share/man/man3.Z/pthread_pset_bind_np.3t:
None
/usr/share/man/man3.Z/pthread_spu_to_ldom_np.3t:
None
cksum(1) Output:
OS-Core.C-MIN-32ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
2563175536 229214 /usr/lib/libpthread.a
2443626554 258870 /usr/lib/libpthread_tr.a
OS-Core.C-MIN-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
1325333956 435556 /usr/lib/pa20_64/libpthread.a
3382755246 489430 /usr/lib/pa20_64/libpthread_tr.a
OS-Core.CORE-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
3403220902 178176 /usr/lib/pa20_64/libpthread.1
3817631781 207816 /usr/lib/pa20_64/libpthread_tr.1
OS-Core.CORE-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
3128738369 159744 /usr/lib/libpthread.1
394456443 184320 /usr/lib/libpthread_tr.1
ProgSupport.PAUX-ENG-A-MAN,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
3591096921 8533 /usr/share/man/man3.Z/
pthread_ldom_bind_np.3t
3591096921 8533 /usr/share/man/man3.Z/pthread_ldom_id_np.3t
3591096921 8533 /usr/share/man/man3.Z/
pthread_num_ldomprocs_np.3t
3591096921 8533 /usr/share/man/man3.Z/
pthread_num_ldoms_np.3t
3591096921 8533 /usr/share/man/man3.Z/
pthread_num_processors_np.3t
3591096921 8533 /usr/share/man/man3.Z/
pthread_processor_bind_np.3t
3591096921 8533 /usr/share/man/man3.Z/
pthread_processor_id_np.3t
3591096921 8533 /usr/share/man/man3.Z/
pthread_pset_bind_np.3t
3591096921 8533 /usr/share/man/man3.Z/
pthread_spu_to_ldom_np.3t
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies:
PHCO_27632:
To enable the new mutex type which can be unlocked
by a thread other than the owner, the following
must be installed.
PHCO_27632
PHCO_27633.
These product updates can be installed in any order.
If any of these product updates are not insatlled,
this product update will have no impact on your
system.
PHCO_26466: To enable the process shared mutex performance,
the following must be installed: PHKL_26467, PHKL_26468,
PHKL_26469 and PHCO_26466. These product updates may be
installed in any order. If any of these product updates are
not installed, this product update will have no impact on
your system.
PHCO_25751: To enable the pthread shared
mutex performance enhancement, the following must be
installed: PHKL_26240, PHKL_26316, and PHCO_25751
PHCO_25226: Perf changes enabled by
pthread_mutex_disable_handoff_np() or
pthread_mutexattr_disable_handoff_np() or by setting the
environment variable PTHREAD_DISABLE_HANDOFF=ON. By default
these perf changes are disabled. The first API pthread_
mutex_disable_handoff_np() is for process wide disabling of
handoff mode in all mutexes. So is the env. variable. The
pthread_mutexattr_disable_handoff_np() takes as argument
pointer to pthread_mutexattr_t and can be used to disable
handoff mode for a particular mutex. The pthread_mutex_
disable_handoff_np() has no arguments and has to be called
by the main thread before any new threads are created.
"Handoff mode" is used to strictly adhere to certain
characteristics of POSIX real-time threads. If your
application does not use any real-time threads trying to
take mutex locks, you can call this new API to get the
performance benefits. To enable the TLS feature, the
following patches should also be installed: PHCO_23427 libc
cumulative patch PHSS_23441 linker cumulative patch
PHSS_23794 linker startup patch PHSS_23953 Fortran90 B.11.01
patch
Supersedes:
PHCO_27632 PHCO_26466 PHCO_25751 PHCO_25226 PHCO_24584 PHCO_23846
Equivalent Patches:
PHCO_29108:
s700: 11.00
s800: 11.00
Patch Package Size: 590 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHCO_29109
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_29109.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_29109. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHCO_29109.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_29109.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_29109.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_29109------------------------------------------
Document ID: PHCO_29029
Date Loaded: 20030707
Title: s700_800 11.11 libc cumulative patch
Patch Name: PHCO_29029
Patch Description: s700_800 11.11 libc cumulative patch
Creation Date: 03/06/27
Post Date: 03/07/07
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.C-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.C-MIN-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.CORE-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.CORE-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
ProgSupport.PROG-AUX,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
ProgSupport.PROG-AX-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
ProgSupport.PROG-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.SYS-ADMIN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
OS-Core.SYS-ADMIN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
Yes
PHCO_29029: ABORT MEMORY_LEAK HANG
PHCO_28427: ABORT HANG
PHCO_27434: HANG
Process Hang
PHCO_27910: ABORT CORRUPTION HANG
PHCO_26870: ABORT CORRUPTION HANG
PHCO_26124: ABORT CORRUPTION
PHCO_25452: ABORT HANG
PHCO_24942: ABORT CORRUPTION
PHCO_23427: CORRUPTION
PHCO_23772: CORRUPTION
PHCO_23093: CORRUPTION
Category Tags:
defect_repair enhancement general_release critical
halts_system corruption memory_leak manual_dependencies
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_29029
Symptoms:
PHCO_29029:
( SR:8606294826 CR:JAGae58519 )
A multi-threading Application, which calls gethostbyname
hangs on thread cancels.
( SR:8606303142 CR:JAGae66498 )
In a multi-threaded application, calling getcwd(3C)
in one thread, may cause API's that do operations
on files using a relative path in another thread,
to fail.
( SR:8606303454 CR:JAGae66809 )
The realpath() function returns a path with an
extra slash when called with a relative path from
the root directory.
( SR:8606310639 CR:JAGae73510 )
Memory related problems exist in functions pututline,
pututxline, scandir, mbrtowc and regerror. This may
leads to abort and core dumps.
( SR:8606315457 CR:JAGae78180 )
localtime(3C) core dumps.
PHCO_28427:
( SR:8606282083 CR:JAGae46026 )
Application hangs in free/realloc.
( SR:8606271895 CR:JAGae36074 )
When SBA is turned on, the program is compiled with the -z
option and it tries to free the same block twice,
a core dump results.
( SR:8606288623 CR:JAGae52554 )
Problem with res_update DNS library resolver routine.
( SR:8606293042 CR:JAGae56792 )
Superuser cannot restrict the paths set in the NLSPATH
environment variable for setuid root programs which
are using catopen(3C) and executed by others.
( SR:8606300530 CR:JAGae63999 )
calloc miscalculates the requirement
PHCO_27740:
( SR:8606264319 CR:JAGae28649 )
This product update is a member of a set needed to enable
the optional HP-UX Device IDs feature. Upon installation,
the HP-UX Device IDs bundle (DevIDs11i) will install the
full set of product updates (including this one) necessary
to enable the Device IDs feature.
If the HP-UX Device IDs product (DeviceIDs11i) is not
installed, this product update to HP-UX will have no impact
on your system.
PHCO_27434:
( SR:8606258699 CR:JAGae23018 ) Duplicate
( SR:8606261751 CR:JAGae26070 ) Duplicate
( SR:8606265515 CR:JAGae29801 )
When using popen(3S) in different threads or
popen(3S) and fork(2) simultaneously in different
threads, the process may hang if it is using
pclose(3S) subsequently.
( SR:8606262841 CR:JAGae27171 )
strtod(3C) returns the wrong end pointer, when
the first argument is "infinity".
PHCO_27910:
( SR:8606260114 CR:JAGae24434 )
getipnodebyname() routine returns incorrect results in
multi-threaded environment when it is called with an
IP address as the argument.
( SR:8606239772 CR:JAGae08197 )
Either or both of the following symptoms may appear
on a given system.
1. Service Guard may experience umount(2) failures.
2. System throughput and/or response time may
degrade when SPUs are added to a configuration
that includes significant getcwd(3C) activity,
for example in the SDET benchmark.
( SR:8606257150 CR:JAGae21456 )
opendir(3C) performance may be slow.
( SR:8606254777 CR:JAGae19108 )
gethostbyname() routine returns incorrect results in
multi-threaded environment when it is called with an
IP address as the argument.
( SR:8606251497 CR:JAGae17562 )
32bit applications running on 64 bit kernel,which call
getresuid(3C) or getresgid(3C) may abort and dump core on
systems with greater than 2GB physical memory.
( SR:8606245321 CR:JAGae11794 )
inetd(1M) daemon may hang on 11.11 trusted systems.
Inetd services will not work until "inetd -b" is run twice.
PHCO_26870:
( SR:8606239772 CR:JAGae08197 )
Either or both of the following symptoms may appear
on a given system.
1. Service Guard may experience umount(2) failures.
2. System throughput and/or response time may
degrade when SPUs are added to a configuration
that includes significant getcwd(3C) activity,
for example in the SDET benchmark.
( SR:8606260114 CR:JAGae24434 )
getipnodebyname() routine returns incorrect results in
multi-threaded environment when it is called with an
IP address as the argument.
( SR:8606257150 CR:JAGae21456 )
opendir(3C) performance may be slow.
( SR:8606254777 CR:JAGae19108 )
gethostbyname() routine returns incorrect results in
multi-threaded environment when it is called with an
IP address as the argument.
( SR:8606251497 CR:JAGae17562 )
32bit applications running on 64 bit kernel,which call
getresuid(3C) or getresgid(3C) may abort and dump core on
systems with greater than 2GB physical memory.
( SR:8606245321 CR:JAGae11794 )
inetd(1M) daemon may hang on 11.11 trusted systems.
Inetd services will not work until "inetd -b" is run twice.
PHCO_26124:
( SR:8606231691 CR:JAGae00927 )
A user built perl executable aborted when using getpwent(3C)
API.
( SR:8606225736 CR:JAGad94809 )
Enhancement providing pre-enablement for a future release of
libnsl functionality. The changes in this patch will have no
affect on your system.
( SR:8606233401 CR:JAGae02625 )
setlocale(3C) is resulting in core dump when an application
compiled with -z option calls setlocale(3C) more than ten
times with different locales and categories other than
LC_ALL.
PHCO_25452:
( SR:8606228311 CR:JAGad97368 )
On a system with duplicate utmpx entries, logname and
getlogin were reporting incorrect login-names for
the user.
( SR:8606199060 CR:JAGad68247 )
Deadlock occurs when one thread in the process is performing
a blocking read (via stdio interfaces like fgets), another
thread performs a fork() before the blocking thread could
return.
( SR:8606225942 CR:JAGad95015 )
Improve performance of getdate() and clock() in
multi-threaded environments.
( SR:8606225355 CR:JAGad94442 )
Application which uses localtime() aborts when built
with -z and environment variable TZ set to last entry
in /usr/lib/tztab
PHCO_24942:
( SR:8606212783 CR:JAGad81970 )
res_query dumps core with large numbers of file descriptors.
( SR:8606205180 CR:JAGad74356 )
regexec() does not handle multibyte characters correctly.
( SR:8606214105 CR:JAGad83296 )
memchr() returns NULL unexpectedly.
( SR:8606203226 CR:JAGad72400 )
When a file stream is opened in write-only mode, an
immediate fread() reported failure but an fread() which was
followed by a fwrite() reported success.
( SR:8606213123 CR:JAGad82310 )
directory (3C) API's mutex contention.
( SR:8606204965 CR:JAGad74141 )
Default SBA support for C++ applications.
( SR:8606211883 CR:JAGad81071 )
delmntent libc routine deletes the entire mnttab contents.
( SR:8606202970 CR:JAGad72144 )
When a file stream is opened in read-only mode, putw()
reports a success though sets the errno to EBADF.
( SR:8606206070 CR:JAGad75245 )
Performance degradation of mktime ().
( SR:8606183079 CR:JAGad52295 )
incorrect freeing of memory in update_mnttab may
result in core dump.
( SR:8606215963 CR:JAGad85135 )
11.11 libc patches install PA1.1 version libc library
under /usr/lib on PA2.0 system.
PHCO_24400:
( SR:8606204553 CR:JAGad73735 )
getwc() incapable of handling codeset GB18030.
( SR:8606201456 CR:JAGad70632 )
The libc is not IPv6 enabled.
( SR:8606188513 CR:JAGad57721 )
fstyp returns "unknown_fstyp" on VxFS version 4 disk layout
file system
PHCO_23427:
( SR:8606177629 CR:JAGad46861 )
ptsname corrupts heap SIGBUS may result
( SR:8606196622 CR:JAGad65825 )
Multithreaded application core dumps sometimes when
it uses the Name Service Switch calls like getXXent
and endXXent.
( SR:8606179946 CR:JAGad49168 )
New feature and not a defect. Initialized TLS support
in libc for 64 bit non-threaded applications.
( SR:8606239637 CR:JAGab20870 )
When environment variable TZ is not set, the variables
tzname[2] and timezone is set to hard coded values
corresponding to Eastern Standard Time.
( SR:8606172344 CR:JAGad41604 )
(1) Trusted system calls made on an 11.0 NIS system
causes a SIGSEGV core dump.
(2) Using "dns" as a source for databases other than
"hosts" causes a SIGSEGV core dump.
( SR:8606194571 CR:JAGad63779 )
getdate fails VSU test case
( SR:8606165366 CR:JAGad34660 )
mallinfo() returns incorrect arena/uordblks.
( SR:8606186527 CR:JAGad55731 )
M_BLOCK behavior for malloc not working correctly.
( SR:8606185046 CR:JAGad54248 )
malloc(3C) has a silent data corruption in fourth quadrant.
PHCO_23772:
( SR:8606185984 CR:JAGad55189 )
For those PA-32bit Threaded C Applications which uses C++
plugins and pthread/cma calls in static
constructor/destructor, may happen that destructors will be
called twice. Non-threaded PA-32 bit applications do not
have this problem.
PHCO_23093:
( SR:8606162328 CR:JAGad31644 )
Memory Corruption when using fwscanf routine with
%lc option.
( SR:8606162140 CR:JAGad31456 )
regcomp(3C) function fails to detect an extended
regular expression
( SR:8606170481 CR:JAGad39745 )
sigwait() does not work as cancellation point if
the thread is cancelled after it enters
__sigwait_sys().
( SR:8606172179 CR:JAGad41440 )
User cannot use C++ runtime library on 32 bit
application
( SR:8606175166 CR:JAGad44410 )
gettimeofday is very slow for certain vendors who
use it for time stamping.
( SR:8606164457 CR:JAGad33756 )
Global symbols in libc can conflict with one in
program causing SIGBUS.
( SR:8606102984 CR:JAGab69119 )
No externally supported method to pthread safe
dynamically loaded libs
Defect Description:
PHCO_29029:
( SR:8606294826 CR:JAGae58519 )
A multi-threaded application which calls gethostbyname() can
hang if several of the threads are cancelled.
Resolution:
Installed the cleanup handlers to free the resources upon
cancellation requests.
( SR:8606303142 CR:JAGae66498 )
In a multi-threaded application, calling getcwd(3C) in one
thread may cause an API that relies on relative path name
in another thread to fail.
Resolution:
Modified the getcwd algorithm so that this problem
does not occur.
( SR:8606303454 CR:JAGae66809 )
realpath() function adds a slash to separate working
directory from relative path (for processing) without
checking whether the working directory is root or not.
Resolution:
slash character to separate working directory from
relative path (for processing) is added after ensuring
the current directory is not root.
( SR:8606310639 CR:JAGae73510 )
In functions pututline(), pututxline() and scandir(), memory
leaks occur in certain situations where the process is on
the verge of running out of memory. If a NULL pointer is
passed as the second argument to mbrtowc(), it may core dump
if the application is compiled with -z. In function
regerror(), an out of bounds array access may cause
unpredictable results.
Resolution:
More checks added so that memory leaks, NULL pointer
dereferencing and out of bounds array access do not
take place.
( SR:8606315457 CR:JAGae78180 )
The TZ variable used by localtime(3C) is not properly
being evaluated.
Resolution:
The TZ variable used by localtime(3C) is now properly
being evaluated.
PHCO_28427:
( SR:8606282083 CR:JAGae46026 )
Libc malloc(3C) family of API's hang if the complete heap of
the process is exhausted and application calls
free()/realloc().This happens because of improper handling
of resources by malloc(3C) itself.
Resolution:
The hang problem in free()/realloc()/malloc() is resolved by
releasing the resource held by thread.
( SR:8606271895 CR:JAGae36074 )
When SBA is turned on, the program is compiled with the -z
option and it tries to free the same block twice,
a core dump results.
Resolution:
In the free(3C) code, an additional check is made to see
whether the block being freed is already free.
If so, free(3C) returns immediately.
( SR:8606288623 CR:JAGae52554 )
Under certain circumstances, large size packets received
by the res_update resolver routine were not handled
properly.
Resolution:
res_update now properly handles packets of all sizes.
( SR:8606293042 CR:JAGae56792 )
Catopen(3C) uses the paths listed in the NLSPATH
environment variable for opening the specified catalog
file. There is no option for the superuser to restrict
the paths listed in NLSPATH.
Resolution:
Catopen(3C) has been modified to restrict the paths
listed in the NLSPATH environment variable. The
restrictions are in effect for setuid programs owned
by root and executed by others. A new configuration
file, "/etc/default/nlspath", allows the superuser
to restrict the paths set by others in the NLSPATH
environment variable.
( SR:8606300530 CR:JAGae63999 )
calloc miscalculates the requirement
Resolution:
calloc properly calculate the requirement.
PHCO_27740:
( SR:8606264319 CR:JAGae28649 )
This product update contains a minor enhancement required to
enable the HP-UX Device IDs feature.
When AutoFS unmounts a filesystem, it obtains the device id
from the filesystem server. If that server is slow, or not
responding, there may be a delay of 15 seconds or more. On
systems with many AutoFS managed filesystems and many slow
or non-responding servers, the cumulative delay may be quite
significant.
Resolution:
Ensure that each filesystem's device IDs are made available
in the /etc/mnttab file (mounted filesystem table) only if
the optional HP-UX Device IDs feature is enabled.
PHCO_27434:
( SR:8606258699 CR:JAGae23018 ) Duplicate
( SR:8606261751 CR:JAGae26070 ) Duplicate
( SR:8606265515 CR:JAGae29801 )
When using popen(3S) in a multithreaded application,
the process can hang waiting in pclose(3S) because
of race conditions.
Resolution:
The popen(3S) and fork(2) were serialised to resolve
the race conditions.
( SR:8606262841 CR:JAGae27171 )
In strtod(3C), if the first argument is "infinity",
it is returning next to next character after
"infinity". But it is supposed to return next character
after "infinity".
Resolution:
strtod(3C) is modified in such a way that, if the
first argument is "infinity", then it will return
next character after "infinity".
PHCO_27910:
( SR:8606260114 CR:JAGae24434 )
When getipnodebyname() is called with an IP address
as the argument in a multi-threaded environment, the
static global variables may be corrupted as they were
not protected for threads.
Resolution:
The global variables are now protected for threads by
defining them locally to the function where they are used.
( SR:8606239772 CR:JAGae08197 )
Obtaining complete filesystem mount information can be a
performance problem for some applications on systems having
a large number of mounts.
Resolution:
Used the new system call which returns information for
multiple mounts with one call (rather than one per call).
( SR:8606257150 CR:JAGae21456 )
Path name searching is done twice which causes opendir
to be slower than necessary.
Resolution:
Path name search has been reduced to one from two calls
by altering the way the syscalls are made.
( SR:8606254777 CR:JAGae19108 )
When gethostbyname() is called with an IP address as the
argument in a multi-threaded environment, the static
global variables may be corrupted as they were not
protected for threads.
Resolution:
The global variables are now protected for threads by
defining them locally to the function where they are used.
( SR:8606251497 CR:JAGae17562 )
The APIs getresuid(3C) and getresgid(3C) call
pstat_getproc(2) syscall to get the real user,real group,
effective user, effective group, saved user and
saved group ids. But for a 32-bit application running on
a 64-bit kernel, there is a possibility of an error with
errno set to EOVERFLOW. Due to improper handling of this
errno in getresuid(3C) and getresgid(3C), made them to fail.
Resolution:
getresuid(3C) and getresgid(3C) have been modified to
handle the EOVERFLOW in the right fashion.
( SR:8606245321 CR:JAGae11794 )
Application calls any of the APIs getpwnam(3C),getpwuid(3C),
getgrgid(3C), or getgrnam(3C) and forks a new process.
In the context of the child process, it then closes all
open files.When any of the above mentioned APIs are
called again in the child context,the API tries to use
a cached file descriptor which was opened in the parent
context causing undesired results.
Resolution:
Libc source has been modified so that the APIs getpwnam(3C),
getpwuid(3C), getgrgid(3C) and getgrnam(3C) will not use
the cached file descriptor in the child context after
fork, if it is closed and reopened.
PHCO_26870:
( SR:8606239772 CR:JAGae08197 )
Obtaining complete filesystem mount information can be a
performance problem for some applications on systems having
a large number of mounts.
Resolution:
Used the new system call which returns information for
multiple mounts with one call (rather than one per call).
( SR:8606260114 CR:JAGae24434 )
When getipnodebyname() is called with an IP address
as the argument in a multi-threaded environment, the
static global variables may be corrupted as they were
not protected for threads.
Resolution:
The global variables are now protected for threads by
defining them locally to the function where they are used.
( SR:8606257150 CR:JAGae21456 )
Path name searching is done twice which causes opendir
to be slower than necessary.
Resolution:
Path name search has been reduced to one from two calls
by altering the way the syscalls are made.
( SR:8606254777 CR:JAGae19108 )
When gethostbyname() is called with an IP address as the
argument in a multi-threaded environment, the static
global variables may be corrupted as they were not
protected for threads.
Resolution:
The global variables are now protected for threads by
defining them locally to the function where they are used.
( SR:8606251497 CR:JAGae17562 )
The APIs getresuid(3C) and getresgid(3C) call
pstat_getproc(2) syscall to get the real user,real group,
effective user, effective group, saved user and
saved group ids. But for a 32-bit application running on
a 64-bit kernel, there is a possibility of an error with
errno set to EOVERFLOW. Due to improper handling of this
errno in getresuid(3C) and getresgid(3C), made them to fail.
Resolution:
getresuid(3C) and getresgid(3C) have been modified to
handle the EOVERFLOW in the right fashion.
( SR:8606245321 CR:JAGae11794 )
Application calls any of the APIs getpwnam(3C),getpwuid(3C),
getgrgid(3C), or getgrnam(3C) and forks a new process.
In the context of the child process, it then closes all
open files.When any of the above mentioned APIs are
called again in the child context,the API tries to use
a cached file descriptor which was opened in the parent
context causing undesired results.
Resolution:
Libc source has been modified so that the APIs getpwnam(3C),
getpwuid(3C), getgrgid(3C) and getgrnam(3C) will not use
the cached file descriptor in the child context after
fork, if it is closed and reopened.
PHCO_26124:
( SR:8606231691 CR:JAGae00927 )
When the domain name is set to null and when the
NSS (Name Service Switch) configuration is "files nis" for
password database, then the getpwent(3C) API dumps core
with the SIGBUS error. In the switch code, the destructor
for the same files backend is called second time.
Resolution:
The code flow is changed in such a way that the destructor
for the same files backend will not be called more than
once.
( SR:8606225736 CR:JAGad94809 )
Enhancement providing pre-enablement for a future release of
libnsl functionality. The changes in this patch will have no
affect on your system .
Resolution:
Provided a wrapper routine for libnsl.
( SR:8606233401 CR:JAGae02625 )
setlocale(3C) is dereferencing "NULL" pointer and resulting
in core dump while checking whether locales can be removed
from the cache or not.
Resolution:
setlocale(3C) will check for NULL pointer before
dereferencing a pointer during removal of locales
from the cache.
PHCO_25452:
( SR:8606228311 CR:JAGad97368 )
Due to duplicate entries problem in the utmpx file, we had
more than one entry for the same pts/pty/tty. This leads to
a situation wherein only one of the entries in the
/etc/utmpx file is correct and signifying the current
session of the user and the rest of the entries being
incorrect. They correspond to processes that no-longer
exist but still are marked as user processes. logname and
getlogin would report incorrect username in this case.
Resolution:
The fix takes into account the current session for a
particular terminal. It compares the session id of the
calling process and the session id of the ut_pid entry in
the /etc/utmpx file to get the correct entry which is
the entry corresponding to the current user's session.
( SR:8606199060 CR:JAGad68247 )
The input stdio interfaces acquire a mutex and
perform a read. The read may block if there is no data
available on the stream. At that time, when fork() is
performed by another thread, the registered
atfork-handler also tries to acquire the same mutex
but as the mutex is held by a thread which is blocked
on I/O, it results in an indefinite wait causing a
deadlock.
Resolution:
The locking of the stdio mutex in atfork-handler has been
removed. With this fix, deadlock in parent will not occur
as reported in the defect.
( SR:8606225942 CR:JAGad95015 )
Improve performance of getdate() and clock() in
multi-threaded environments.
Resolution:
Reduced locking granularity in getdate() and clock() to
improve the performance in multi-threaded environments.
( SR:8606225355 CR:JAGad94442 )
Core dump occured because of a null pointer dereference
which happens when 1) Application is built with -z and
the environment variable TZ used is not in the file
/usr/lib/tztab
Or 2) when the application is built with -z and the
environment variable TZ is the last entry in the
/usr/lib/tztab.
Resolution:
The pointer is checked for null before de-referencing.
PHCO_24942:
( SR:8606212783 CR:JAGad81970 )
res_query() dumps core when called through a large number of
threads simultaneously from a single process as the socket
descriptor may cross 2048 which is the current limit.
Resolution:
The code has been modified to handle any number of threads
(limited by system resources only) as the limit on socket
descriptor is removed.
( SR:8606205180 CR:JAGad74356 )
regexec() does not handle multibyte characters correctly.
where the second byte of a multibyte SJIS character is
interpreted as stand alone single byte character.
Resolution:
For matching a pattern containing .* , .+ , regexec travers
es the entire length of the string and then backtracks to
find out if it can match the remaining part of the
pattern.The backtracking logic currently doesn't take the
multi-byte scenario into consideration and goes back byte
by byte.In the case of a multi-byte character with a valid
character as a second byte, a match is found for the
second byte even though it is not a stand-alone character
and just forms part of a multi-byte character.
Now the code has been changed to take care of multi-byte
back tracking.
( SR:8606214105 CR:JAGad83296 )
memchr() returns NULL unexpectedly in the PA 2.0 Narrow mode
Resolution:
The above defect is because the higher order 32 bits were
not cleared. Now the instruction is added to clear the
higher order 32 bits in PA2.0 Narrow mode.
( SR:8606203226 CR:JAGad72400 )
There was a missed condition wherein a file stream which has
been opened in write-only mode, an immediate fread on the
stream failed but if the fread() followed after a fwrite()
didn't report an error.
Resolution:
Changes have been made to code in the fread() call.Check was
being made on the basis of _cnt field of the file stream and
the routine that sets the error (_filbuf()) was then being
called. The pathflow is different when the _cnt field is
greater than 0 (which is taken when fwrite() updates the
file stream and updates the _cnt field). _cnt greater than
0 denotes that there are bytes in the look-ahead buffer.
In case the file stream has been fflushed,the _cnt field
is set to 8192 (_DBUFSZ) when the stream is opened in
read-only mode. These cases, when the _cnt
is greater than 0 had not been taken into consideration
from the write-only mode of operation point of view.
Introduced a check to handle this.
( SR:8606213123 CR:JAGad82310 )
Application using the directory (3C) API's in
multithreaded environment got into mutex contention
problem, which resulted in 100% usage of the CPU resource
time.
Resolution:
The application was creating more than 1000 threads and also
openning ~50000 directories.
Since there are 50000 instances opendir(), there will be
50000 nodes in the directory mutex linked list. Under this
circumstance when multiple threads at the same time tries
to open/close directories, in an average there will be a
traversal of ~25000 nodes, during which the global mutex
will be locked.
Fix is to use 2 linked lists Inuse and Free in place of
one list. This eliminates lot of search time and mutex
contention. The 2 APIs opendir() and closedir() modified
to incorporate the new design, which provides direct
access to the required mutex.
( SR:8606204965 CR:JAGad74141 )
The existing PA C++ binaries performnace can be improved
significantly by providing the SBA support for small block
allocation.
Resolution:
mallopt(3C) is enhanced to provide a new commond M_SBA_ON
which will be used by libCsup, C++ initialization library.
The libCsup will call mallopt(M_SBA_ON, 1) in its
initialization routine, as a result the mallopt configures
the SBA with the predefined default values.
( SR:8606211883 CR:JAGad81071 )
delmntent libc routine deletes the entire contents if
mntent structure obtained from the call to getmntent
was passed to delmntent.
Resolution:
The defect is due to the returning of same global buffer
by getmntent call to an application and the same global
buffer being used in the delmntent libc call. The code
has been fixed to address the problem.
( SR:8606202970 CR:JAGad72144 )
When putw() fails, it is supposed to set the error flag
for the file stream, set the errno describing the error
occurred and return EOF. Only the errno was being set but
error flag of the file stream wasn't being updated due to
which EOF was not being returned.
Resolution:
Change has been made to flsbuf.c file in the _wrtchk()
routine wherein, in case no write permissions are found
for the file stream, the errno is set and EOF returned but
the file stream's errof flag wasn't being set. On return
from this call, file's error flag was being checked which
was not being set earlier and hence, it was being considered
as success.
( SR:8606206070 CR:JAGad75245 )
mktime takes the timezone specification from /usr/lib/tztab
file. Incase the application does a rapid switch between 2
invalid time zones then for each switch the tztab file is
accessed and searched for the required time zone. Hence for
each switch the file is read completely. This degrades the
performance of mktime.
Resolution:
The /usr/lib/tztab file is cached in memory local to the
process,the first time mktime is called,and each subsequent
call to mktime makes use of this cached data. This approach
reduces the number of disk read operations.
( SR:8606183079 CR:JAGad52295 )
freeing of an unallocated memory was done in
update_mnttab routine, which may result in coredump
of an application.
Resolution:
The problem was fixed by freeing only
the memory which was allocated through libc malloc
family calls.
( SR:8606215963 CR:JAGad85135 )
When cold installing 11.11, the postinstall script for
CORE-SHLIBS replaces the PA1.0 /usr/lib/libc.2 with a
with a PA2.0 version if needed.
When installing PHCO_23427 (or one of the superseded
patches PHCO_23772 and PHCO_23093) on a PA2.0 system,
this PA2.0 file gets replaced by a PA1.0 version.
Resolution:
Control scripts have been provided along with the
patch for placing the right version of libc library
under /usr/lib directory.
PHCO_24400:
( SR:8606204553 CR:JAGad73735 )
getwc() unable to handle Chinese codeset GB18030
Resolution:
getwc() depends on mbtopc() to convert file code to process
code.When Multibyte character is split across the buffer
mbtopc() detects this and returns number of more bytes
required to make this vaild character. The current getwc()
function works on the assumption that mbtopc() always
returns the number of more bytes required in case of a
mlltibyte split.But in case of gb18030 mbtopc() method
cannot tell the caller its a 2 or 4 byte, because both
two and four byte characters begin with the same byte
range (x81 - xFE). Now the routine mbtopc() in gb18030
method returns MB_CUR_MAX in case the multibyte character
is split across the buffer.Now to fix this getwc() is
changed not to depend on the return value from mbtopc()
in case of the multibye split.
( SR:8606201456 CR:JAGad70632 )
IPv6 functionality should be provided in libc.
Resolution:
The source code for networking APIs in libc
have been modified to effect IPv6 changes.
New APIs included :
getaddrinfo(),
getnameinfo(),
freeaddrinfo(),
gai_strerror(),
getipnodebyname(),
getipnodebyaddr(),
rcmd_af(),
rresvport_af(),
rexec_af()
The last three APIs are provided to enable IPv6 in
rcommands.
rlogin and remsh Applications call rcmd_af() and
rresvport_af() APIs and rexec calls rexec_af() API.
IP address to hostname resolution APIs:
The getaddrinfo(), getipnodebyname() APIs are provided
for name to address resolution. The getnameinfo() and
getipnodebyaddr() APIs are provided for address to name
resolution.
They work for both IPv4 and IPv6 hostnames and addresses.
freeaddrinfo() is used to free the linked list created
by getaddrinfo().
gai_strerror() is used to print error messages
corresponding to error values from getaddrinfo().
( SR:8606188513 CR:JAGad57721 )
fstyp command calls statvfsdev on VxFS version 4 disk layout
returns "unknown_fstyp". It fails on accessing initial inode
list extents block address which exceeds 32 bit addressing.
lseek64 should be used instead of lseek in __vx_fs_lseek.
Resolution:
Now the call to lseek is replaced with lseek64 by using a
compilation flag _FILE_OFFSET_BITS=64 in the makefile.
PHCO_23427:
( SR:8606177629 CR:JAGad46861 )
When the application is linked with libpthreads
ptsname() function may corrupt heap
Resolution:
The cause of this problem is instead of passing the sizeof
bytes allocated by malloc to the GET_TSS() function, the
sizeof the character pointer returned by malloc is passed
as an argument. So,it is always taking sizeof the character
pointer which is less than the number of bytes allocated
by malloc.
ptsname() is modifiied to pass the correct argument
( SR:8606196622 CR:JAGad65825 )
The getXXent call and endXXent functions call shl_unload()
function to unload the shared backend library when the
number of references to the backend instance structure is
zero. However, the library call shl_unload() on PA32
machine unloads the shared library regardless of whether
there are other references to it through other load
invocations. This causes the subsequent shl_unload call
fail with signal 11.
Resolution:
Removed the shl_unload call for PA32 architecture in
the SO_per_src_delete function.
( SR:8606179946 CR:JAGad49168 )
Initialized TLS support in libc for 64 bit non threaded
applications.
Resolution:
The initialization routine of Libc has changed to support
initialized TLS variables in a PA64 non threaded
applications. Both the archived and shared version of the
libraries have this enhancement. To get the complete
functionality of ITLS (Initilized thread local storage) the
following patches has to be installed.
PHSS_23441- linker core
PHSS_23794 - linker ISU
PHCO_23846 - libpthread
PHSS_23953 - Fortran compiler
Currently this feature is available with Fortran compiler
only.No changes are required to be done in libc when this
feature is made available for any other compilers.
( SR:8606239637 CR:JAGab20870 )
When the variable TZ is not set in the environment, in HP-UX
it defaults to EST5EDT which is the east coast time in US.
This poses problem in the environment of the processes that
(a) are started by init(1m)
(b) clear their environment (e.g. login (1), sendmail(1m) )
The hard coded value is inappropriate for any timezone other
than east coast of US and the difference is difficult to
track for countries like Australia which frequently update
their daylight timing rules
Resolution:
When the environment variable TZ is not set, tzset() checks
the default file /etc/default/tz for the timezone value and
sets timezone values based on that. The file
/etc/default/tz contains the timezone value set by tzset()
when the environment variable TZ is not set. The format for
the file is same as TZ format without the prefix "TZ=".
Please check environ(5) for TZ format. 1) if the
environment variable TZ is present, it takes precedence. 2)
if TZ is not present then the value contained in
/etc/default/tz is used for the default. 3) if
/etc/default/tz is not set then the default value is
equivalent to EST5EDT (Eastern Standard Time) of US.
(Install the Patch PHCO_24396 to get the sample
/etc/default/tz file. Please read "Special Installation
Instructions" field for more information on PHCO_24396
patch)
( SR:8606172344 CR:JAGad41604 )
When the APIs getprpwnam(), getgrnam(), getnetbyname(),
and getservbyname() are configured with the
/etc/nsswitch.conf file to search sources that do not
support these calls, the Name Server Switch engine code
unloads the sources and returns NSS_NOTFOUND. The source
"nis" doesn't support the trusted system call getprpwnam().
The source "dns" is only valid for the "hosts" database.
Thus, subsequent API getXXXbyYYY calls that try to search
sources that have been unloaded end up accessing invalid
locations, resulting in a SIGSEGV core dump.
Resolution:
If a source doesn't support an API getXXXbyYYY call,
don't unload the source. Just have the Name Server
Switch engine code return NSS_UNAVAIL.
( SR:8606194571 CR:JAGad63779 )
Insufficient handling of locale specific representation of
time in getdate(3C)
Resolution:
getdate() changed to be inline with UNIX 98 specifications.
( SR:8606165366 CR:JAGad34660 )
mallinfo() doesn't give correct memory statistics if the
application is multithreaded and uses multiple arenas. The
problem was introduced during multi arena enhancement. The
way mallinfo() designed works fine only for single arena,
but the problem starts when there are 2 or more arenas and
there is a overlapping brk value.
When multiple threads call malloc(3C) to allocate space,
each will be assigned an arena. Each arena will maintain
the start and end point of that arena. The arena_start
represents the starting heap address for this thread and
the end_arena represents the ending address. Assume 2
threads are say THREAD1 and THREAD2 running in parallel.
THREAD1 calls malloc(), malloc stores the the arena_start1
(current brk value say 0x1000 ) and extends the brk value
to predefined size and sets the end_arena1(0x4000),
similarly THREAD2(arena_start 0x4000, arena_end 0x8000). If
THREAD1 again calls malloc() and there is no pre-allocated
space in the arena, the brk value is increased and
arena_end will be set( 0x12000).
The mallinfo() will collect the size by visiting each arena
starting from arena_start till arena_end of that arena. In
the above case arena_start and arena_end of THREAD1 is
0x1000 and 0x12000 respectively, for THREAD2 arena_start is
0x4000 and arena_end is 0x8000 respectively. While counting
the size, arena for THREAD2 will be counted 2 times, once
with arena1 and once with arena2. Hence the problem. In
single arena implementation this problem will not be
revealed.
Double counting is happening because we will modify the
dummy header when lastbrk != curbrk. The dummy header which
had SIZE=0 and USED set, will be set with the difference of
curbrk and lastbrk. If the lastbrk of one thread is not
equal to the curbrk, the possibility is that either user
application called brk/sbrk or some other thread expanded
the brk value. If the curbrk value is changed from some
other thread then the other thread treats this as the user
allocation and the dummy header is modified appropriately
and fixes the arenaend for this thread.
The problem will be there if there is a overlap between the
brk values of the different arenas. So in the current
implementation USER_ID is used when
O The application directly calls brk/sbrk O The other arena
calls brk/sbrk
The problem is because of setting USER_ID when the other
arena calls brk/sbrk.
Resolution:
The resolution is basically to avoid the use of USER_ID
when the other arena calls brk/sbrk. A new memory block
identifier ARENA_ID is defined in malloc.c as
The ARENA_ID is used to mark that the memory block is used
and it is used by some arena. The used memory block will be
marked with ARENA_ID under the circumstance mentioned
below.
O When a block of memory is used by some other arena and
the last brk value maintained in the that arena is not
equal to the _curbrk. While counting memory usage
statistics in mallinfo(), the memory block with ARENA_ID as
the id we will skip because it is used by some other arena
and will be taken into account under that arena.
( SR:8606186527 CR:JAGad55731 )
The defect was due to blocking the signals after locking
the malloc mutexes in the case of multi threaded malloc.
When malloc/calloc/valloc/realloc is called in signal
handler and also the main thread of execution and there
are frequent signals to application. The application
becoming busy in locking and unlocking the malloc mutexes
resulting into application hang situation
Resolution:
Signals blocking is done before locking the mutexes.
Which avoids the too many mutex locks and unlocks.
( SR:8606185046 CR:JAGad54248 )
The defect was due to coalescing when the allocation is
switched from sbrk to mmap at 4th quadrant. The coalescing
was resulting to allocating the blocks of memory near the
stack, which leads to data corruption.
Resolution:
Resolution is to avoid coalescing near the quadrant 4
boundary.
PHCO_23772:
( SR:8606185984 CR:JAGad55189 )
When a C application uses C++ plugins and calls pthread/cma
calls in static constructor/destroctor, it was leading to
destructor being called twice. This was happening because
the C++ runtime initialization routine was invoked at a
point when the pthread library initialization would not have
been complete . During this time, constructor was invoking
pthread calls . This might have lead to destruction of the
shared data (static/global) in the libCsup.
Resolution:
Changes are made to libc so that C++ runtime initialization
routine is invoked only after the completion of pthread
library initialization.
PHCO_23093:
( SR:8606162328 CR:JAGad31644 )
Reading a single wide character with %lc or %lC
format string by fwscanf is not supposed to add a
terminating null character. This is specifically
mentioned in the man page. But fwscanf code with
%lc format string was adding a terminating null
character to the second location of the argument.
Resolution:
Code was changed to consider the "c" case for not
adding the terminating null character at the second
location of the argument to fwscanf.
( SR:8606162140 CR:JAGad31456 )
regcomp(3C) fails to detect an extended regular
expression match in the input data on HP-UX 11.00
using libc patch PHCO_20765 (or PHCO_22076) but
works on HP-UX 10.20 w/ PHCO_20441
Resolution:
Defect is fixed by adding an "alternate" flag
which is set when there is an alternate('|') option
in the regular expression.
( SR:8606170481 CR:JAGad39745 )
sigwait() does not work as cancellation point if the
thread is cancelled after it enters __sigwait_sys().
When cancelling a thread that is blocked on sigwait()
by means of pthread_cancel(), the blocked sigwait()
returns with EINTR rather than checking the cancellation
point before it returns and terminate the thread.
Resolution:
When the thread is cancelled, then __sigwait_sys returns
error EINTR and does not set errno. In sigwait we were
checking for errno and setting the cancellation point.
Now that has been modified to check for return value.
( SR:8606172179 CR:JAGad41440 )
User cannot use C++ runtime library on 32 bit application
without either using a C++ main program or explicitly
invoke the C++ runtime library's initialization
routine, _main, from the C ( or Fortran ) main program.
Resolution:
The definition of the __main_ptr variable is done in
libc_init routine. The same varible is defined as a
global variable in libcsup, which will point to the C++
runtime library initialization routine, _main. Thus,
when libcsup is linked into the program, the variable
_main_ptr will point to _main; otherwise, it will
contain 0.
Now, we have the following three scenerios when the
program is linked with libcsup.
1. Multithreaded Application linked with libc :
In this case, C++ runtime initialization routine
_main (of libcsup) is invoked through __main_ptr in
libc_init.c routine.
2. Single Threaded Application linked with libc :
In this case, C++ runtime initialization routine
_main (of libcsup) is invoked through __main_ptr in
libc _start.c routine.
3. Multithreaded Application linked with libcma :
In this case, C++ runtime initialization routine
_main (of libcsup) is invoked through __main_ptr
in libc_init routine and control won't come to
libc's _start.c routine as libcma's startup routine
is called.
( SR:8606175166 CR:JAGad44410 )
gettimeofday is very slow for certain vendors who
use it for time stamping because it calls a heavy
weight system call to get the current time of the
day.
Resolution:
A new API hrtime_t gethrtime(void) has been added
to libc. This API uses fast light weight system
call to get the nano seconds from certain time.
It does not give you the current time of day.
hrtime_t is a signed 64 bit number. This API will
only be available if the application is being
compiled in -Ae mode because 64 bit integer number
is not available in -Aa mode.
( SR:8606164457 CR:JAGad33756 )
Global symbols in libc can conflict with one in program
causing SIGBUS. In ptsname.c we have defined two global
symbols alpha and range_spec. They are symbols which are
used only by libc. They should not be visible to customers.
They can conflict with the user defined global symbols.
Resolution:
alpha is changed to __alpha and range_spec is modifed as
__range_spec, so that they follow libc conventions.
( SR:8606102984 CR:JAGab69119 )
On HP-UX if a nonthreaded application links to a
thread-safed library the link will fail due to
unresolved symbols.To resolve these symbols, it is
necessary to link the nonthreaded application to the
threads library libpthread.But linking to that library
makes the application threaded even if it creates
no threads. Providing POSIX 1c thread "stubs" in HP-UX
C language library have two direct effects for
nonthreaded applications. a) POSIX 1c threads symbols
are resolved if a nonthreaded application links to a
thread-safed library
b)We avoid the overhead of a real threads library --
especially the overhead associated with mutexes when the
nonthreaded application uses thread stubs
rather than real threads library procedures.
Resolution:
Stubs are provided for all pthread calls only in SHARED
LIBC FLAVORS of the HP-UX C Library.
These stubs do not have any functionality, these are
dummy functions returning zero except pthread_getspecific()
family of APIs which has full functionality implemented
in the stubs. Full functionality is provided in the stub
for the following pthread calls
* pthread_key_create()
* pthread_getspecific()
* pthread_setspecific()
* ptherad_key_delete()
* pthread_exit()
Stub call to pthread_self() returns 1
Stub call to pthread_equal(arg1, arg2) will return
(arg1 == arg2)
Stub call to pthread_create() and pthread_attr_init()
returns ENOSYS.
All other stub calls returns zero.
There are two special interfaces provided for checking
whether an application is linked to pthread library or not.
a) __is_threadlib_linked()
returns 1 for an applications linked to pthread
library otherwise returns zero.
b) __get_ismt()
returns 1 for applications linked with libcma
returns 2 for applications linked with libpthread
otherwise returns 0
Risks:
------
An application may inadvertantly pick up the stubs when it
intended to use the real pthreads APIs, or it may pick up
the stubs when it needs cma APIs or stubs. These are all
link order problems. An application that needs cma behavior
must link to libcma (or the cma stubs library) and must do
so in a supported link order,
i.e. the link line should be shared only and should
not contain "-lc" before -lcma.
So long as this condition is met, the correct cma functions
will be referenced. Similarly, a multithreaded application
that needs pthread threads library behavior must link to
libpthread and must do so in a supported link order, and
only use shared libc and libpthread.
eg : An applications wants to use pthread stubs then
the link order should be
$ cc test.c -lc -lpthread
An applications wants to use pthread library then the
link order should be
$ cc test.c -lpthread -lc
Enhancement:
No (superseded patches contained enhancements)
PHCO_27740:
This product update contains a minor enhancement
required to enable the HP-UX Device IDs feature.
Additional enhancements were delivered in a patch
this one has superseded. Please review the Defect
Description text for more information.
SR:
8606102984 8606162140 8606162328 8606164457 8606165366
8606170481 8606172179 8606172344 8606175166 8606177629
8606179946 8606183079 8606185046 8606185984 8606186527
8606188513 8606194571 8606196622 8606199060 8606201456
8606202970 8606203226 8606204553 8606204965 8606205180
8606206070 8606211883 8606212783 8606213123 8606214105
8606215963 8606225355 8606225736 8606225942 8606228311
8606231691 8606233401 8606239637 8606239772 8606245321
8606251497 8606254777 8606257150 8606258699 8606260114
8606261751 8606262841 8606264319 8606265515 8606271895
8606282083 8606288623 8606293042 8606294826 8606300530
8606303142 8606303454 8606310639 8606315457
Patch Files:
OS-Core.C-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libc.a
/usr/lib/libcres.a
/usr/lib/unix95.o
/usr/lib/unix98.o
OS-Core.C-MIN-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libc.a
/usr/lib/pa20_64/libcres.a
/usr/lib/pa20_64/unix95.o
/usr/lib/pa20_64/unix98.o
OS-Core.CORE-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libc.2
OS-Core.CORE-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libc.2
/usr/lib/pa11_32/libc.2
/usr/lib/pa20_32/libc.2
ProgSupport.PROG-AUX,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libp/libc.a
ProgSupport.PROG-AX-64ALIB,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libp/libc.a
ProgSupport.PROG-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libpicc.a
OS-Core.SYS-ADMIN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/newconfig/etc/default/nlspath
OS-Core.SYS-ADMIN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/newconfig/etc/default/nlspath
what(1) Output:
OS-Core.C-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libc.a:
$ PATCH_11.11/PHCO_29029 Jun 27 2003 12:21:12 $
/usr/lib/libcres.a:
$ PATCH_11.11/PHCO_29029 Jun 27 2003 13:02:59 $
/usr/lib/unix95.o:
None
/usr/lib/unix98.o:
None
OS-Core.C-MIN-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libc.a:
$ PATCH_11.11/PHCO_29029 Jun 27 2003 12:32:55 $
/usr/lib/pa20_64/libcres.a:
$ PATCH_11.11/PHCO_29029 Jun 27 2003 13:03:20 $
/usr/lib/pa20_64/unix95.o:
None
/usr/lib/pa20_64/unix98.o:
None
OS-Core.CORE-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libc.2:
$ PATCH_11.11/PHCO_29029 Jun 27 2003 12:39:03 $
OS-Core.CORE-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libc.2:
$ PATCH_11.11/PHCO_29029 Jun 27 2003 12:26:57 $
/usr/lib/pa11_32/libc.2:
$ PATCH_11.11/PHCO_29029 Jun 27 2003 12:26:57 $
/usr/lib/pa20_32/libc.2:
$ PATCH_11.11/PHCO_29029 Jun 27 2003 12:45:28 $
ProgSupport.PROG-AUX,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libp/libc.a:
$ PATCH_11.11/PHCO_29029 Jun 27 2003 12:53:29 $
ProgSupport.PROG-AX-64ALIB,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libp/libc.a:
$ PATCH_11.11/PHCO_29029 Jun 27 2003 13:01:15 $
ProgSupport.PROG-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libpicc.a:
$ PATCH_11.11/PHCO_29029 Jun 27 2003 12:28:08 $
OS-Core.SYS-ADMIN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/newconfig/etc/default/nlspath:
None
OS-Core.SYS-ADMIN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/newconfig/etc/default/nlspath:
None
cksum(1) Output:
OS-Core.C-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
3372644414 2537200 /usr/lib/libc.a
4098760185 67556 /usr/lib/libcres.a
1400633197 868 /usr/lib/unix95.o
294124086 868 /usr/lib/unix98.o
OS-Core.C-MIN-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
2345618369 4204500 /usr/lib/pa20_64/libc.a
1620681892 67206 /usr/lib/pa20_64/libcres.a
2151074788 1632 /usr/lib/pa20_64/unix95.o
2763618295 1632 /usr/lib/pa20_64/unix98.o
OS-Core.CORE-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
887296124 1860696 /usr/lib/pa20_64/libc.2
OS-Core.CORE-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
932788051 1855488 /usr/lib/libc.2
932788051 1855488 /usr/lib/pa11_32/libc.2
2702724918 1814528 /usr/lib/pa20_32/libc.2
ProgSupport.PROG-AUX,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
3887410243 2803260 /usr/lib/libp/libc.a
ProgSupport.PROG-AX-64ALIB,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
2651001909 4546490 /usr/lib/pa20_64/libp/libc.a
ProgSupport.PROG-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
501222856 2696660 /usr/lib/libpicc.a
OS-Core.SYS-ADMIN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
2396073988 626 /usr/newconfig/etc/default/nlspath
OS-Core.SYS-ADMIN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
2396073988 626 /usr/newconfig/etc/default/nlspath
Patch Conflicts: None
Patch Dependencies:
s700: 11.11: PHCO_24402
s800: 11.11: PHCO_24402
Hardware Dependencies: None
Other Dependencies:
PHCO_28427: 8606293042 (JAGae56792)
The behavior of programs with the following
characteristics may change after this patch is
installed:
* setuid program owned by root
* executed by others
* invokes catopen(3C)
* depends on the NLSPATH environment variable.
The configuration file, "/etc/default/nlspath" is
introduced to provide the solution. The man page
patch, PHCO_28894, has been delivered for this fix.
The man page patch must be installed to get details
about the new configuration file,
"/etc/default/nlspath", and the changed behavior of
catopen(3C). See nlspath(4) and catopen(3C).
Note for CDE: Few of the CDE products,which are
owned by root and depending on environment variable
NLSPATH are changed not to depend on environment
variable. If customer is using CDE products install
following patches for CDE products after
installing the libc patch.
PHSS_26492 - 11.11 CDE Base Periodic Patch
PHSS_26493 - 11.11 CDE Applications Periodic Patch
PHSS_26494 - 11.11 CDE DevKit Periodic Patch
PHSS_26498 - 11.11 XClients Periodic Patch
PHCO_27910: 8606257150 (JAGae21456) The opendir(3C)
performance benefit requires patch PHKL_26239. Both
PHCO_27910 and PHKL_26239 patches are required to
ensure full performance benefit. Installing any of
these 2 patches alone will not cause any adverse
effects to the system.
PHCO_27910: 8606239772 (JAGae08197) The following patches
are required to ensure full performance benefit.
PHKL_26467, PHKL_26239, PHCO_26242, PHCO_27120, PHCO_26331,
PHCO_26332, PHCO_26333 and PHCO_26334. Any of these
patches may be installed independently with no adverse
effects to the system.
PHCO_26870: 8606257150 (JAGae21456) The opendir(3C)
performance benefit requires patch PHKL_26239. Both
PHCO_26870 and PHKL_26239 patches are required to ensure
full performance benefit. Installing any of these 2 patches
alone will not cause any adverse effects to the system.
PHCO_26870: 8606239772 (JAGae08197) The following patches
are required to ensure full performance benefit.
PHKL_26467, PHKL_26239, PHCO_26242, PHCO_27120, PHCO_26331,
PHCO_26332, PHCO_26333 and PHCO_26334. Any of these patches
may be installed independently with no adverse effects to
the system.
Supersedes:
PHCO_28427 PHCO_27910 PHCO_27740 PHCO_27434 PHCO_26870 PHCO_26124
PHCO_25452 PHCO_24942 PHCO_24400 PHCO_23772 PHCO_23427 PHCO_23093
Equivalent Patches: None
Patch Package Size: 7100 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHCO_29029
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_29029.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_29029. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHCO_29029.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_29029.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_29029.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
If you use HP Process Resource Manager (PRM)
version 1.08 or 1.08.2, /opt/prm/bin/prm3d may
core dump at startup if this patch is loaded and
PRM is running.
The following message displays:
Assertion failed:!isLocked_,filedaemon.cc, line232
To solve the problem, load PRM C.02.00 or later
from the September 2001 (or later) Application
Release (AR) media. If you do not experience the
core dump at startup, you will probably not
encounter problems.
If libc patches are installed without rebooting,
applications currently running which are linked shared
against libc will still continue using the former version of
libc. If this presents a problem to any applications, you
should reboot.
PHCO_23427: JAGab20870
The tzset() behaviour have been changed to take default TZ
values from the file/etc/default/tz. A sample file is
released as patch PHCO_24396. The /etc/default/tz included
in the patch contains the earlier default value ie.,
EST5EDT. So unless the user explicitly changes the value
contained in the file the tzset changes are transparent to
the user. The file /etc/default/tz contains the timezone
value set by tzset() when the environment variable TZ is not
set. The format for the file is same as TZ format without
the prefix "TZ=". Please check environ(5) for TZ format.
The order of TZ setting is as follows.
1) if the environment variable TZ is present, it takes the
precedence.
2) if TZ is not present, then the value contained in
/etc/default/tz is used for default.
3) if /etc/default/tz is not set, then the default value is
equivalent to EST5EDT (Eastern Standard Time) of US.
Risks : If the customer already has made some customisations
in /etc/default/tz, installing PHCO_24396 will overwrite
the file.
-----End of Document ID: PHCO_29029------------------------------------------
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]