|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: IT Resource Center (support_feedback_at_us-support-mail.external.hp.com)
Date: Sun Aug 04 2002 - 11:18:43 CDT
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://www.itresourcecenter.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://www.itresourcecenter.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 800 10.X patch digest
Created: Sun Aug 4 3:05:05 PDT 2002
Table of Contents:
Document ID Title
--------------- -----------
PHNE_25341 s700_800 10.26 xntpd cumulative patch
PHKL_26817 s800 10.26 PM fixes
PHSS_27571 s700_800 10.20 OV NNM6.2 xnmloadmib -trapType option
PHSS_26182 s800 10.20 MC/ServiceGuard A.10.12 cumulative patch
PHNE_25172 s700_800 10.01 elm(1) supports MIME (RFC 1521/2), JIS
PHSS_26887 s700_800 10.X OV OB4.10 patch - SAP packet
PHSS_26221 s700_800 10.X OV OB4.10 patch - ORACLE8 packet
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHNE_25341
Date Loaded: 20020802
Title: s700_800 10.26 xntpd cumulative patch
Patch Name: PHNE_25341
Patch Description: s700_800 10.26 xntpd cumulative patch
Creation Date: 02/06/06
Post Date: 02/08/02
Hardware Platforms - OS Releases:
s700: 10.26
s800: 10.26
Products: N/A
Filesets:
InternetSrvcs.INET-ENG-A-MAN InternetSrvcs.INETSVCS-BOOT
Automatic Reboot?: No
Status: General Release
Critical:
No (superseded patches were critical)
PHNE_24476: ABORT
Path Name: /hp-ux_patches/s700_800/10.X/PHNE_25341
Symptoms:
PHNE_25341:
xntpd logs unnecessary audit records
PHNE_24476:
Partial port of 10.20 patch PHNE_23717
JAGad58537 / SR 8606189322: xntpd core dumps.
PHNE_18261:
ntp does not perform trusted auditing, only system auditing
Defect Description:
PHNE_25341:
xntpd fills up the audit log with unnecessory information
Resolution:
Code has been modified to avoid logging unnecessary records
PHNE_24476:
Partial port of 10.20 patch PHNE_23717
JAGad58537 / SR 8606189322: xntpd core dumps with SIGSEGV.
Resolution:
Now xntpd does not core dump.
PHNE_18261:
ntp does not do trusted auditing
Resolution:
implemented xntpd as a multilevel daemon, added trusted
addendum to xntpd(1M), ntpq(1M) and ntpdate(1M)
SR:
8606189322
Patch Files:
/usr/sbin/xntpd
/usr/sbin/ntpdate
/usr/share/man/man1m.Z/xntpd.1m
/usr/share/man/man1m.Z/ntpq.1m
/usr/share/man/man1m.Z/ntpdate.1m
/etc/auth/system/files.fcdb/15.net/PHNE_18261.fcdb
what(1) Output:
/usr/sbin/xntpd:
2002/06/05 Hewlett-Packard HP-UX 10.26 TOS [ ic5gt -
DAV17 ]
01/06/27 services/INETSVCS/xntp/xntpd/ntp_control.c,
hpux, hpux_10.26, ic5gt Revision 1.2 PATCH_
10.26 (PHNE_24476)
99/04/21 services/INETSVCS/xntp/xntpd/ntp_io.c, hpux
, hpux_10.26, ic5gt Revision 1.3 PATCH_10.26
(PHNE_18261)
99/04/21 services/INETSVCS/xntp/xntpd/ntp_loopfilter
.c, hpux, hpux_10.26, ic5gt Revision 1.3 PAT
CH_10.26 (PHNE_18261)
99/04/21 services/INETSVCS/xntp/xntpd/ntpd.c, hpux,
hpux_10.26, ic5gt Revision 1.3 PATCH_10.26 (
PHNE_18261)
99/04/21 services/INETSVCS/xntp/xntpd/ntp_intres.c,
hpux, hpux_10.26, ic5gt Revision 1.1 PATCH_1
0.26 (PHNE_18261)
xntpd 3.4 #Revision 1.1.110.2: Wed Jun 5 19:24:45 G
MT 2002
Copyright 1992 David L. Mills
02/04/18 services/INETSVCS/xntp/lib/systime.c, hpux,
hpux_10.26, ic5gt Revision 1.2 PATCH_10.26
(PHNE_25341)
/usr/sbin/ntpdate:
2002/06/05 Hewlett-Packard HP-UX 10.26 TOS [ ic5gt -
DAV17 ]
99/04/21 services/INETSVCS/xntp/ntpdate/ntpdate.c, h
pux, hpux_10.26, ic5gt Revision 1.4 PATCH_10
.26 (PHNE_18261)
ntpdate 3.4 #Revision 1.1.110.2: Wed Jun 5 19:24:47
GMT 2002
Copyright 1992 David L. Mills
02/04/18 services/INETSVCS/xntp/lib/systime.c, hpux,
hpux_10.26, ic5gt Revision 1.2 PATCH_10.26
(PHNE_25341)
/usr/share/man/man1m.Z/xntpd.1m:
None
/usr/share/man/man1m.Z/ntpq.1m:
None
/usr/share/man/man1m.Z/ntpdate.1m:
None
/etc/auth/system/files.fcdb/15.net/PHNE_18261.fcdb:
99/04/21 etc/auth/system/files.fcdb/15.net/PHNE_1826
1.fcdb, hpux, hpux_10.26, ic5ca Revision 1.1
PATCH_10.26 (PHNE_18261)
cksum(1) Output:
1791851461 167936 /usr/sbin/xntpd
981781417 61440 /usr/sbin/ntpdate
963190725 14738 /usr/share/man/man1m.Z/xntpd.1m
2122406339 7860 /usr/share/man/man1m.Z/ntpq.1m
4290151870 3869 /usr/share/man/man1m.Z/ntpdate.1m
2885530080 444 /etc/auth/system/files.fcdb/15.net/
PHNE_18261.fcdb
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_18261 PHNE_24476
Equivalent Patches: None
Patch Package Size: 310 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_25341
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHNE_25341.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHNE_25341. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHNE_25341.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_25341.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHNE_25341------------------------------------------
Document ID: PHKL_26817
Date Loaded: 20020802
Title: s800 10.26 PM fixes
Patch Name: PHKL_26817
Patch Description: s800 10.26 PM fixes
Creation Date: 02/05/28
Post Date: 02/08/02
Hardware Platforms - OS Releases:
s800: 10.26
Products: N/A
Filesets:
OS-Core.CORE-KRN
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_26817: PANIC
Path Name: /hp-ux_patches/s800/10.X/PHKL_26817
Symptoms:
PHKL_26817:
Porting of 10.20 patch PHKL_21934 to TOS
(PHKL_21934:)
(SR: 8606139862 CR: JAGad09174)
Possible data page fault panic related to internal thread
manipulation. Panic stack trace may vary.
(PHKL_21517:)
(SR: 8606131455 CR: JAGad00605)
System panics with trap type 15, data page fault. The
stack may look like:
resume_cleanup+0x378
resume+0x280
_swtch+0x138
real_sleep+0x330
_sleep_one+0x14
netisr_daemon+0x194
main+0x92c
$vstart+0x34
$locore+0x74
Defect Description:
PHKL_26817:
Porting of 10.20 patch PHKL_21934 to TOS
(PHKL_21934:)
(SR: 8606139862 CR: JAGad09174)
Race condition when inserting a thread onto a sleep queue
resulted in "ghosted" threads and pointers not correctly
updated.
Resolution:
Modify insertion routine to place thread at the end of the
queue if it is the lowest priority thread after walking the
queue. Update queue and thread pointers appropriately.
(PHKL_21517:)
(SR: 8606131455 CR: JAGad00605)
Some routines used the value of the previous thread pointer
without verifying that it was valid, resulting in a trap
type 15 and a system panic.
Resolution:
We now verify that the previous thread pointer is valid
before dereferencing it.
SR:
8606131455 8606139862
Patch Files:
/usr/conf/lib/libhp-ux.a(pm_swtch.o)
/usr/conf/lib/libhp-ux.a(syscall.o)
/usr/conf/lib/libhp-ux.a(trap.o)
what(1) Output:
/usr/conf/lib/libhp-ux.a(pm_swtch.o):
02/04/18 kern/sys/pm_swtch.c, hpux, hpux_10.26, ic5g
s Revision 1.7 PATCH_10.26 (PHKL_26817)
/usr/conf/lib/libhp-ux.a(syscall.o):
None
/usr/conf/lib/libhp-ux.a(trap.o):
trap.c $Date: 97/09/23 11:22:02 $ $Revision: 1.16
9.98.14 $ PATCH_10.20 (PHKL_12663)
cksum(1) Output:
923004258 20864 /usr/conf/lib/libhp-ux.a(pm_swtch.o)
551316813 5568 /usr/conf/lib/libhp-ux.a(syscall.o)
2462020934 26856 /usr/conf/lib/libhp-ux.a(trap.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHKL_26816:
s700: 10.26
PHKL_21934:
s800: 10.20
Patch Package Size: 110 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_26817
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHKL_26817.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHKL_26817. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHKL_26817.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_26817.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHKL_26817------------------------------------------
Document ID: PHSS_27571
Date Loaded: 20020731
Title: s700_800 10.20 OV NNM6.2 xnmloadmib -trapType option
Patch Name: PHSS_27571
Patch Description: s700_800 10.20 OV NNM6.2 xnmloadmib -trapType option
Creation Date: 02/07/29
Post Date: 02/07/31
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
OpenView Network Node Manager 6.2
Filesets:
OVPlatform.OVMIN,B.06.20.00
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_27571
Symptoms:
PHSS_27571:
Incorrect behaviour of xnmloadmib when MIBs were loaded
with the -trapType option , under the Japanese locale.
Defect Description:
PHSS_27571:
Loading of MIBs with the -trapType option was incorrectly
handled by xnmloadmib under the Japanese locale.
Resolution:
Modified xnmloadmib to load the MIBs with the -trapType
option under the Japanese locale.
SR:
8606264678
Patch Files:
/opt/OV/lib/libovsnmp.2
what(1) Output:
/opt/OV/lib/libovsnmp.2:
libovsnmp
rnetstat
HP OpenView SNMP Dev Kit NNM Release B.06.20
PATCH PHSS_27571, 07292002
HP Precision Architecture HP-UX 10.x
Copyright (c) 1990-2002 Hewlett-Packard Co., All Ri
ghts Reserved.
cksum(1) Output:
2199423695 2569872 /opt/OV/lib/libovsnmp.2
Patch Conflicts: None
Patch Dependencies:
s700: 10.20: PHSS_27332
s800: 10.20: PHSS_27332
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHSS_27572:
s700: 11.00 11.11
s800: 11.00 11.11
PSOV_03194:
sparcSOL: 2.6 2.7 2.8
NNM_00937:
intelNT: 4.00 4.01
intelWIN2000: 1.00
Patch Package Size: 2570 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_27571
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_27571.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_27571. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHSS_27571.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27571.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
WARNING: This patch should not be loaded unless the last
consolidated patch PHSS_27332 has been loaded.
To check if this patch is on your system use the
following command:
swlist -l product -l fileset PHSS_27332
If swlist cannot find the patch, then you will
need to obtain the PHSS_27332 patch and load it
before loading this patch.
========================================================
BEFORE LOADING THIS PATCH...
If there are any ovw sessions running on either the
Management Station or on any Management Consoles, these
sessions need to be closed. The "ovstop" command
should then be executed.
WARNING : the patch will not install if any
Network Node Manager processes are
detected.
BACKUP ALL OpenView DIRECTORIES TO TAPE. This
pre-caution ensures that if you have problems after
installing the patch, you will be able to restore your
current state from tape.
NOTE : ovstart is NOT executed after the patch is loaded
You will need to manually run ovstart.
Also, in order to keep a history of the patches
installed on your system the post-install script
will attempt to copy this <patch_name>.text file
to /usr/OV/ReleaseNotes/patches
(or /opt/OV/ReleaseNotes/patches). Please make
sure this file is in /tmp before installation.
========================================================
-----End of Document ID: PHSS_27571------------------------------------------
Document ID: PHSS_26182
Date Loaded: 20020730
Title: s800 10.20 MC/ServiceGuard A.10.12 cumulative patch
Patch Name: PHSS_26182
Patch Description: s800 10.20 MC/ServiceGuard A.10.12 cumulative patch
Creation Date: 02/07/08
Post Date: 02/07/30
Hardware Platforms - OS Releases:
s800: 10.20
Products:
ServiceGuard A.10.12
Filesets:
Cluster-Monitor.CM-CORE,A.10.12
Package-Manager.CM-PKG,A.10.12
Automatic Reboot?: No
Status: General Release
Critical:
Yes
PHSS_26182: ABORT
1. When using the unsupported contributed
cmsetsafety tool to disable and then re-enable
safety time, the tool fails to restore safety
time protection properly, resulting in node TOC.
2. ServiceGuard daemon cmcld aborts with the
message "DLPI error! dl_errno: 1, dl_unix_errno:
0." in syslog. This leads to a system TOC.
PHSS_24284: ABORT
4) SG cluster of more than 3 nodes with dual
heartbeat may fail with core if one heartbeat
network is disconnected for a while, then recovers
and later a second heartbeat network fails.
8) If a port-scanning utility such as the Linux
application "nmap" is executed against a node
running ServiceGuard version 10.12 or earlier, cmcld
on the node may hang and unexpectedly fail.
PHSS_22870: ABORT
1) SG clusters configured with fibre-channel cluster
lock disks may fail to obtain the lock before
exhausting the allowed retry time.
The SG cmcld daemon would log the following message
in syslog: "Unable to obtain Cluster Lock.
Operation timed out."
6) The cmcld logs the message, "timers delayed
x.x seconds". Though this message can be due
to a kernel latency issue outside the control of
ServiceGuard, there are also circumstances
which lead to this occurring without any
kernel latency. In these cases, the cluster
may reform with the same membership, or there
may be no cluster reformation. Another
possible symptom of this problem can occur
on a very static 1-node cluster where
there will be no heartbeat activity
and no other activity like package failures
for a long period of time. In this case,
a new node attempting to join the cluster
after this semi-dormant period of time
may lead to the existing node failing
with an assertion. The message would be,
"Assertion failed: (tsb_tmp).tsb_low <=
TICKS_PER_MAX_USEC, file: timers.c,
line: 739"
Path Name: /hp-ux_patches/s800/10.X/PHSS_26182
Symptoms:
PHSS_26182:
1. When using the unsupported contributed cmsetsafety tool
to disable and then re-enable safety time, the tool
fails to restore safety time protection properly,
resulting in node TOC.
2. ServiceGuard daemon cmcld aborts with the message
"DLPI error! dl_errno: 1, dl_unix_errno: 0." in syslog.
This leads to a system TOC.
3. When a shutdown(1m) command is run from two nodes
concurrently, it can cause cmhaltnode to fail. This can
happen if one node has completed its cmhaltnode and the
other node is still running cmhaltnode. This problem can
also be seen if a cmhaltnode command is halting the
cluster on one node and another node in the cluster does
a TOC or a reboot before the cmhaltnode command
completes.
The /etc/rc.log.old will contain messages or command
will exit with messages like:
Warning: Do not modify or enable packages until the
halt operation is completed.
Halting Package <pkg_name>
cmhaltnode : Unable to halt package <pkg_name>: Socket
is not connected
Check the syslog and pkg log files for more detailed
information:
cmhaltnode : Warning : node failed to HALT
ERROR: Unable to halt cluster on this node.
4. cmsnmpd will not store cluster name in the mib
definition when started while cluster or local
node are halted. A call to "resls /cluster/status"
will result in output which is missing the cluster
name.
5. When nodes configured for a particular package are only
a subset of the nodes in the cluster, a call to
cmGetstatus(CM_PKG_STATUS) may return -26, causing
cmsnmpd to sever the socket connection with the
ServiceGuard cmcld daemon. This behavior will happen
when the user brings up the cluster or node and/or
restarts the cmsnmpd subagent. Once the socket
connection with SG is severed, no MIB variables or SNMP
traps will be updated or sent, which results in stale
data in the SG MIB table.
6. The cmsnmpd subagent will store the package status
as unknown, instead of down in the Serviceguard MIB
table when a package's node fails and the package is
not restarted.
PHSS_24284:
1. When certain ServiceGuard events are generated or the
cmsnmpd subagent is brought up when the local node or
cluster is down, the snmpdm agent will log
"CloneVarBind: Unable to clone vb->value.os_value"
messages in the /var/adm/snmpd.log file.
2. The service status reported by cmsnmpd once a package
has been halted is reported as unknown rather than down.
3. When the SG coordinator node is halted,
the cmsnmpd subagent on the new coordinator node
only updates the hpmcSGPkgCurrNode mib variable
for packages that failover after the coordinator
change. The hpmcSGPkgCurrNode mib value is
NULL for all other packages that
are still running in the cluster.
4. ServiceGuard cluster with serial link will fail if all
heartbeat network switches fail. The similar thing
with serial link can be seen if crossover cables are
used for all heartbeats and one of the nodes fails.
5. ClusterView and EMS do not display the correct status for
packages when a package is configured with a subnet that
is not available on all nodes in the cluster.
6. "Failed to release volume group <volume group name>"
error messages are printed in syslog by cmclconfd when
cmcheckconf, cmapplyconf, cmgetconf or cmquerycl are
issued. One possible side effect is that syslog may
report on cluster start that the cluster lock is not
initialized, although early on, after cmapplyconf, it
does report that cluster lock has already been
initialized. Another symptom is that subsequent tries to
create or import a VG may fail.
7. cmviewconf displays an incorrect HALT_SCRIPT_TIMEOUT
value for a package when the RUN_SCRIPT_TIMEOUT is
set to NO_TIMEOUT (0) and the HALT_SCRIPT_TIMEOUT
is set to a non-zero value.
8. If a port-scanning utility such as the Linux application
"nmap" is executed against a node running ServiceGuard
version 10.12 or earlier, cmcld on the node may hang and
unexpectedly fail.
9. When a local LAN failover fails, no error messages about
the failure are logged to syslog.
PHSS_22870:
1. SG clusters configured with fibre-channel cluster lock
disks may fail to obtain the lock before exhausting the
allowed retry time.
The SG cmcld daemon would log the following message in
syslog: "Unable to obtain Cluster Lock. Operation timed
out."
2. The SG cmclconfd daemon logs the error message
"Permission denied for user username on node nodename"
to syslog.log after cold installed Operating
Environment Update Release (OEUR) and rebooted.
3. cmquerycl hangs and numerous "Collision with another
configuration processes" messages shown in syslog.log.
4. ServiceGuard returns "Non-uniform connections" error
message when "cmquerycl -c clustername" is issued after
an online node addition. This happens when nodes of a
cluster have inconsistent lan configurations, i.e:
different lan ids on the same bridged net or different
number of lan cards on each node.
5. ServiceGuard logs error message "Unable to open
disk" in syslog.log when cmgetconf is issued on
clusters with XP disk array.
6. The cmcld logs the message, "timers delayed x.x seconds".
Though this message can be due to a kernel
latency issue outside the control of ServiceGuard, there
are also circumstances which lead to this occurring
without any kernel latency. In these cases, the cluster
may reform with the same membership, or there may be no
cluster reformation. Another possible symptom of this
problem can occur on a very static 1-node cluster where
there will be no heartbeat activity and no other activity
like package failures for a long period of time. In this
case, a new node attempting to join the cluster after
this semi-dormant period of time may lead to the
existing node failing with an assertion. The message
would be, "Assertion failed: (tsb_tmp).tsb_low <=
TICKS_PER_MAX_USEC, file: timers.c, line: 739"
7. MC/ServiceGuard node TOC'ed when the serial heartbeat
data gets corrupted. This can happen when the system
gets very busy.
PHSS_21995:
1. Log message indicating DLPI message corruption.
Possibilities include:
cmcld: DLPI message too small (112 < 68 + 48).
Ignoring the message.
cmcld: DLPI message checksum incorrect upon
completion. Group, 2, seems to be corrupting
the message.
cmcld: DLPI message not sent because oversized
(99999 + 48 > 9216).
cmcld: Length of DLPI header (0) is too small.
Ignoring the message.
cmcld: DLPI message too small (108 < 64 + 48).
Ignoring the message.
cmcld: DLPI message too big (99999 + 48).
Ignoring the message.
cmcld: DLPI message not sent because oversized
(99999 + 48 > 9216).
cmcld: The comm_link message length is inconsistant.
(48 < 999 + 24).
cmcld: DLPI message checksum incorrect upon receipt
from 3. Ignoring the message.
2. During extremely high memory & I/O loads on a system
and the cluster is reforming, a node may go down i.e.
TOC. Amessage in syslog like the following may appear
in /var/adm/syslog/OLDsyslog.log:
2173:Jul 21 12:38:56 node27 cmcld: Unable to accept
a connection: No buffer space available
3. DLPI errors returned from disconnected interface cards
during configuration stage.
4. ServiceGuard daemon(cmcld) generates a core dump upon
receiving a message from an unconfigured token ring
interface whose DLSAP address size is larger then 20
bytes.
5. ServiceGuard external logging daemon, cmlogd, exits too
early when a node is halted. Thus causes last minute
log messages don't show up in syslog.
6. ServiceGuard doesn't log error message indicating the
failure of IP address failback at default level when a
node is halted.
7. ServiceGuard cluster daemon(cmcld) may abort with error
messages: "Unable to send DLPI message, Interrupted
system call" followed by "Aborting! Failed to send over
DLPI"
8. Error messages confusing to customers are displayed in
syslog during lan failover.
9. Cluster fails to reform after a local switch.
10. If a user inadvertently kills the cmlvmd process, the
node will either reboot or TOC.
11. During a cmrunnode, if another node in the cluster
fails, there is a very small timing window which
could prevent the cluster from reforming and all
nodes will TOC with the message "Cluster Formation
Failed" appearing in syslog. This can only occur
on clusters of 3 or greater nodes.
12. ServiceGuard command cmhaltcl fails to halt all nodes
with the combination of a high value of HB_INTERVAL and
NODE_TIMEOUT.
13. If cmcld experiences unexpected interrupted system
calls,it could hit assertion core "Assertion failed:
inp->state == CL_NODE_ADDING"
14. The cmsnmpd agent could appear to hang and applications
querying the cluster MIB would get back an error
indication. The cmsnmpd agent would become responsive
after the next cluster event (such as membership
changes or package state changes).
15. On a non-coordinator node, cmsnmpd does not update the
hpmcSGPkgStatus mib value when the package switching
option is changed from enabled to disabled using
"cmmodpkg -d pkgname".
16. Umount in package control script fails, disabling
package failover.
17. ServiceGuard config commands(cmcheckconf, cmapplyconf)
consistently fail to configure a cluster with error
"Non-uniform connections detected". The problem is
more likely to occur on large cluster configurations
or when the network traffic is very busy.
18. MC/ServiceGuard node TOCd when corrupted DLPI packet
is received.
PHSS_21867:
1. A package takeover will fail if the mountpoint is busy,
even if the FS_MOUNT_RETRY_COUNT is set to >0 in
the package control script.
2. ServiceGuard daemon (cmcld) will dump core with "out
order message" error. This happens in dual heartbeat
configurations.
3. Second dual cluster lock not tried if first dual cluster
lock fails, leading to a cluster TOC. This problem only
impact cusomer using Dual Cluster Locks.
4. Cmcld TOCs with a SIGSEGV leading to a cmcld core in
/var/adm/cmcluster with a stack trace in dlpi_recv or
ns_if_setgood(). The cmcld is not resistant against
corrupted DLPI frames.
5. Package control script will fail during startup of a
package, if the mount point used by the package is
busy. The package startup will fail. This has been
the intended behavior.
Defect Description:
PHSS_26182:
1. When safety time is disabled, a timer is started to
simulate safety time protection, but when safety time is
re-enabled, the timer is not cancelled and eventually
pops, leading to node TOC.
Resolution:
Change support tool to cancel the timer when enabling
safety time.
2. This is actually a DLPI bug. The DLS provider somehow
returns dl_errno as 1, which means bad address, for a
temporary resource shortage. It should return dl_errno
as 4 with unix_errno as ENOBUFS or ENOSR instead so
ServiceGuard could handle this transient problem
accordingly.
Resolution:
A DLPI patch will be released to fix this problem.
The workaround solution in ServiceGuard is to
abort only if we receive the dl_errno 1 too frequently
in a relatively long period of time, which indicates
a permanent, serious problem. Otherwise, the problem
is transient and will be ignored.
3. The cmhaltnode command halts packages first. While
halting the packages if other nodes in the cluster
reboot or halt, the cluster communications for halting
the package may get disconnected, resulting in an error,
ENOTCONN. This error causes the cmhaltnode command to
exit out without halting the cluster.
Resolution:
If an ENOTCONN error is generated before completing the
cmhaltnode command, the command will now handle this and
will retry to halt cluster services again, but this time
the rebooted or halted node will not be used for the
cluster communications for the package being halted.
4. The fix submitted for JAGad68565 in
PHSS_24678 (SG11.13) and PHSS_24536 (SG11.09)
to intialize all Emanate Cluster related variables
to empty strings when the cluster or local node
wasn't running caused resls to show the cluster
name as an empty string if the local node is halted.
Resolution:
Change was made to initialize all status variables to
empty string when cmsnmpd first starts, independent
of whether the cluster or local node are up or down.
5. cmGetstatus() loops serially through each node in the
cluster when validating that each node the package is
configured to run on is actually in the cluster.
However, it incorrectly uses the number of nodes the
package is configured to run on instead of the number of
nodes in the cluster, so it may not do the validation
for all nodes that can run the package, and when this
happens, cmsnmpd severs its connection with cmcld.
Resolution:
cmGetstatus() was changed to use the number of nodes
in the cluster when validating each node that the
package can run on. The number of nodes in the
cluster had to be calculated as was done elsewhere
in cmGetstatus().
6. When cmsnmpd tries to determine if a package status has
changed when an node failure causes a cluster reconfig,
the valid/invalid bit is never checked and the
packages local flags aren't updated.
Resolution:
Changed cmsnmpd to update a package's local
flags and to identify a package status change when a
package status changes from invalid to valid after a
node failure or cluster reconfig.
PHSS_24284:
1. When the cmsnmpd agent is brought up or ServiceGuard
events are generated when the SG daemon, cmcld, is down
there's several cluster related variables that are left
uninitialized. The SG daemon, cmcld, is down when the
local node is halted or the cluster is down. These error
messages appear in the snmpd.log file when the cmsnmpd
subagent sends these uninitialized variables to the
SNMP Master agent, snmpdm.
Resolution:
Initialize all cluster related variables when cmsnmpd is
started.
2. The status is not updated when the service is halted.
Resolution:
The status is marked down before the callback is deleted.
3. The cmsnmpd on the non-coordinator nodes assigns a NULL
value for the hpmcSGPkgCurrNode mib variables, and
when the coordinator is halted, the SG API sends an
event to cmsnmpd on the new coordinator indicating
the current owner of all the packages. This NULL
value doesn't get overwritten by cmsnmpd on the new
coordinator node for all packages.
Resolution:
The fix involved updating the hpmcSGPkgCurrNode mib
varible when an SG API event is recieved by cmsnmpd on
the new coordinator node indicating the package is "up".
4. When all heartbeat networks goes down and serial device
is configured then node who notices these failures will
delay itself before going for cluster lock. This will
ensure that if other node is good then it can obtain
the cluster lock and form a one node cluster. But
if other node is down or also delayed then before this
node can acquire cluster lock, safety time may expire
and this node may TOC. In the case of heartbeat network
switch failure both nodes may delay themselves and the
whole cluster may fail.
Resolution:
To enforce the delay, more time is spent in FC state.
A very large number of FCs are sent if node notices that
it has serial device and all heartbeat networks are
down. This number of FCs is so huge that if other node
is also delayed or fails then this node will TOC as it
does not have enough time to form one-node cluster. The
recalculations are done for how many FCs are needed such
that the other node has enough time to get the lock and
form one-node cluster and if it does not do that, then
this node has enough time to form one-node cluster.
5. The cluster SNMP agent (cmsnmpd) incorrectly
dealt with a return value from a status lookup
on nodes on which the package subnet was not
available. This caused cmsnmpd to stop retrieving
status information from ServiceGuard.
Resolution:
The subagent was modified to deal with the case where a
node does not contain a subnet used by packages
configured for other nodes.
6. ServiceGuard config daemon cmclconfd passes an array
which contain physical volume name to a LVM
library function while trying to detach physical
volume groups during the device query process of
cmcheckconf/cmapplyconf. Later on, cmclconfd frees the
memory allocated for the array but LVM library keeps
using it. This leads to memory corruption and because
LVM cannot locate corrupted data for the physical
volume group, it cannot detach it, which leads to
the failure of releasing volume group. The cluster lock
disk not being able to initialize problem is a side
effect of this.
Resolution:
Make change such that LVM library makes copy of the
actual data, not of the pointer to physical volume name.
7. cmviewconf checks the wrong variable when determining
what value to display for HALT_SCRIPT_TIMEOUT.
Resolution:
Modify cmviewconf to check the correct variable when
determining what value to display for
HALT_SCRIPT_TIMEOUT.
8. Port-scanning utilities like "nmap" connect and
disconnect to the ServiceGuard ports very quickly without
sending any data. When cmcld detects a connection, it
makes a blocking accept() call to receive data.
Resolution:
Use a non-blocking accept() call with improved logic.
9. Error messages describing local LAN failover failures are
not logged to syslog in a production environment.
Resolution:
Make change such that the error messages are logged to
syslog in a production environment.
PHSS_22870:
1. This problem occurs because SG does not explicitly
recognize fibre-channel lock disks, rather they are
treated as a generic default and allowed a minimum
amount of retry time for cluster lock operations.
2. If an SG command is issued on the local system or
somewhere else in the network which requires invoking
cmclconfd, cmclconfd will check the .rhosts file to see
if the user has permission to execute it. After OEUR is
installed and the system is rebooted, there is no
.rhosts file in the system for cmclconfd to check.
Therefore, this is correct behavior. However, the message
should be less generic so customers will not panic.
3. The problem was due to cmclconfd closes fd 0 during
startup. DLPI network probing module could open fd 0,
but it uses fd 0 as an invalid fd, thus it never closes
fd 0. This resulted in the perpetually bound cmclconfd
to the DLPI port which eventually blocks all other
network probing due to the collision while binding to
this port. The resoluation is to make sure cmclconfd
open fd 0,1,2 as /dev/null, thus DLPI will never be
able to open fd 0 as it binds to DLPI port and a
retry timeout is implemented to break out the retry
in the cmclconfd client in case deadlock happenen from
an older version of cmclconfd.
4. When adding nodes online, ServiceGuard assigns
bridged net id for new nodes from scratch, without
using existing bridged net ids. This leads to
situations where existing nodes and newly added
nodes have different views of cluster's bridged nets
configuration. Once 'cmquerycl' is issued, SG checks to
see if lan cards on the same bridged net could talk
to each other. Since existing nodes and newly added
node have different views on which lan card is of which
bridged net, SG will check for connection between
lan cards that are actually not on the same bridged net.
This is where SG gives out the "Non-uniform connection"
error messages.
5. Problem occurred since cmgetconf tried to open all
entries in I/O trees that showed up under /dev/dsk.
However, some of these entries are not disks, like in
this case, disk controllers for XP disk array.
6. This problem occurred because the wrong thread inside
the cmcld intercepted the SIGALRM that was intended for
the timer loop thread.
7. When the serial link experiences an over-run or under-
run, the serial link code will attempt to find the next
message. In doing so if it finds what looks like a valid
header which has a correct header check sum, it
attempts to compute check sum for entire message.
Sometimes random bytes look like a valid header but
message length is very large. This very large value
causes cmcld to get a memory violation.
PHSS_21995:
1. Attempting to understand the cause the DLPI corruption.
The message encountered should reduce the possiblities.
Resolution: Added hardward information to an existing
message. Added another data verification to reduce the
window of possible causes.
The modified message is:
Net_id 3 received a DLPI message with an incorrect
checksum from net_id 2 on node tour.
Ignoring the message.
The new message is:
DLPI checksum incorrect - message corrupted during send.
2. When ServiceGaurd daemon 'cmcld' is attempting to
establish a heart beat connection a socket call returns
an error EAGAIN. This error causes cmcld to abort.
3. If a source interface is not physically connected, then
the sending will fail. In dual ported and quad-ported
hardwares, one or more ports often will not be used,
causing the sending to fail.
Resolution : Increased the log level so that this kind
of an error doesnt showup at a severity level of zero.
4. A buffer designed to store the ASCII representation of
the unconfigured DLSAP address was not allocated long
enough. Thus causes the stack corruption problem.
Resolution: The buffer size has been increased to hold
the largest DLSAP address of any interface type.
5. When a node is halted, cmcld shutdowns the cmlogd in
order to complete the service gracefully. This is
done with the attempt that any last minute messages will
be sending directly to syslog. However, there are a few
important networking log messages that have already been
sent to cmlogd and waiting to be written to syslog.
Therefore, upon exiting cmlogd service, these messages
will never make to syslog at all.
Resolution: The cmcld daemon has been changed to not
shutdown the cmlogd facility in order to allow last
minute messages to be written to syslog completely.
6. When a node is halted, ServiceGuard always attempts to
switch the stationary IP address back to its original
configuration. In few cases, where the switch fails due
to driver problem, ServiceGuard does not log the error
message at default level. Thus causing confusion for
users regarding the consistency of it's behaviour among
different revisions.
Resolution: The error message indicating the failure of
the IP failback has been updated so that it will show up
in syslog.
7. ServiceGuard does not handle the Interrupted system call
(EINTR) error code properly when putmsg() or getmsg()
returns it.
Resolution: Retry the system calls when the EINTR error
is returned.
8. Although lan failover works correctly, while it is
occuring, there is a window where DLPI returns
errors during driver reset. This produces error
messages customers could see in syslog.
Resolution: Log level was changed so error messages will
not appear in syslog anymore.
9. SG fails to reform cluster after a local switch due to
continuously broken General Service connections between
coordinator and member nodes.
Resolution: Reestablish General Service connections.
10. For a variety of reasons, system administrators will
sometimes need to kill system processes. The cmlvmd
process was not masking the signals commonly used
for this purpose. Thus if an administrator mistakenly
sent a kill signal to cmlvmd, it would terminate. This
in turn would cause cmcld to either reboot or TOC the
system.
Resolution: Added additional signal handling to
cmlvmd.
11. During the quiescence period of the cluster formation
for the new node joining, the new node is counted in
the last number of active nodes. When the existing
nodes dies, we go back to reform. We have to get
quorum of the last number of active nodes. But we only
accept votes from old members that were in the last
incarnation. So, our last number of active nodes is
too high.
Resolution: Set a flag to indicate when the last number
of active nodes includes nodes that aren't allowed to
vote and interpret this flag when calculating quorum.
12. The cmhaltcl fails to stick around long enough to halt
the last node in the cluster.
Resolution: To use the election timeout instead of the
node timeout to determine how long to wait for the
cluster to reform after halting each node during
cmhaltcl.
13. The procedure that makes the connect() does not handle
the EINTR code properly.
Resolution: When the connect call returns EINTR, we will
retry.
14. An error in a messaging library caused the cmsnmpd
agent to block on a socket read when no incomming
data was available. The next event message would clear
up the situation.
Resolution: Modified the messaging library to only
notify the caller when data is available.
15. The package switching bit in the hpmcSGPkgStatus mib
variable is never cleared when the Package Switching
option is changed from enabled to disabled. Without
the fix, cmsnmpd only updated this mib variable when
the Package Switching option was changed from disabled
to enabled.
Resolution: This was corrected by adding code to clear
the package switching bit in the hpmcSGPkgStatus mib
variable when the Package Switching option is changed
to disabled.
16. Umount call in control script fails since not all
processes have terminated before it starts.
Resolution: Retry 'Umount' for a number of times
specified by user. Sleep for a while in between so
processes would have time to act on fuser's signal.
17. There isn't any automatic retry mechanism available in
ServiceGuard's network probe area. Thus when several
network interfaces couldn't get probe messages from
other interfaces due to busy traffic, ServiceGuard
config commands prematurely determine the non-uniform
network connections between those interfaces.
Resolution: A retry mechanism has been implemented so
that missing probe messages will be re-transmitted
until they are received by their peers or until maximum
number of retries is reached.
18. MC/ServiceGuard tries to recover and log messages
including sender's node id when corrupted DLPI packet
is received. MC/ServiceGuard node TOCd while logging if
sender's node id is corrupted in DLPI packet.
Resolution: Algorithm is added to check validity of
sender's node id.
PHSS_21867:
1. The function in the package control script that
frees up a busy mount point does not handle the
input parameters passed to it correctly in all cases.
The problem only occurs if:
1. there are mount options and
2. if the retry count is set to > 0 and
3. if the mount point is busy
Resolution: Account for the case that the mount
options (which are operated on as a single parameter
in the freeup_busy_mountpoint_and_mount_fs() function)
are passed correctly.
2. When there is more than one network connection, it is
possible to have the 2nd connection to get established
after some messages has been sent thru the first
established connection. When we send the next message
on the 2nd connection, this message can arrive earlier
than the previous message sent thru the first connection.
Resolution: Changed the code to check for this condition.
3. When dual cluster locks are configured, if the request
to acquire the first cluster lock fails, the cluster
membership election is restarted -- if the request
failed because one or the other of the two lock disks
is down, the election will be restarted continuously
until safety time is exhausted, leading to a cluster TOC.
Resolution: changed dual cluster lock such that
1) if first dual lock fails at lock request, move on
and try second dual lock; 2) if first dual lock is
granted and second dual lock fails at lock request, SG
will assume cluster lock is granted and will move on
with cluster membership protocol.
4. DLPI buffer is corrupted
Resolution: Add checksum and size checks upon receipt.
Drop corrupted buffers after logging problem.
Add code to check the size of a message before sending.
5. The package control script tries to mount all the
logical volumes specified in the control script in
their specified mount points while starting a
package. If any one of these mount points is busy,
the mount operation in the control script will fail,
the package will not startup.
Enhancement:
The package control script is enhanced to allow
customer to specify a retry count to retry the mount
operation if the mount fails. A new configuration
variable, FS_MOUNT_RETRY_COUNT is added to the
package control script, to optionally set the number
of times the mount operation will be retried. During
each retry, fuser -k will be used to remove any
processes using the mount point.
SR:
8606141323 8606143447 8606143939 8606135914 8606106319
8606158792 8606155018 8606114259 8606129766 8606156893
8606145304 8606145229 8606109633 8606126975 8606141299
8606134738 8606130431 8606164978 8606161913 8606129359
8606165889 8606168354 8606188123 8606167794 8606156457
8606160805 8606165415 8606151921 5003416578 8606163578
8606199378 8606193167 8606194562 8606223632 8606198063
8606219681 8606200990 8606158555 8606140550 8606178310
4701391482 8606217091 8606231688 8606230697 8606232772
8606259876 8606234353 8606247612 8606251320 8606245185
8606254920 8606264328
Patch Files:
/usr/contrib/bin/cmsetlog
/usr/contrib/bin/cmsetsafety
/usr/lbin/cm/C/CMcore.ou
/usr/lbin/cm/C/CMpack.ou
/usr/lbin/cm/C/CMpack.ui
/usr/lbin/cmclconfd
/usr/lbin/cmcld
/usr/lbin/cmlogd
/usr/lbin/cmlvmd
/usr/lbin/cmsnmpd
/usr/lbin/cmsrvassistd
/usr/lbin/cmui
/usr/sbin/cmapplyconf
/usr/sbin/cmcheckconf
/usr/sbin/cmdeleteconf
/usr/sbin/cmgetconf
/usr/sbin/cmhaltcl
/usr/sbin/cmhaltnode
/usr/sbin/cmhaltpkg
/usr/sbin/cmhaltserv
/usr/sbin/cmmakepkg
/usr/sbin/cmmigrate
/usr/sbin/cmmodnet
/usr/sbin/cmmodpkg
/usr/sbin/cmquerycl
/usr/sbin/cmruncl
/usr/sbin/cmrunnode
/usr/sbin/cmrunpkg
/usr/sbin/cmrunserv
/usr/sbin/cmviewcl
/usr/sbin/cmviewconf
/usr/sbin/convert
what(1) Output:
/usr/contrib/bin/cmsetlog:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Local Comm
Util
Commands
/usr/contrib/bin/cmsetsafety:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Local Comm
Util
Commands
/usr/lbin/cm/C/CMcore.ou:
RCS $Header: CMcore.ou,v 80.1.1.1 99/02/05 16:18:55
ssa Exp $
/usr/lbin/cm/C/CMpack.ou:
RCS $Header: CMpack.ou,v 80.1.1.1 99/02/05 16:19:26
ssa Exp $
/usr/lbin/cm/C/CMpack.ui:
$Revision: 80.18.1.1 $
/usr/lbin/cmclconfd:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config Daemon
Config
Build date: Thu Jul 11 17:16:51 PDT 2002
Build id: ibld_sg_a1012_patch_opt
Command Cln
Command Srv
Local Comm
Util
Config DB
/usr/lbin/cmcld:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
Build date: Thu Jul 11 17:19:01 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Daemon
Cluster Monitor
Command Srv
Package Manager
CommunicationSrv
Network Sensor
Remote Comm
Local Comm
Util
Status DB
Status Database API
Config
Config DB
Service Sensor
Sync
Dlm
Cluster LVM
/usr/lbin/cmlogd:
Build date: Thu Jul 11 17:19:01 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Log Daemon
Local Comm
Util
/usr/lbin/cmlvmd:
Build date: Thu Jul 11 17:16:34 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Cluster LVM
Local Comm
Util
/usr/lbin/cmsnmpd:
Build date: Thu Jul 11 17:21:07 PDT 2002
Build id: ibld_sg_a1012_patch_opt
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
API
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
SNMPSUBAGENT
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
Copyright 1992-1996 SNMP Research, Incorporated
SNMP Research Distribution version 14.0.0.0
/usr/lbin/cmsrvassistd:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
Build date: Thu Jul 11 17:16:02 PDT 2002
Build id: ibld_sg_a1012_patch_opt
/usr/lbin/cmui:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
GUI
Config
Command Cln
Command Utils
Util
Local Comm
/usr/sbin/cmapplyconf:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmcheckconf:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmdeleteconf:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmgetconf:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmhaltcl:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmhaltnode:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmhaltpkg:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmhaltserv:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmmakepkg:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmmigrate:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmmodnet:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmmodpkg:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmquerycl:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmruncl:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmrunnode:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmrunpkg:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmrunserv:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmviewcl:
Build date: Thu Jul 11 17:19:32 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Commands
/usr/sbin/cmviewconf:
Build date: Thu Jul 11 17:21:31 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Tools
/usr/sbin/convert:
Build date: Thu Jul 11 17:21:31 PDT 2002
Build id: ibld_sg_a1012_patch_opt
A.10.12 Date: 06/28/2002; PATCH: PHSS_26182
Config
Command Cln
Command Srv
Command Utils
Local Comm
Util
Tools
cksum(1) Output:
4173846025 290816 /usr/contrib/bin/cmsetlog
4173846025 290816 /usr/contrib/bin/cmsetsafety
2761637911 621 /usr/lbin/cm/C/CMcore.ou
330706857 632 /usr/lbin/cm/C/CMpack.ou
1955992203 68539 /usr/lbin/cm/C/CMpack.ui
2440295455 475136 /usr/lbin/cmclconfd
2380025277 1445504 /usr/lbin/cmcld
1736233842 65536 /usr/lbin/cmlogd
3511076149 135168 /usr/lbin/cmlvmd
900751912 1277692 /usr/lbin/cmsnmpd
717763304 53248 /usr/lbin/cmsrvassistd
29332264 995328 /usr/lbin/cmui
1178875186 692224 /usr/sbin/cmapplyconf
1178875186 692224 /usr/sbin/cmcheckconf
1178875186 692224 /usr/sbin/cmdeleteconf
1178875186 692224 /usr/sbin/cmgetconf
1178875186 692224 /usr/sbin/cmhaltcl
1178875186 692224 /usr/sbin/cmhaltnode
1178875186 692224 /usr/sbin/cmhaltpkg
1178875186 692224 /usr/sbin/cmhaltserv
1178875186 692224 /usr/sbin/cmmakepkg
1178875186 692224 /usr/sbin/cmmigrate
1178875186 692224 /usr/sbin/cmmodnet
1178875186 692224 /usr/sbin/cmmodpkg
1178875186 692224 /usr/sbin/cmquerycl
1178875186 692224 /usr/sbin/cmruncl
1178875186 692224 /usr/sbin/cmrunnode
1178875186 692224 /usr/sbin/cmrunpkg
1178875186 692224 /usr/sbin/cmrunserv
1178875186 692224 /usr/sbin/cmviewcl
1937037493 577536 /usr/sbin/cmviewconf
1791188413 589824 /usr/sbin/convert
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_24284 PHSS_22870 PHSS_21995 PHSS_21867
Equivalent Patches: None
Patch Package Size: 7260 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_26182
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_26182.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_26182. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHSS_26182.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_26182.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
1) Halt ServiceGuard on the node the patch is
to be installed on.
2) Install the patch on that node.
3) Restart ServiceGuard on that node.
4) Patch needs to be installed on all nodes in the
cluster.
5) For the install, the ServiceGuard snmp subagent was
stopped and not automatically restarted. This
subagent is primarily used with the ClusterView
product. If this applies to you, then restart it
manually by executing the following command:
/usr/lbin/cmsnmpd
-----End of Document ID: PHSS_26182------------------------------------------
Document ID: PHNE_25172
Date Loaded: 20020729
Title: s700_800 10.01 elm(1) supports MIME (RFC 1521/2), JIS
Patch Name: PHNE_25172
Patch Description: s700_800 10.01 elm(1) supports MIME (RFC 1521/2), JIS
Creation Date: 02/07/22
Post Date: 02/07/29
Hardware Platforms - OS Releases:
s700: 10.01
s800: 10.01
Products: N/A
Filesets:
MailUtilities.MAILERS MailUtilities.MAIL-ENG-A-MAN
MailUtilities.MAIL-JPN-S-MAN MailUtilities.MAIL-JPN-E-MAN
OS-Core.UX-JPN-E-MSG OS-Core.UX-JPN-S-MSG
Automatic Reboot?: No
Status: Special Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHNE_25172
Symptoms:
PHNE_25172:
1. JAGaa45552 / SR 8606184872:
elm generates an invalid MIME-encoded header, when a
portion of the unencoded text is present in the encoded
header.
2. JAGaa62600 / SR 8606184873:
elm does not accept 8-bit characters in subject line.
3. JAGaa93235 / SR 5003448183:
When the length of the address list exceeds 256
characters elm fails with an error message,
"Too many addresses, or addresses too long!"
4. JAGab13395 / SR 1653301564:
When a mail is sent with a ":" in the comment text along
with the email ids in the "To:" address, elm garbles the
"To:" header field.
5. JAGab17360 / SR 1653305060:
elm does not support configurable folder permissions.
6. JAGab46340 / SR 8606111696:
elm drops the attachment(s) while replying to a mail
which has attachment(s).
7. JAGab68639 / SR 8606184875:
elm fails to expand the user/system aliases.
8. JAGac39335 / SR 8606123975:
elm unlinks the file which is attached while replying
to a mail which already has attachment(s).
9. JAGac40290 / SR 8606124898:
elm displays a wrong offset in the "Date:" field when
the date rolls over to next month.
10. JAGac59567 / SR 8606126726:
elm adds an extra empty attachment whenever a mail with
attachment is sent.
11. JAGad40143 / SR 8606170879:
mailfrom/newmail does not understand the new
configuration parameter 'folderperms' used in 'elmrc'
file and displays a sample error message as shown below.
'I can't understand sort key "folderperms" in line 226
in your ".elm/elmrc" file'.
12. JAGad45662 / SR 8606176424:
elm sometimes does not display the attachments in the
mail message.
13. JAGad50499 / SR 8606181282:
elm does not work properly in certain conditions.
14. JAGad62462 / SR 8606193250:
elm does not prompt for alias addresses and fails to
create new aliases in the command mode.
15. JAGad93852 / SR 8606224764:
elm formats the "To:" header field incorrectly in the
reply.
16. JAGae19074 / SR 8606254743:
The elm.1 man page does not provide information on
setting the configurable folder permissions with the
`folderperms' variable.
17. JAGae27581 / SR 8606263254:
If an elm2.4 patch is installed on a system which
already has elm2.0 patch, 'swverify' logs error
messages for elm2.0 patch deliverables.
PHNE_15836:
1. Elm is not considering the option set in elmrc file.
PHNE_13695:
1. Problem in elm with TERM environment variable.
2. ELM 2.4(PHNE_11925) will not see sys aliases if no user
aliases are defined.
3. ELM 2.4(PHNE_11925) -c option causes screen corruption.
4. ELM 2.4 does not show D status with arrow cursor.
5. Elm 2.4(PHNE_11925) has a problem in handling
JIS code implementation.
6. newmail and mailfrom are not working properly.
PHNE_11925:
1. The reply command produces a wrong destination address
since NIS domain name is not same as BIND domain name.
2. elm hangs when used in file input mode.
3. Latest elm patch PHNE_8143 does not show latest manpages.
PHNE_8143:
The following patch incorporates rfc 1522 in elm. It also
supports JIS for the japanese environment. This takes care
of MIME mails (i.e mails with audio, video attachments or
any other 8 bit data)
Defect Description:
PHNE_25172:
1. JAGaa45552 / SR 8606184872:
When a portion of the unencoded text is present in the
MIME-encoded header, the switching between ASCII mode
and non-ASCII modes does not happen properly.
Resolution:
The switching between ASCII mode and non-ASCII modes is
done properly.
2. JAGaa62600 / SR 8606184873:
The data type used to manipulate the characters in the
subject line does not handle 8-bit characters correctly.
Resolution:
The data type now handles the 8-bit characters
correctly.
3. JAGaa93235 / SR 5003448183:
The length of the buffer used to hold the "To:"
address list is limited to 256 characters.
Resolution:
The buffer size has been increased to 2560 bytes.
4. JAGab13395 / SR 1653301564:
If a message contains a ":" in the comment text in the
"To:" address list, then at the receiving end the "To:"
header is formatted incorrectly. In this case, elm was
misinterpreting the ":" in the comment text while
displaying the message.
Resolution:
Code has been modified to handle the problem.
5. JAGab17360 / SR 1653305060:
elm does not support configurable parameter for folder
permissions.
Resolution:
Now a configurable parameter "folderperms" is provided
in the elmrc file, where the user can set the values for
folder permissions. The default folder permission is
0640.
6. JAGab46340 / SR 8606111696:
elm ignores the attachment(s) while replying to a mail
which has attachment(s).
Resolution:
The code has been modified to fix the problem.
7. JAGab68639 / SR 8606184875:
The total number of aliases present in elm database is
not getting set to the proper value when elm enters into
the alias mode.
Resolution:
Code has been modified to set the total number of
aliases properly in the alias mode.
8. JAGac39335 / SR 8606123975:
elm unlinks the newly attached file during cleanup of
the temporary files used to store the previous
attachment.
Resolution:
Care has been taken not to unlink the newly attached
file.
9. JAGac40290 / SR 8606124898:
When the date rolls into the next month, elm calculates
incorrect GMT offset for a particular time interval.
Resolution:
The code has been modified to calculate the GMT offset
properly.
10. JAGac59567 / SR 8606126726:
elm adds an extra MIME boundary when a mail with an
attachment is sent.
Resolution:
Code has been modified not to add an additional MIME
boundary.
11. JAGad40143 / SR 8606170879:
The mailfrom and newmail utilities are unable to
distinguish between the 'folderperms' and 'folders'
parameters specified in the elmrc file.
Resolution:
Code has been modified to resolve the same.
12. JAGad45662 / SR 8606176424:
elm looks for MIME end boundaries in mail attachments.
It does not display those messages which do not have a
MIME end boundary since the length count of such
attachments is not updated.
Resolution:
Code has been modified to update the length count of the
messages, which do not have MIME end boundaries.
13. JAGad50499 / SR 8606181282:
elm does not work properly in certain conditions.
Resolution:
Code has been modified to resolve the same.
14. JAGad62462 / SR 8606193250:
elm always obtains the non-success return value even in
the case of success. Hence elm does not prompt for alias
addresses in command mode.
Resolution:
The return value is handled properly in case of success.
15. JAGad93852 / SR 8606224764:
elm does not extract the host name properly while
formatting the 'To' address in the reply header.
Resolution:
Code has been modified to interpret the host names
properly.
16. JAGae19074 / SR 8606254743:
When the elm code was modified to support the
'folderperms' variable, the elm.1 man page was not
updated.
Resolution:
The English version of the elm.1 man page has been
modified accordingly.
17. JAGae27581 / SR 8606263254:
The elm2.4 patch does not supersede elm2.0 patch and
the IPD entries for elm2.0 patch are not updated in the
SD database.
Resolution:
The control scripts for elm2.4 patch have been modified
to resolve the problem.
PHNE_15836:
1. Option in elmrc file to disable metamail for a
particular charset is not working.
PHNE_13695:
1. Problem in elm when TERM environment variable is set
with a string of more than 70 characters.
2. ELM 2.4(PHNE_11925) system aliases are not accessible
unless a user also has user aliases defined.
3. ELM 2.4(PHNE_11925) -c option clears the screen and
returns to prompt. No useful information is visible.
4. ELM 2.4 does not show deleted messages with the "D" mark
when used with the arrow (->) cursor.
5. Elm 2.4(PHNE_11925) has a problem in handling
JIS code implementation.
6. newmail and mailfrom are not working properly.
PHNE_11925:
1. elm adds the <hostname>.<NISdomain> where NISdomain is
different from BIND domain.
2. elm hangs, when invoked in the command line with file
redirection option for sending mails.
3. The previous patch PHNE_8143 was not removing the
manpages from cat1.Z, due to which the user was not
able to view the latest manpages.
PHNE_8143:
Elm was not designed to take care of MIME mails(i.e mails
with audio, video attachments or any other 8 bit data) .
SR:
8606263254 8606184872 8606184873 5003448183 1653301564
1653305060 8606111696 8606184875 8606123975 8606124898
8606126726 8606170879 8606176424 8606181282 8606193250
8606224764 8606254743 8606258978 4701381533 5003408047
5003408054 4701378695 4701399303 1653236695 1653218008
1653215624 4701354993 8606113012
Patch Files:
/usr/bin/elm
/usr/bin/readmail
/usr/bin/newalias
/usr/bin/mailfrom
/usr/bin/newmail
/usr/bin/fastmail
/usr/bin/elmalias
/usr/bin/answer
/usr/bin/printmail
/usr/bin/listalias
/usr/bin/checkalias
/usr/share/man/man1.Z/answer.1
/usr/share/man/man1.Z/elmalias.1
/usr/share/man/man1.Z/mailfrom.1
/usr/share/man/man1.Z/newmail.1
/usr/share/man/man1.Z/elm.1
/usr/share/man/man1.Z/fastmail.1
/usr/share/man/man1.Z/newalias.1
/usr/share/man/man1.Z/readmail.1
/usr/share/man/ja_JP.SJIS/man1.Z/answer.1
/usr/share/man/ja_JP.SJIS/man1.Z/elmalias.1
/usr/share/man/ja_JP.SJIS/man1.Z/mailfrom.1
/usr/share/man/ja_JP.SJIS/man1.Z/newmail.1
/usr/share/man/ja_JP.SJIS/man1.Z/elm.1
/usr/share/man/ja_JP.SJIS/man1.Z/fastmail.1
/usr/share/man/ja_JP.SJIS/man1.Z/newalias.1
/usr/share/man/ja_JP.SJIS/man1.Z/readmail.1
/usr/share/man/ja_JP.eucJP/man1.Z/answer.1
/usr/share/man/ja_JP.eucJP/man1.Z/elmalias.1
/usr/share/man/ja_JP.eucJP/man1.Z/mailfrom.1
/usr/share/man/ja_JP.eucJP/man1.Z/newmail.1
/usr/share/man/ja_JP.eucJP/man1.Z/elm.1
/usr/share/man/ja_JP.eucJP/man1.Z/fastmail.1
/usr/share/man/ja_JP.eucJP/man1.Z/newalias.1
/usr/share/man/ja_JP.eucJP/man1.Z/readmail.1
/usr/lib/nls/msg/C/elm.cat
/usr/lib/nls/msg/ja_JP.SJIS/elm.cat
/usr/lib/nls/msg/ja_JP.eucJP/elm.cat
/usr/share/lib/elm/elmrc-info
/usr/share/lib/elm/delta-doc
/usr/share/lib/elm/delta-doc.sjis
/usr/share/lib/elm/delta-doc.euc
what(1) Output:
/usr/bin/elm:
$Id: init.c,v 5.20 1994/05/30 16:31:40 syd Exp $
$Id: showmsg.c,v 5.16 1994/08/30 15:09:43 syd Exp $
$Id: signals.c,v 5.13 1994/09/01 19:42:39 syd Exp $
$Revision: 1.206.214.3 $ 10.01 [ELM 2.4] PHNE_25172
$
/usr/bin/readmail:
$Revision: 1.206.214.2 $
/usr/bin/newalias:
$Revision: 1.206.214.2 $
/usr/bin/mailfrom:
$Revision: 1.206.214.3 $ 10.01 [ELM 2.4] PHNE_25172
$
/usr/bin/newmail:
$Revision: 1.206.214.3 $ 10.01 [ELM 2.4] PHNE_25172
$
/usr/bin/fastmail:
$Revision: 1.206.214.2 $
/usr/bin/elmalias:
$Revision: 1.206.214.2 $
/usr/bin/answer:
$Revision: 1.206.214.2 $
/usr/bin/printmail:
$Revision: 1.1.213.1 $
$Id: printmail.SH,v 5.1 1992/10/04 00:46:45 syd Exp
$
/usr/bin/listalias:
$Revision: 1.1.213.1 $
$Id: listalias.SH,v 5.1 1993/04/12 02:10:26 syd Exp
$
/usr/bin/checkalias:
$Revision: 1.1.213.1 $
: checkalias.SH,v 5.2 1993/04/12 02:11:05 syd Exp $
/usr/share/man/man1.Z/answer.1:
None
/usr/share/man/man1.Z/elmalias.1:
None
/usr/share/man/man1.Z/mailfrom.1:
None
/usr/share/man/man1.Z/newmail.1:
None
/usr/share/man/man1.Z/elm.1:
None
/usr/share/man/man1.Z/fastmail.1:
None
/usr/share/man/man1.Z/newalias.1:
None
/usr/share/man/man1.Z/readmail.1:
None
/usr/share/man/ja_JP.SJIS/man1.Z/answer.1:
None
/usr/share/man/ja_JP.SJIS/man1.Z/elmalias.1:
None
/usr/share/man/ja_JP.SJIS/man1.Z/mailfrom.1:
None
/usr/share/man/ja_JP.SJIS/man1.Z/newmail.1:
None
/usr/share/man/ja_JP.SJIS/man1.Z/elm.1:
None
/usr/share/man/ja_JP.SJIS/man1.Z/fastmail.1:
None
/usr/share/man/ja_JP.SJIS/man1.Z/newalias.1:
None
/usr/share/man/ja_JP.SJIS/man1.Z/readmail.1:
None
/usr/share/man/ja_JP.eucJP/man1.Z/answer.1:
None
/usr/share/man/ja_JP.eucJP/man1.Z/elmalias.1:
None
/usr/share/man/ja_JP.eucJP/man1.Z/mailfrom.1:
None
/usr/share/man/ja_JP.eucJP/man1.Z/newmail.1:
None
/usr/share/man/ja_JP.eucJP/man1.Z/elm.1:
None
/usr/share/man/ja_JP.eucJP/man1.Z/fastmail.1:
None
/usr/share/man/ja_JP.eucJP/man1.Z/newalias.1:
None
/usr/share/man/ja_JP.eucJP/man1.Z/readmail.1:
None
/usr/lib/nls/msg/C/elm.cat:
None
/usr/lib/nls/msg/ja_JP.SJIS/elm.cat:
None
/usr/lib/nls/msg/ja_JP.eucJP/elm.cat:
None
/usr/share/lib/elm/elmrc-info:
None
/usr/share/lib/elm/delta-doc:
None
/usr/share/lib/elm/delta-doc.sjis:
None
/usr/share/lib/elm/delta-doc.euc:
None
cksum(1) Output:
645130938 495616 /usr/bin/elm
1897822551 155648 /usr/bin/readmail
3784381362 57344 /usr/bin/newalias
947979155 151552 /usr/bin/mailfrom
2696684495 159744 /usr/bin/newmail
2290673280 139264 /usr/bin/fastmail
778692878 53248 /usr/bin/elmalias
2662448242 53248 /usr/bin/answer
1935898620 731 /usr/bin/printmail
92312035 1106 /usr/bin/listalias
2900031923 646 /usr/bin/checkalias
713989090 2782 /usr/share/man/man1.Z/answer.1
2181283634 4045 /usr/share/man/man1.Z/elmalias.1
1117666637 2618 /usr/share/man/man1.Z/mailfrom.1
3594592099 1993 /usr/share/man/man1.Z/newmail.1
2399672807 38898 /usr/share/man/man1.Z/elm.1
2608797654 3218 /usr/share/man/man1.Z/fastmail.1
3285005579 3625 /usr/share/man/man1.Z/newalias.1
2525915446 2052 /usr/share/man/man1.Z/readmail.1
3736177690 3287 /usr/share/man/ja_JP.SJIS/man1.Z/answer.1
2429751981 4559 /usr/share/man/ja_JP.SJIS/man1.Z/elmalias.1
1336944441 2933 /usr/share/man/ja_JP.SJIS/man1.Z/mailfrom.1
2588206346 2304 /usr/share/man/ja_JP.SJIS/man1.Z/newmail.1
2974928354 42485 /usr/share/man/ja_JP.SJIS/man1.Z/elm.1
3773839001 3692 /usr/share/man/ja_JP.SJIS/man1.Z/fastmail.1
3024865978 4088 /usr/share/man/ja_JP.SJIS/man1.Z/newalias.1
434861353 2238 /usr/share/man/ja_JP.SJIS/man1.Z/readmail.1
1651323335 3286 /usr/share/man/ja_JP.eucJP/man1.Z/answer.1
566152020 4561 /usr/share/man/ja_JP.eucJP/man1.Z/elmalias.1
1427477186 2930 /usr/share/man/ja_JP.eucJP/man1.Z/mailfrom.1
71018742 2287 /usr/share/man/ja_JP.eucJP/man1.Z/newmail.1
1660496601 42281 /usr/share/man/ja_JP.eucJP/man1.Z/elm.1
3929583524 3682 /usr/share/man/ja_JP.eucJP/man1.Z/fastmail.1
4163045114 4096 /usr/share/man/ja_JP.eucJP/man1.Z/newalias.1
114714742 2243 /usr/share/man/ja_JP.eucJP/man1.Z/readmail.1
1579155863 58120 /usr/lib/nls/msg/C/elm.cat
7222964 63126 /usr/lib/nls/msg/ja_JP.SJIS/elm.cat
3774551901 63130 /usr/lib/nls/msg/ja_JP.eucJP/elm.cat
1215678891 9656 /usr/share/lib/elm/elmrc-info
3099121094 10213 /usr/share/lib/elm/delta-doc
3004534624 12164 /usr/share/lib/elm/delta-doc.sjis
311432325 12164 /usr/share/lib/elm/delta-doc.euc
Patch Conflicts:
PHNE_6691 PHNE_6897 PHNE_7256 PHNE_7343 PHNE_9165 PHNE_9859
PHNE_20504
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_8143 PHNE_11925 PHNE_13695 PHNE_15836
Equivalent Patches:
PHNE_24520:
s700: 10.20
s800: 10.20
PHNE_24522:
s700: 11.11
s800: 11.11
Patch Package Size: 1760 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_25172
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHNE_25172.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHNE_25172. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHNE_25172.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_25172.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHNE_25172:
The length of the subject string (used with the -s command
line option) and filenames (used with the -f and -i command
line options) is limited to 255 characters. If the length
exceeds this limit, the strings will be truncated to 255
characters. The English version of the elm.1 man page has
been modified accordingly.
The binary prlong is not provided with this patch.
Since the tool prmail provides the same functionality,
prlong will not be supported anymore.
If this patch is installed on systems which do not
have the Japanese filesets (MailUtilities.MAIL-JPN-S-MAN,
MailUtilities.MAIL-JPN-E-MAN,OS-Core.UX-JPN-E-MSG,
OS-Core.UX-JPN-S-MSG), error messages pertaining to
the absence of these filesets will be seen in the
logfile of swverify. If users do not need JIS support,
they can ignore these error messages in the logfile. If
users need JIS support, they have to install the
Japanese filesets.
This package cannot be installed along with Mpower mailer.
Mpower mailer acts like a front end to elm to view and send
MIME mails. This is not possible with this version of elm,
as this by itself takes care of MIME mails. If Mpower
mailer is already installed in the system, then you'll have
to remove the headers put in by the Mpower mailer in the
~/.elm/elmheaders file. It is also better to change the
pager and the editor set by the Mpower mailers as any other
equivalent pager/editor by editing the ~/.elm/elmrc file.
This patch contains the catalog files only for Japanese and
English. So it is not suitable for any other language.
This patch has a conflict with PHNE_6691, PHNE_6897
PHNE_7256, PHNE_7343, PHNE_9165, PHNE_9859 and PHNE_20504.
Ensure that these patches are not installed on the system
before installing PHNE_25172. Hence this patch is
recommended only if the user wants MIME or JIS support.
-----End of Document ID: PHNE_25172------------------------------------------
Document ID: PHSS_26887
Date Loaded: 20020728
Title: s700_800 10.X OV OB4.10 patch - SAP packet
Patch Name: PHSS_26887
Patch Description: s700_800 10.X OV OB4.10 patch - SAP packet
Creation Date: 02/07/24
Post Date: 02/07/28
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
OmniBackII A.04.10
Filesets:
OMNIBACK-II.OMNI-SAP-P,A.04.10
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_26887
Symptoms:
PHSS_26887:
Id = HSLco33261 SR: H555007380
SAP integration on UNIX clients automatically passes
"-u" option.
Id = HSLco33795 SR: H555007605
OmniBack II SAP integration is not supported on
Compaq Tru64 operating system.
Defect Description:
PHSS_26887:
Id = HSLco33261
brbackup/brarchive is always started with "-u" option
which displays logon information.
Resolution:
brbackup/brarchive options are passed in a file.
Part of SSPUX410_014.
Id = HSLco33795 SR: H555007605
OmniBack II SAP integration is not supported on
Compaq Tru64 operating system.
Resolution:
OmniBack II SAP integration is supported on
Compaq Tru64 operating system.
SR:
H555007605 H555007380
Patch Files:
/opt/omni/databases/vendor/sap/gpl/i386/linux-60/A.04.10/
packet.Z
/opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/A.04.10/
packet.Z
/opt/omni/databases/vendor/sap/hp/s800/hp-ux-11/A.04.10/
packet.Z
/opt/omni/databases/vendor/sap/ibm/rs6000/aix-42/A.04.10/
packet.Z
/opt/omni/databases/vendor/sap/sun/sparc/solaris-26/A.04.10/
packet.Z
/opt/omni/databases/vendor/sap/dec/alpha/osf1-4/A.04.10/
packet.Z
/opt/omni/databases/vendor/sap/dec/alpha/osf1-4/A.04.10/
require.dat
what(1) Output:
/opt/omni/databases/vendor/sap/gpl/i386/linux-60/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/sap/hp/s800/hp-ux-11/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/sap/ibm/rs6000/aix-42/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/sap/sun/sparc/solaris-26/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/sap/dec/alpha/osf1-4/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/sap/dec/alpha/osf1-4/A.04.10/
require.dat:
None
cksum(1) Output:
3357482138 950920 /opt/omni/databases/vendor/sap/gpl/i386/
linux-60/A.04.10/packet.Z
695903519 1300460 /opt/omni/databases/vendor/sap/hp/s800/
hp-ux-1020/A.04.10/packet.Z
2751300048 1300745 /opt/omni/databases/vendor/sap/hp/s800/
hp-ux-11/A.04.10/packet.Z
3985033471 1159908 /opt/omni/databases/vendor/sap/ibm/
rs6000/aix-42/A.04.10/packet.Z
2770768014 1223231 /opt/omni/databases/vendor/sap/sun/sparc/
solaris-26/A.04.10/packet.Z
2183962725 1881811 /opt/omni/databases/vendor/sap/dec/alpha/
osf1-4/A.04.10/packet.Z
1650591381 18 /opt/omni/databases/vendor/sap/dec/alpha/
osf1-4/A.04.10/require.dat
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies:
PHSS_26349
Supersedes: None
Equivalent Patches:
PHSS_26888:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Patch Package Size: 7700 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_26887
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_26887.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_26887. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHSS_26887.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_26887.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_26887:
NOTE!
This Patch has to be installed on the Installation
Server host.
The OB2 SAP agent must be redistributed to the SAP
client system(s) after the installation of the patch
in order to get the fixes into effect.
For distribution of the SAP agent, refer to
the OmniBackII Installation guide.
Patch includes the following Site Specific Patches:
SSPUX410_014
-----End of Document ID: PHSS_26887------------------------------------------
Document ID: PHSS_26221
Date Loaded: 20020728
Title: s700_800 10.X OV OB4.10 patch - ORACLE8 packet
Patch Name: PHSS_26221
Patch Description: s700_800 10.X OV OB4.10 patch - ORACLE8 packet
Creation Date: 02/07/24
Post Date: 02/07/28
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
OmniBackII A.04.10
Filesets:
OMNIBACK-II.OMNI-OR8-P,A.04.10
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_26221
Symptoms:
PHSS_26221:
Id = HSLco30536 SR: H555006648
OmniBack II Oracle8 integration is not supported on
64-bit versions of AIX operating system.
Id = HSLco30537 SR: H555006649
OmniBack II Oracle8 integration is not supported on
Compaq Tru64 operating system.
Id = HSLco31519 SR: H555006850
Debug files for Oracle8 sessions are always put
in /tmp/directory.
Id = HSLco33404 SR: H555007447
ob2rman.exe script fails when executed on Solaris 8
system.
Id = JAGad70781 SR: 8606201607
Recovery Catalog Database is not backed up in
environments with different Oracle8 version in use.
Id = JAGae06736 SR: 8606237698
Backup of controlfilecopy fails when using
split-mirror Oracle8 backup.
Defect Description:
PHSS_26221:
Id = HSLco30536
OmniBack II Oracle8 integration is not supported on
64-bit versions of AIX operating system.
Resolution:
OmniBack II Oracle8 integration is supported on
64-bit versions of AIX operating system.
Part of SSPUX410_018.
Id = HSLco30537
OmniBack II Oracle8 integration is not supported on
Compaq Tru64 operating system.
Resolution:
OmniBack II Oracle8 integration is supported on
Compaq Tru64 operating system.
Id = HSLco31519
OmniBack ignores OB2OPTS variable and puts debug files
to default location.
Resolution:
Debug files for Oracle8 sessions are put to location
specified in OB2OPTS variable.
Id = HSLco33404
ob2rman.exe script contains a grep command with "-x"
option which does not exist on Solaris 8 systems.
Resolution:
Option "-x" is removed from the script.
Id = JAGad70781
OmniBack exports the path to export utility from the
local system before backing up Recovery Catalog
Database. If different version of Oracle8 is used on
remote system, Recovery Catalog Database backup fails
because of incorrect path to it is exported.
Resolution:
Environment variable ORA_EXP is introduced. Setting its
value to path to export utility on the system in
/etc/opt/omni/oracle8/${ORACLE_SID}/.profile file
resolved described problem.
Id = JAGae06736
ob2rman.exe script incorrectly assumes that certain
lines in Recovery Manager script are put in certain
order. If this is not the case controlfilecopy backup
fails.
Resolution:
ob2rman.exe script logic is adjusted.
SR:
H555006649 H555006850 8606201607 H555007447 8606237698
H555006648
Patch Files:
/opt/omni/databases/vendor/oracle8/gpl/i386/linux-60/
A.04.10/packet.Z
/opt/omni/databases/vendor/oracle8/hp/s800/hp-ux-1020/
A.04.10/packet.Z
/opt/omni/databases/vendor/oracle8/hp/s800/hp-ux-11/A.04.10/
packet.Z
/opt/omni/databases/vendor/oracle8/ibm/rs6000/aix-42/
A.04.10/packet.Z
/opt/omni/databases/vendor/oracle8/sun/sparc/solaris-26/
A.04.10/packet.Z
/opt/omni/databases/vendor/oracle8/dec/alpha/osf1-4/A.04.10/
packet.Z
/opt/omni/databases/vendor/oracle8/dec/alpha/osf1-4/A.04.10/
require.dat
what(1) Output:
/opt/omni/databases/vendor/oracle8/gpl/i386/linux-60/
A.04.10/packet.Z:
None
/opt/omni/databases/vendor/oracle8/hp/s800/hp-ux-1020/
A.04.10/packet.Z:
None
/opt/omni/databases/vendor/oracle8/hp/s800/hp-ux-11/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/oracle8/ibm/rs6000/aix-42/
A.04.10/packet.Z:
None
/opt/omni/databases/vendor/oracle8/sun/sparc/solaris-26/
A.04.10/packet.Z:
None
/opt/omni/databases/vendor/oracle8/dec/alpha/osf1-4/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/oracle8/dec/alpha/osf1-4/A.04.10/
require.dat:
None
cksum(1) Output:
2475281722 377699 /opt/omni/databases/vendor/oracle8/gpl/
i386/linux-60/A.04.10/packet.Z
2424095081 1251149 /opt/omni/databases/vendor/oracle8/hp/
s800/hp-ux-1020/A.04.10/packet.Z
1029160945 1251459 /opt/omni/databases/vendor/oracle8/hp/
s800/hp-ux-11/A.04.10/packet.Z
3679864335 850585 /opt/omni/databases/vendor/oracle8/ibm/
rs6000/aix-42/A.04.10/packet.Z
837478311 1065633 /opt/omni/databases/vendor/oracle8/sun/
sparc/solaris-26/A.04.10/packet.Z
3476332420 510781 /opt/omni/databases/vendor/oracle8/dec/
alpha/osf1-4/A.04.10/packet.Z
3512108347 17 /opt/omni/databases/vendor/oracle8/dec/alpha/
osf1-4/A.04.10/require.dat
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies:
PHSS_26349
Supersedes: None
Equivalent Patches:
PHSS_26222:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Patch Package Size: 5250 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_26221
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_26221.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_26221. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHSS_26221.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_26221.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_26221:
NOTE!
Patch has to be installed on the Installation Server host.
The Oracle 8 packets must be redistributed to the Oracle 8
client system(s) afterwards to get the fixes into effect.
Patch includes the following Site Specific Patches:
SSPUX410_018
-----End of Document ID: PHSS_26221------------------------------------------
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]