|
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 Jul 14 2002 - 14:17:06 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 700 11.X patch digest
Created: Sun Jul 14 3:05:10 PDT 2002
Table of Contents:
Document ID Title
--------------- -----------
PHKL_27220 s700_800 11.00 Enable IDS/9000, data page fault running IDS
PHSS_27417 s700_800 11.X OV ECS3.10 July 2002 Consolidated Patch
PHSS_27276 s700_800 11.04 Virtualvault 4.6 itcwdog startup fix
PHNE_26550 s700_800 11.00 PCI FDDI B.11.00-B.11.00.16 cumulative patch
PHCO_26813 s700_800 11.00 cumulative patch for syslogd(1M)
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHKL_27220
Date Loaded: 20020712
Title: s700_800 11.00 Enable IDS/9000, data page fault running IDS
Patch Name: PHKL_27220
Patch Description: s700_800 11.00 Enable IDS/9000, data page fault running IDS
Creation Date: 02/06/12
Post Date: 02/07/12
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
OS-Core.CORE2-KRN,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
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_27220: PANIC
Category Tags:
defect_repair enhancement general_release critical panic
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_27220
Symptoms:
PHKL_27220:
( SR:8606175959 CR:JAGad45199 )
A data page fault may occur, during normal operating
conditions, on systems running the IDS/9000 product. The
stack trace will look similar to the following:
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xdb8
nokgdb+0x8
_idds_set_recalc+0x4
set_all_idds_recalc+0x9c
idds_set_config+0x8c
do_idds_config+0x1a8
idds_pd_ioctl+0xf8
spubind_cdev_ioctl+0x94
PHKL_21359:
( SR: 8606132622 CR: JAGad01771 )
The Praesidium IDS/9000 product requires this patch in order
to run. This patch has no impact on systems without the
Praesidium IDS/9000 product installed and enabled.
Defect Description:
PHKL_27220:
( SR:8606175959 CR:JAGad45199 )
The data page fault occurs when a pointer with a NULL value
is dereferenced. It was previously assumed the pointer
would always be non-NULL, but in some cases it is valid for
it have a NULL value.
Resolution:
The value of the pointer is now checked before it is
dereferenced. If it is NULL, the appropriate action is now
taken.
PHKL_21359:
( SR: 8606132622 CR: JAGad01771 )
This patch is one of 16 patches (PHKL_21348-PHKL_21363)
required by the Praesidium IDS/9000 product. These patches
enable the collection and tracking of information from
various system calls. Unless all of the enabling patches
(or their successors) and the product are installed, and the
product is enabled, this patch has no impact on the system.
Resolution:
This patch adds a new kernel-internal interface for the
IDS/9000 product.
SR:
8606132622 8606175959
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libhp-ux.a(proc_iface.o)
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libhp-ux.a(proc_iface.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libhp-ux.a(proc_iface.o):
proc_iface.c $Date: 2002/06/12 11:58:23 $Revision: r
11ros/6 PATCH_11.00 (PHKL_27220)
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libhp-ux.a(proc_iface.o):
proc_iface.c $Date: 2002/06/12 11:58:23 $Revision: r
11ros/6 PATCH_11.00 (PHKL_27220)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP:
2829892054 20596 /usr/conf/lib/libhp-ux.a(proc_iface.o)
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
1353439808 75200 /usr/conf/lib/libhp-ux.a(proc_iface.o)
Patch Conflicts: None
Patch Dependencies:
s700: 11.00: PHKL_18543
s800: 11.00: PHKL_18543
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHKL_21359
Equivalent Patches: None
Patch Package Size: 120 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_27220
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_27220.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_27220. 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_27220.text file is
available in the product readme:
swlist -l product -a readme -d 
/tmp/PHKL_27220.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_27220.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
This patch depends on base patch PHKL_18543.
For successful installation please insure that PHKL_18543
is already installed, or that PHKL_18543 is included
in the same depot with this patch and PHKL_18543
is selected for installation.
-----End of Document ID: PHKL_27220------------------------------------------
Document ID: PHSS_27417
Date Loaded: 20020711
Title: s700_800 11.X OV ECS3.10 July 2002 Consolidated Patch
Patch Name: PHSS_27417
Patch Description: s700_800 11.X OV ECS3.10 July 2002 Consolidated Patch
Creation Date: 02/07/09
Post Date: 02/07/11
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
OpenView Event Correlation Services 3.1x
Filesets:
OVECS.OVECS-CMG,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP
OVECS.OVECS-CMG,fr=A.03.10,fa=HP-UX_B.11.11_32/64,v=HP
OVECS.OVECS-DES,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP
OVECS.OVECS-DES,fr=A.03.10,fa=HP-UX_B.11.11_32/64,v=HP
OVECS.OVECS-RUN-MAN,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP
OVECS.OVECS-RUN-MAN,fr=A.03.10,fa=HP-UX_B.11.11_32/64,v=HP
OVECS.OVECS-RUN,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP
OVECS.OVECS-RUN,fr=A.03.10,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
No (superseded patches were critical)
PHSS_27335: ABORT
Category Tags:
defect_repair general_release critical halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_27417
Symptoms:
PHSS_27417:
Cumulative Consolidated Patch
PHSS_27335:
PTSfc01334: core dumps when trace and log mask are
set to -1
PTSfc02167: If two events are sent to the input port
of the unless node and another event is
fed to the reset port, the following
error message is displayed "Error,
bad value type in memory".
PTSfc02210: ECS-Designer hangs when the event file
is loaded when time delay between events
is very large.
PTSfc02284: pmd core dumps in EV_markTraceValue()
of libECSS.sl
PTSfc02525: Error loading datastore/factstore when it
contains an empty list.e.g a datastore
with entry ADD DATA('key',[]) fails
PTSfc02575: ECS Designer core dumps, when circuit with
ECDL code logic to reinitialise global
dictionary, containing values from factstore,
is simulated.
PTSfc02599: ECS feed function flagToSrcCircuit does
not behave as described in ECS designer
reference guide.
PTSfc02660: ECS designer unable to use a X display
number greater than 99.
PTSfc02730: Unless node reverses the order of events
when output.
PTSfc02755: Enhancement request to remove runtime
licensing check in ECS Designer .
PTSfc02815: Uuid values stored in global dictionary
gives garbage values or results in a core
dump when accessed at a later point.
PHSS_26086:
PTSfc02177: ECS configurator is not accessible
from non-english based web browser.
PTSfc01778: ECS Configuration GUI hangs when
used with Java 1.3 plugin. This
happens whenever a parameter is
modified.
PTSfc02452: we cannot use all ecsmgr options correctly
under Japanese locales. LANG=ja_JP.SJIS,
LANG=ja_JP.eucJP for HP-UX LANG=ja,
LANG=japanese, LANG=ja_JP.PCK for Solaris,
HPUX, NT Platforms.
PHSS_25339:
PTSfc02120: ECS3.1 provides a LWIE library which
comprises the core engine using which
applications can be written. It also
provides shared libraries for drilldown,
circuit serialisation, multiple event
creation which can be invoked from ECS
circuits. But this leads to the problem of
shipping of external shared libraries
along with the application written by
customer and hence their installation in
all machines using the application.
PTSfc01871: ecsevgen does not work with -v option,gives
mpbind error
PTSfc02204: ecsmgr manpage to be updated with changes
for OVO
Defect Description:
PHSS_27417:
Cumulative Consolidated Patch
Resolution:
Cumulative Consolidated Patch
PHSS_27335:
PTSfc01334: core dumps when trace and log mask are
set to -1
Resolution:
This error was due to cut and
paste problem. Here in place
of getting the FactStore name,
DataStore name was searched.
PTSfc02167: If two events are sent to the input port
of the unless node and another event is
fed to the reset port, the following
error message is displayed "Error,
bad value type in memory".
Resolution:
This was due to improper deletion of
events in the unless node, which resulted
in memory corruption. This was resolved
by checking proper conditions.
PTSfc02210: ECS-Designer hangs when the event file
is loaded when time delay between events
is very large.
Resolution:
When the event file is loaded, the cleanup
function is called every minute in the
simulator, which causes the Designer to
hang if the delay is too large.
A flag was introduced which does no
cleanup while loading the event file.
PTSfc02284: pmd core dumps in EV_markTraceValue()
of libECSS.sl
Resolution:
This problem occurs when elements,which
are taken as reference and stored in
global dictionary,get deleted.The
solution is to make a deep copy of values
before storing it in global dictionary.
PTSfc02525: Error loading datastore/factstore when
it contains an empty list.e.g a datastore
with entry ADD DATA('key',[]) fails
Resolution:
The parser used while loading
datastore/factstore had no rules to
to understand empty list.This has
now been added.
PTSfc02575: ECS Designer core dumps, when circuit with
ECDL code logic to reinitialise global
dictionary, containing values from factstore,
is simulated.
Resolution:
Refer to Resolution of PTSfc02815.
PTSfc02599: ECS feed function flagToSrcCircuit does
not behave as described in ECS Designer
Reference Guide.
Resolution:
This is a documentation error.
Second argument of 'feed' does not have a
default value as mentioned in the Designer
Reference Guide. It should be either true or
false.
PTSfc02660: ECS designer unable to use a X display
number greater than 99.
Resolution:
The ECS designer binary was changed to
be dynamically linked against the X
libraries installed on the host machine.
PTSfc02730: Unless node reverses the order of events
when output.
Resolution:
The problem occurs only when we have more
then two events arriving in unless node
at the same time. The reason for this that
ECS uses UUID to sort the events in this
case and in place of sorting in the
increasing order events were sorted
in decreasing order.
PTSfc02755: Enhancement request to remove runtime
licensing check in ECS Designer .
Resolution:
The relevant code sections which check
for license has been removed from the
designer code.Henceforth runtime
license strings are not required for
using ECS Designer.
PTSfc02815: Uuid values stored in global dictionary
gives garbage values or results in a core
dump when accessed at a later point.
Resolution:
ECS internally uses the concept of engine
and interpreter memory collections.When
engine values are placed in interperter
collections for eg. dictionary,the engine
values need to be appropriately wrapped by
guard structures so that they can be deep
copied into the interpreter memory collection.
mechanism helps safeguard against corrupt memory
pointer access even if the engine deletes its
collection values.This mechanism were not
in place in certain sections of the ECS code,
which has now been rectified.
PHSS_26086:
PTSfc02177: ECS configurator is not accessible
from non-english based web browser.
Resolution:
This problem is specific to NT, since
NNM6.2 is now installed in the path
which has space in them. So while accessing
the file, perl does not find the files
and fails.Hence the file name was put b/w
quotes.So perl interprets it properly.
PTSfc01778: ECS Configuration GUI hangs when
used with Java 1.3 plugin. This
happens whenever a parameter is
modified.
Resolution:
This was occurring because there was no
permission to access certain classes. Java's
security model has changed significantly
since Java 1.1. access problem. The code
was changed to access a standard class
(java.io), instead of the non-standard,
internal (sun.io) class being used earlier.
PTSfc02452: we cannot use all ecsmgr options correctly
under Japanese locales. LANG=ja_JP.SJIS,
LANG=ja_JP.eucJP for HP-UX LANG=ja,
LANG=japanese, LANG=ja_JP.PCK for Solaris,
HPUX, NT Platforms.
Resolution:
This problem was due to improper string
comparsion and faulty argument processing.
PHSS_25339:
PTSfc02120:
ECS3.1 provides a LWIE library which
comprises the core engine using which
applications can be written. It also
provides shared libraries for drilldown,
circuit serialisation, multiple event
creation which can be invoked from ECS
circuits. But this leads to the problem of
shipping of external shared libraries
along with the application written by
customer and hence their installation in
all machines using the application.
Resolution:
To solve this it was decided to make these
functionalities part of the LWIE library and
hence their conversion to built-in-functions
in ECDL.This will enable the drilldown
(append, flush), circuit serialization(feed),
multiple event(create_events) functions to be
part of ECDL syntax and will get resolved
internally in the LWIE library. The customer
now only needs to recompile his circuits
which use drilldown, circuit serialization,
multiple event creation using this patch's
ECS designer and use it along with this
patch's LWIE library. Once this is done the
customer need not use or install the
external C shared libraries for drilldown,
circuit serialization, multiple event
creation along with their application using
LWIE library.
PTSfc01871:
ecsevgen does not work with -v option, gives
mpbind error
Resolution:
ecsevgen is modified to parse the -v option
appropriately.
PTSfc02204:
ecsmgr manpage to be updated with changes
for OVO
Resolution:
Following text has been added to the ecsmgr
manpage
ECS engine instances for OVO:
- OVO Server (opcecm): 11
- OVO Agent (opceca): 12
Only the following options of ecsmgr(1m) are
supported with OVO:
-h, -instance, -data_dump, -data_update,
-fact_dump, -fact_update -info, -stats,
-snapshot.
All other options are NOT supported for OVO.
Enhancement:
No
SR:
F333002755 F333002575 F333002210 F333002599 F333001334
F333002730 F333002525 F333002660 F333002167 F333002284
F333002177 F333002452 F333001778 F333001871
Patch Files:
OVECS.OVECS-CMG,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP:
OVECS.OVECS-CMG,fr=A.03.10,fa=HP-UX_B.11.11_32/64,v=HP:
/opt/OV/www/lib/ecs/ecsmgr.ovpl
/opt/OV/www/htdocs/classes/cmg/cmg.jar
OVECS.OVECS-DES,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP:
OVECS.OVECS-DES,fr=A.03.10,fa=HP-UX_B.11.11_32/64,v=HP:
/opt/OV/bin/ecsdes2
/opt/OV/bin/ecdlheap
/etc/opt/OV/share/conf/ecs/modules/ecs_defaults.ecs
OVECS.OVECS-RUN-MAN,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP:
OVECS.OVECS-RUN-MAN,fr=A.03.10,fa=HP-UX_B.11.11_32/64,v=HP:
/opt/OV/man/man1m.Z/ecsmgr.1m
OVECS.OVECS-RUN,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP:
OVECS.OVECS-RUN,fr=A.03.10,fa=HP-UX_B.11.11_32/64,v=HP:
/opt/OV/lib/libCE.3
/opt/OV/contrib/ecs/ecsevgen
/opt/OV/bin/ecsmgr
what(1) Output:
OVECS.OVECS-CMG,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/www/lib/ecs/ecsmgr.ovpl:
None
/opt/OV/www/htdocs/classes/cmg/cmg.jar:
None
OVECS.OVECS-DES,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/bin/ecsdes2:
ecsdes2.cc $Revision: /main/NILGIRIS/7 $ $Date: 2002
/06/24 05:40 UTC $
Reference.hh $Revision$ $Date$
Librarian.hh $Revision$ $Date$
PATCH PHSS_25339, (PTSfc02120) Sep 2001
Librarian.hh $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiConnection.cc $Revision$ $Date$
cdiDisplay.cc 1.42 1997/11/28 06:21:59
Reference.hh $Revision$ $Date$
cdiHelp.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiJunction.cc $Revision$ $Date$
cdiNode.cc 1.46 1997/09/03 08:04:00
cdiText.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiViewer.cc 1.223 1998/01/08 03:00:41
Reference.hh $Revision$ $Date$
Librarian.hh $Revision$ $Date$
cdiAttributeDefnPanel.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiBreakPointTool.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiCompiler.cc $Revision: /main/3 $ $Date: 1998/08/2
1 10:25 UTC $
Reference.hh $Revision$ $Date$
Librarian.hh $Revision$ $Date$
cdiConfigureDefnPanel.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiConnectionTool.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiControlPanel.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiDebNodeInfo.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiDebuggerControls.cc $Revision$ $Date$
Librarian.hh $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiDescriptionDefnPanel.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiJunctionTool.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiLibraryInterface.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
Librarian.hh $Revision$ $Date$
cdiLibraryTool.cc $Revision$ $Date$
Librarian.hh $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiNodeInstanceEditor.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiNodeTool.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiNotice.cc $Revision$ $Date$
cdiPanel.cc $Revision$ $Date$
cdiParameterDefnPanel.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiPort.cc $Revision$ $Date$
cdiProgressBar.cc $Revision$ $Date$
cdiSelectionTool.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiTextEditor.cc $Revision: /main/NILGIRIS/2 $ $Date
: 2000/03/06 08:29 UTC $
Librarian.hh $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiTextTool.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiUnconfiguredTool.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiCompilerError.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiCompilerOutput.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiDebCircuitInfo.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiDebNodeAttrPanel.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiDebNodeStatPanel.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiDefnPanel.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiLogViewer.cc $Revision$ $Date$
Librarian.hh $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiNodePanels.cc $Revision$ $Date$
cdiSubProcess.cc 1.5 1997/11/13 05:57:05
cdiCommentPanel.cc $Revision$ $Date$
cdiCompErrItem.cc $Revision$ $Date$
cdiDebNodeAttrItem.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
cdiParameterPanel.cc $Revision$ $Date$
cdiPortPanel.cc $Revision$ $Date$
cdiPortParameterPanel.cc $Revision$ $Date$
cdiParameterItem.cc $Revision$ $Date$
cdiPortItem.cc $Revision$ $Date$
messages.c $Revision: /main/NILGIRIS/1 $ $Date: 1999
/12/02 03:28 UTC $
debConnection.cc $Revision: 1.10 $ $Date: 1997/06/17
00:59:41 $
Reference.hh $Revision$ $Date$
debNode.cc $Revision: 1.22 $ $Date: 1997/07/01 23:33
:55 $
Reference.hh $Revision$ $Date$
debSession.cc $Revision: 1.75 $ $Date: 1998/03/17 06
:29:49 $
Reference.hh $Revision$ $Date$
Librarian.hh $Revision$ $Date$
debCircuit.cc $Revision: 1.10 $ $Date: 1997/06/17 00
:59:39 $
Reference.hh $Revision$ $Date$
debCompoundNode.cc $Revision: 1.12 $ $Date: 1997/06/
17 00:59:40 $
debConnectable.cc $Revision: 1.6 $ $Date: 1997/07/01
23:33:54 $
debPath.cc $Revision: 1.8 $ $Date: 1997/07/01 23:33:
55 $
debPort.cc $Revision: 1.9 $ $Date: 1997/06/17 00:59:
43 $
Reference.hh $Revision$ $Date$
debFakeNode.cc $Revision: 1.8 $ $Date: 1997/06/17 00
:59:42 $
debRealNode.cc $Revision: 1.12 $ $Date: 1997/06/17 0
0:59:44 $
Reference.hh $Revision$ $Date$
EcdlLoader.cc $Revision: 1.63 $ $Date: 1998/04/01 07
:02:00 $
Reference.hh $Revision$ $Date$
Interface.cc $Revision: 1.81 $ $Date: 1998/01/05 04:
53:52 $
Reference.hh $Revision$ $Date$
Librarian.hh $Revision$ $Date$
ParseTree.cc $Revision: /main/NILGIRIS/1 $ $Date: 19
99/08/13 07:09 UTC $
CompoundDefn.cc $Revision: 1.106 $ $Date: 1998/04/01
07:00:44 $
Reference.hh $Revision$ $Date$
Librarian.hh $Revision$ $Date$
Connectable.cc $Revision: 1.12 $ $Date: 1997/09/03 0
8:05:26 $
Connection.cc $Revision: 1.13 $ $Date: 1997/06/17 01
:04:23 $
CosmeticNode.cc $Revision: 1.12 $ $Date: 1997/09/03
08:05:27 $
JunctionNode.cc $Revision: 1.19 $ $Date: 1998/01/08
02:54:39 $
Module.cc $Revision: 1.42 $ $Date: 1998/04/07 06:50:
04 $
Reference.hh $Revision$ $Date$
Node.cc $Revision: 1.54 $ $Date: 1997/11/04 00:52:27
$
Reference.hh $Revision$ $Date$
Librarian.hh $Revision$ $Date$
NodeDefn.cc $Revision: 1.43 $ $Date: 1997/11/04 00:5
2:29 $
NodeFactory.cc $Revision: 1.52 $ $Date: 1998/01/08 0
2:54:41 $
Parameter.cc $Revision: 1.12 $ $Date: 1997/06/17 01:
04:29 $
Port.cc $Revision: 1.22 $ $Date: 1997/09/16 01:13:20
$
PortNode.cc $Revision: 1.19 $ $Date: 1998/01/08 02:5
4:42 $
PortType.cc $Revision: 1.11 $ $Date: 1998/01/14 06:3
7:00 $
cmoBuffer.cc $Revision: 1.10 $ $Date: 1997/06/17 01:
04:33 $
Reference.hh $Revision$ $Date$
cmoEdit.cc $Revision: 1.7 $ $Date: 1997/06/17 01:04:
34 $
Reference.hh $Revision$ $Date$
cmoEditEffect.cc $Revision: 1.7 $ $Date: 1998/01/05
01:02:05 $
cmoExportedAttribute.cc $Revision: 1.11 $ $Date: 199
7/09/03 08:05:32 $
cmoTextItem.cc $Revision: 1.5 $ $Date: 1997/06/17 01
:04:38 $
cmoAttribute.cc $Revision: 1.8 $ $Date: 1997/06/17 0
1:04:32 $
cmoCompPort.cc $Revision: 1.4 $ $Date: 1997/06/17 01
:04:33 $
cmoEditItem.cc $Revision: 1.5 $ $Date: 1997/06/17 01
:04:35 $
cmoEditModuleSwap.cc $Revision: 1.5 $ $Date: 1997/06
/17 01:04:36 $
cmoLocalAttribute.cc $Revision: 1.5 $ $Date: 1997/06
/17 01:04:37 $
clbCompiler.cc $Revision$ $Date$
Librarian.hh $Revision$ $Date$
Reference.hh $Revision$ $Date$
clbDisplay.cc $Revision$ $Date$
Librarian.hh $Revision$ $Date$
Reference.hh $Revision$ $Date$
clbLibrarian.cc $Revision$ $Date$
Librarian.hh $Revision$ $Date$
Reference.hh $Revision$ $Date$
clbReference.cc $Revision: /main/2 $ $Date: 1998/08/
21 11:17 UTC $
Librarian.hh $Revision$ $Date$
Reference.hh $Revision$ $Date$
clbTempReference.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
clbStorageMethod.cc $Revision$ $Date$
clbStoreEncrypted.cc $Revision$ $Date$
clbStoreOldCrypt.cc $Revision$ $Date$
Reference.hh $Revision$ $Date$
Librarian.hh $Revision$ $Date$
clbTempFile.cc $Revision$ $Date$
clbType.cc $Revision$ $Date$
Librarian.hh $Revision$ $Date$
Reference.hh $Revision$ $Date$
clbInterface.cc $Revision$ $Date$
tree.c $Revision: 1.7 $ $Date: 1998/04/01 23:18:08 $
ecdl_yacc.y $Revision: 1.11 $ $Date: 1996/05/22 01:4
3:17 $
ecdl_lex.l $Revision: /main/NILGIRIS/1 $ $Date: 1999
/08/13 07:23 UTC $
name.c $Revision: 1.3 $ $Date: 1996/05/22 01:43:04 $
cdReservedWords.cc $Revision: 1.5 $ $Date: 1997/07/0
1 23:33:42 $
cdSignal.cc $Revision: 1.10 $ $Date: 1997/11/19 03:3
7:36 $
cdUtils.cc $Revision: 1.5 $ $Date: 1996/05/16 23:57:
10 $
Container.cc $Revision$ $Date$
EditableList.cc $Revision$ $Date$
StringList.cc $Revision$ $Date$
$Id$
AnnotationList.cc $Revision: 1.11 $ $Date: 1997/10/1
3 05:29:04 $
AnnotationMgr.cc $Revision: 1.12 $ $Date: 1997/09/03
08:04:35 $
AnnotationViewer.cc $Revision: 1.14 $ $Date: 1997/12
/04 00:36:55 $
DebugHandle.cc $Revision: 1.76 $ $Date: 1997/12/15 0
6:18:59 $
DisplayEvent.cc $Revision: 1.14 $ $Date: 1997/06/17
01:03:04 $
EventList.cc $Revision: 1.16 $ $Date: 1997/10/22 05:
02:49 $
EventStore.cc $Revision: 1.11 $ $Date: 1998/02/05 03
:39:09 $
InputLogList.cc $Revision: 1.38 $ $Date: 1998/02/06
07:11:55 $
InputLogViewer.cc $Revision: 1.35 $ $Date: 1997/12/0
4 00:36:56 $
OutputLogViewer.cc $Revision: 1.29 $ $Date: 1997/12/
04 00:36:57 $
Librarian.hh $Revision$ $Date$
Reference.hh $Revision$ $Date$
Schema.cc $Revision: 1.8 $ $Date: 1997/06/17 01:03:1
1 $
SimpleViewer.cc $Revision: 1.28 $ $Date: 1998/04/29
06:03:03 $
AnnotationEvent.cc $Revision: 1.19 $ $Date: 1997/06/
17 01:02:59 $
AnnotationRenderer.cc $Revision: 1.9 $ $Date: 1997/0
9/03 08:04:36 $
CompoundEvent.cc $Revision: 1.21 $ $Date: 1998/03/18
05:58:33 $
Identifier.cc $Revision: 1.11 $ $Date: 1997/06/17 01
:03:06 $
InputLogRenderer.cc $Revision: 1.18 $ $Date: 1997/09
/16 00:53:42 $
OutputLogList.cc $Revision: 1.36 $ $Date: 1998/02/23
22:33:42 $
OutputLogRenderer.cc $Revision: 1.14 $ $Date: 1997/0
9/03 08:04:43 $
PrimitiveEvent.cc $Revision: 1.23 $ $Date: 1998/04/0
1 23:22:07 $
SimpleList.cc $Revision: 1.9 $ $Date: 1997/06/17 01:
03:12 $
SimpleRenderer.cc $Revision: 1.14 $ $Date: 1997/10/2
2 05:02:50 $
TempEvent.cc $Revision: 1.22 $ $Date: 1997/06/17 01:
03:14 $
Event.cc $Revision: 1.22 $ $Date: 1997/10/22 05:01:2
4 $
Alert.cc $Revision: 1.1.1.8 $ $Date: 1996/09/20 06:5
0:43 $
ApplicationManager.cc $Revision: 1.1.1.13 $ $Date: 1
998/01/16 01:56:58 $
TUSC Component: TW 1.5.8 Feb 19 1998 12:14:53 { GEN=
/common/components/GEN/1.7 }
BasicObject.cc $Revision: 1.1.1.3 $ $Date: 1996/09/2
0 06:54:15 $
ColumnSet.cc $Revision: 1.1.1.4 $ $Date: 1996/09/20
06:51:48 $
CommandManager.cc $Revision: 1.1.1.8 $ $Date: 1996/0
9/20 06:54:17 $
Dialog.cc $Revision: 1.1.1.7 $ $Date: 1996/09/20 06:
52:31 $
DialogItem.cc $Revision: 1.1.1.8 $ $Date: 1996/09/20
06:52:32 $
DynListItemRenderer.cc $Revision: 1.1.1.5 $ $Date: 1
996/09/20 06:51:51 $
DynamicList.cc $Revision: 1.1.1.4 $ $Date: 1996/09/2
0 06:51:52 $
DynamicListDefinition.cc $Revision: 1.1.1.4 $ $Date:
1996/09/20 06:51:54 $
DynamicListItem.cc $Revision: 1.1.1.4 $ $Date: 1996/
09/20 06:51:55 $
DynamicListViewer.cc $Revision: 1.1.1.8 $ $Date: 199
7/11/13 00:48:03 $
Error.cc $Revision: 1.1.1.8 $ $Date: 1997/11/13 00:4
7:51 $
ErrorAlert.cc $Revision: 1.1.1.6 $ $Date: 1996/09/20
06:50:44 $
InformationAlert.cc $Revision: 1.1.1.6 $ $Date: 1996
/09/20 06:50:46 $
InternationalString.cc $Revision: 1.1.1.5 $ $Date: 1
996/09/20 06:51:18 $
Mark.cc $Revision: 1.1.1.4 $ $Date: 1996/09/20 06:51
:23 $
Notifier.cc $Revision: 1.1.1.5 $ $Date: 1996/09/20 0
6:52:38 $
ObjectFactory.cc $Revision: 1.1.1.4 $ $Date: 1996/09
/20 06:51:25 $
Observer.cc $Revision: 1.1.1.3 $ $Date: 1996/09/20 0
6:52:39 $
Panel.cc $Revision: 1.1.1.8 $ $Date: 1998/01/16 01:5
7:21 $
PersistentObject.cc $Revision: 1.1.1.6 $ $Date: 1996
/09/20 06:54:23 $
QuestionAlert.cc $Revision: 1.1.1.6 $ $Date: 1996/09
/20 06:50:48 $
SchBSelectTool.cc $Revision: 1.1.1.8 $ $Date: 1997/1
1/13 00:48:26 $
SchConnTool.cc $Revision: 1.1.1.6 $ $Date: 1997/11/1
3 00:48:27 $
SchConnection.cc $Revision: 1.1.1.6 $ $Date: 1997/11
/13 00:48:28 $
SchElement.cc $Revision: 1.1.1.5 $ $Date: 1996/09/20
06:53:19 $
SchNode.cc $Revision: 1.1.1.6 $ $Date: 1996/09/20 06
:53:20 $
SchNodeTool.cc $Revision: 1.1.1.5 $ $Date: 1996/09/2
0 06:53:21 $
SchPalette.cc $Revision: 1.1.1.10 $ $Date: 1998/01/1
6 01:57:31 $
SchText.cc $Revision: 1.1.1.5 $ $Date: 1997/11/13 00
:48:31 $
SchTextTool.cc $Revision: 1.1.1.4 $ $Date: 1996/09/2
0 06:53:26 $
SchTool.cc $Revision: 1.1.1.6 $ $Date: 1996/09/20 06
:53:27 $
SchToolFactory.cc $Revision: 1.1.1.4 $ $Date: 1996/0
9/20 06:53:28 $
SchVSelectTool.cc $Revision: 1.1.1.6 $ $Date: 1996/0
9/20 06:53:29 $
SchViewer.cc $Revision: 1.1.1.8 $ $Date: 1998/01/16
01:57:34 $
Schematic.cc $Revision: 1.1.1.3 $ $Date: 1996/09/20
06:53:33 $
Stack.cc $Revision: 1.1.1.7 $ $Date: 1997/11/13 00:4
7:54 $
StringTranslator.cc $Revision: 1.1.1.6 $ $Date: 1996
/09/20 06:51:28 $
Viewable.cc $Revision: 1.1.1.4 $ $Date: 1996/09/20 0
6:54:25 $
Viewer.cc $Revision: 1.1.1.9 $ $Date: 1996/09/20 06:
54:28 $
Window.cc $Revision: 1.1.1.5 $ $Date: 1996/09/20 06:
52:47 $
Stub ActivityManager.cc $Revision: 1.1.1.4 $ $Date:
1996/09/20 06:50:39 $
Stub ClipboardManager.cc $Revision: 1.1.1.4 $ $Date:
1996/09/20 06:51:15 $
Stub ControlPanel.cc $Revision: 1.1.1.4 $ $Date: 199
6/09/20 06:51:43 $
DefinitionDialog.cc $Revision: 1.1.1.10 $ $Date: 199
7/11/13 00:48:01 $
DiskStore.cc $Revision: 1.1.1.6 $ $Date: 1996/09/20
06:54:19 $
Stub Folder.cc $Revision: 1.1.1.6 $ $Date: 1996/09/2
0 06:52:16 $
Stub FolderViewer.cc $Revision: 1.1.1.4 $ $Date: 199
6/09/20 06:52:19 $
Item.cc $Revision: 1.1.1.4 $ $Date: 1996/09/20 06:51
:19 $
StubLocalWorkstationManager.cc $Revision: 1.1.1.4 $
$Date: 1996/09/20 06:51:20 $
Stub LoginDialog.cc $Revision: 1.1.1.4 $ $Date: 1996
/09/20 06:51:21 $
MessageArea.cc $Revision: 1.1.1.7 $ $Date: 1996/09/2
0 06:52:36 $
PSIStream.cc $Revision: 1.1.1.5 $ $Date: 1998/01/16
01:57:47 $
PSOStream.cc $Revision: 1.1.1.4 $ $Date: 1998/01/16
01:57:48 $
STUB Permissions.cc $Revision: 1.1.1.3 $ $Date: 1996
/09/20 06:51:25 $
Stub Printer.cc $Revision: 1.1.1.3 $ $Date: 1996/09/
20 06:53:09 $
Stub Recording.cc $Revision: 1.1.1.4 $ $Date: 1996/0
9/20 06:51:06 $
SchTextEdit.cc $Revision: 1.1.1.5 $ $Date: 1997/11/1
3 00:48:31 $
Stub SecurityServer.cc $Revision: 1.1.1.3 $ $Date: 1
996/09/20 06:51:26 $
STUB User.cc $Revision: 1.1.1.3 $ $Date: 1996/09/20
06:54:12 $
ViewableDefinition.cc $Revision: 1.1.1.4 $ $Date: 19
96/09/20 06:54:26 $
Stub WclInterp.cc $Revision: 1.1.1.3 $ $Date: 1996/0
9/20 06:54:46 $
AMSAlarm.cc $Revision: 1.1.1.4 $ $Date: 1996/09/20 0
6:50:28 $
AVList.cc $Revision: 1.1.1.5 $ $Date: 1996/09/20 06:
54:02 $
AlarmList.cc $Revision: 1.1.1.4 $ $Date: 1996/09/20
06:50:30 $
AttributeValue.cc $Revision: 1.1.1.4 $ $Date: 1996/0
9/20 06:54:03 $
BasicObjectList.cc $Revision: 1.1.1.3 $ $Date: 1996/
09/20 06:54:16 $
EmbeddedList.cc $Revision: 1.1.1.6 $ $Date: 1996/09/
20 06:52:34 $
PersistentStore.cc $Revision: 1.1.1.4 $ $Date: 1996/
09/20 06:54:24 $
Stub RecordEvent.cc $Revision: 1.1.1.4 $ $Date: 1996
/09/20 06:51:05 $
AlarmListViewer.cc $Revision: 1.1.1.6 $ $Date: 1996/
09/20 06:50:31 $
CommandLine.cc $Revision: 1.1.1.7 $ $Date: 1996/09/2
0 06:52:29 $
GEN.cc 1.3 1996/05/15 00:42:56
TUSC Component: GEN 1.7 Feb 18 1998 14:48:05 { NONE
}
sim_control.c $Revision: 1.52 $ $Date: 1998/03/18 06
:52:08 $
sim_debug.c 1.71 1997/01/15 04:05:06
ECS.c $Revision: 1.9 $ $Date: 1998/04/22 23:30:06 $
ECS 3.1 (A.03.10)
ECS REV: A.03.10
ecsLocale.c $Revision: /main/2 $ $Date: 1998/08/21 1
0:59 UTC $
endecode.c $Revision: /main/NILGIRIS/3 $ $Date: 2000
/01/28 15:09 UTC $
anno_event.c $Revision: 1.18 $ $Date: 1997/08/29 00:
49:58 $
control.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/
07/12 09:30 UTC $
debug.c $Revision: 1.26 $ $Date: 1997/07/08 07:17:52
$
fatal.c $Revision: 1.13 $ $Date: 1998/05/07 02:26:33
$
log.c $Revision: 1.7 $ $Date: 1997/07/04 07:34:11 $
mesgbuf.c $Revision: 1.18 $ $Date: 1998/05/07 00:28:
35 $
trace.c $Revision: 1.12 $ $Date: 1998/03/12 04:48:38
$
engine_control.c $Revision: /main/NILGIRIS/5 $ $Date
: 2000/02/22 14:08 UTC $
annotate.c $Revision: /main/NILGIRIS/1 $ $Date: 1999
/09/29 12:35 UTC $
bus.c $Revision$ $Date$
clock.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/07
/02 05:55 UTC $
DFIX12000:clock.c 19mar99
combine.c $Revision: /main/NILGIRIS/2 $ $Date: 2001/
01/06 09:20 UTC $
count.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/09
/29 12:35 UTC $
create.c $Revision: /main/NILGIRIS/2 $ $Date: 2000/0
2/04 15:32 UTC $
extract.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/
09/29 12:36 UTC $
filter.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/0
9/29 12:36 UTC $
input.c $Revision: /main/NILGIRIS/5 $ $Date: 2001/02
/20 12:04 UTC $
loader.c $Revision$ $Date$
memory.c $Revision: /main/NILGIRIS/1 $ $Date: 2002/0
4/24 10:02 UTC $
modify.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/0
9/29 12:30 UTC $
output.c $Revision$ $Date$
rate.c $Revision: /main/NILGIRIS/3 $ $Date: 1999/10/
25 11:06 UTC $
DFIX12000:rate.c 19mar99
PATCH PHSS_18006, Consolidated patch Mar 1999
rearrange.c $Revision$ $Date$
table.c $Revision: /main/NILGIRIS/2 $ $Date: 1999/09
/29 12:31 UTC $
DFIX12000:table.c 19mar99
unless.c $Revision: /main/NILGIRIS/4 $ $Date: 2002/0
6/27 14:09 UTC $
DFIX12000:unless.c 19mar99
delay.c $Revision$ $Date$
transit.c $Revision$ $Date$
assembler.c $Revision: /main/NILGIRIS/1 $ $Date: 200
0/01/28 14:19 UTC $
dicts.c $Revision: /main/NILGIRIS/2 $ $Date: 2002/06
/20 15:04 UTC $
interpreter.c $Revision: /main/NILGIRIS/9 $ $Date: 2
002/06/20 15:02 UTC $
library.c $Revision: /main/NILGIRIS/2 $ $Date: 2002/
06/20 15:06 UTC $
memory.c $Revision$ $Date$
bif_oid.c $Revision: 1.1 $ $Date: 1997/09/25 05:08:2
4 $
dicts.c $Revision: 1.18 $ $Date: 1998/03/27 09:02:35
$
endecrypt.c $Revision: 1.1 $ $Date: 1997/10/15 09:57
:37 $
opc_pattern.c $Revision: /main/2 $ $Date: 1998/08/21
10:33 UTC $
circuit.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/
07/02 05:52 UTC $
engine.c $Revision: 1.15 $ $Date: 1997/08/14 00:08:4
2 $
node.c $Revision: 1.44 $ $Date: 1998/05/01 04:33:53
$
nodeclass.c $Revision: 1.16 $ $Date: 1997/09/26 07:3
7:47 $
patching.c $Revision: 1.8 $ $Date: 1997/12/15 06:19:
31 $
port.c $Revision: 1.11 $ $Date: 1996/05/15 05:45:40
$
stream.c $Revision: /main/NILGIRIS/5 $ $Date: 2000/0
1/18 07:32 UTC $
streamio.c $Revision: /main/NILGIRIS/4 $ $Date: 2000
/02/15 15:22 UTC $
notify.c $Revision: 1.2 $ $Date: 1997/08/07 08:13:22
$
trace.c $Revision: 1.4 $ $Date: 1998/06/10 09:01:45
$
value.c $Revision: /main/NILGIRIS/9 $ $Date: 2002/07
/09 09:54 UTC $
PATCH PHSS_27417, Consolidated Patch July 2002
PATCH PHSS_27335, June 2002
vstring.c $Revision: /main/2 $ $Date: 1998/08/21 10:
54 UTC $
ctxtmap.c $Revision: 1.3 $ $Date: 1998/01/29 08:58:2
4 $
datastore.c $Revision: 1.8 $ $Date: 1998/07/25 18:31
:39 $
dfstore.c $Revision: /main/2 $ $Date: 1998/08/07 15:
39 UTC $
factstore.c $Revision: 1.8 $ $Date: 1998/07/25 18:36
:10 $
query.c 1.16 1996/11/20 23:28:02
container.c $Revision: 1.17 $ $Date: 1998/02/18 00:4
9:18 $
log.c 1.27 1996/06/03 04:56:34
engmgr.c $Revision: /main/NILGIRIS/7 $ $Date: 2000/0
3/01 09:41 UTC $
sequence.c $Revision: 1.17 $ $Date: 1998/01/28 03:39
:17 $
dictionary.c $Revision: 1.23 $ $Date: 1998/04/01 06:
13:08 $
engine_dict.c $Revision: 1.7 $ $Date: 1998/03/23 07:
30:52 $
char_sets.c $Revision: /main/2 $ $Date: 1998/08/21 1
0:39 UTC $
ascii.c $Revision: /main/NILGIRIS/1 $ $Date: 2000/01
/28 14:18 UTC $
ascii_alloc.c $Revision$ $Date$
parse.c $Revision: /main/2 $ $Date: 1998/08/21 10:29
UTC $
token_set.c $Revision$ $Date$
berova.c $Revision: /main/NILGIRIS/4 $ $Date: 2001/1
0/19 04:28 UTC $
md.c $Revision$ $Date$
DFIX15000: dtd.c 01Oct1999
DFIX15001: dict.c 21Dec1999
DFIX15014: ber.c 13Dec2000
DFIX15000: ber.c 01Oct1999, 13sep2000
DFIX15000: enum.c 01Oct1999
OSE Release HPPA_HPUX11 40312
/opt/OV/bin/ecdlheap:
ECS 3.1 (RELEASE) PATCH PHSS_25339,PHSS_25338,PSOV_0
3018,ECS_00007 (PTSfc02120) Sep 2001
/etc/opt/OV/share/conf/ecs/modules/ecs_defaults.ecs:
None
OVECS.OVECS-RUN-MAN,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/man/man1m.Z/ecsmgr.1m:
None
OVECS.OVECS-RUN,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/lib/libCE.3:
log.c $Revision: 1.7 $ $Date: 1997/07/04 07:34:11 $
trace.c $Revision: 1.12 $ $Date: 1998/03/12 04:48:38
$
PATCH PHSS_25339, (PTSfc02120) Sep 2001
engine_control.c $Revision: /main/NILGIRIS/5 $ $Date
: 2000/02/22 14:08 UTC $
events.c $Revision: /main/NILGIRIS/10 $ $Date: 2002/
06/24 05:42 UTC $
fatal.c $Revision: 1.13 $ $Date: 1998/05/07 02:26:33
$
mesgbuf.c $Revision: 1.18 $ $Date: 1998/05/07 00:28:
35 $
bus.c $Revision$ $Date$
clock.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/07
/02 05:55 UTC $
DFIX12000:clock.c 19mar99
combine.c $Revision: /main/NILGIRIS/2 $ $Date: 2001/
01/06 09:20 UTC $
count.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/09
/29 12:35 UTC $
create.c $Revision: /main/NILGIRIS/2 $ $Date: 2000/0
2/04 15:32 UTC $
delay.c $Revision$ $Date$
extract.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/
09/29 12:36 UTC $
filter.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/0
9/29 12:36 UTC $
input.c $Revision: /main/NILGIRIS/5 $ $Date: 2001/02
/20 12:04 UTC $
loader.c $Revision$ $Date$
modify.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/0
9/29 12:30 UTC $
output.c $Revision$ $Date$
rate.c $Revision: /main/NILGIRIS/3 $ $Date: 1999/10/
25 11:06 UTC $
DFIX12000:rate.c 19mar99
PATCH PHSS_18006, Consolidated patch Mar 1999
rearrange.c $Revision$ $Date$
table.c $Revision: /main/NILGIRIS/2 $ $Date: 1999/09
/29 12:31 UTC $
DFIX12000:table.c 19mar99
transit.c $Revision$ $Date$
unless.c $Revision: /main/NILGIRIS/4 $ $Date: 2002/0
6/27 14:09 UTC $
DFIX12000:unless.c 19mar99
assembler.c $Revision: /main/NILGIRIS/1 $ $Date: 200
0/01/28 14:19 UTC $
bif_oid.c $Revision: 1.1 $ $Date: 1997/09/25 05:08:2
4 $
dicts.c $Revision: 1.18 $ $Date: 1998/03/27 09:02:35
$
dicts.c $Revision: /main/NILGIRIS/2 $ $Date: 2002/06
/20 15:04 UTC $
endecrypt.c $Revision: 1.1 $ $Date: 1997/10/15 09:57
:37 $
interpreter.c $Revision: /main/NILGIRIS/9 $ $Date: 2
002/06/20 15:02 UTC $
library.c $Revision: /main/NILGIRIS/2 $ $Date: 2002/
06/20 15:06 UTC $
opc_pattern.c $Revision: /main/2 $ $Date: 1998/08/21
10:33 UTC $
circuit.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/
07/02 05:52 UTC $
engine.c $Revision: 1.15 $ $Date: 1997/08/14 00:08:4
2 $
node.c $Revision: 1.44 $ $Date: 1998/05/01 04:33:53
$
nodeclass.c $Revision: 1.16 $ $Date: 1997/09/26 07:3
7:47 $
notify.c $Revision: 1.2 $ $Date: 1997/08/07 08:13:22
$
patching.c $Revision: 1.8 $ $Date: 1997/12/15 06:19:
31 $
port.c $Revision: 1.11 $ $Date: 1996/05/15 05:45:40
$
stream.c $Revision: /main/NILGIRIS/5 $ $Date: 2000/0
1/18 07:32 UTC $
streamio.c $Revision: /main/NILGIRIS/4 $ $Date: 2000
/02/15 15:22 UTC $
ctxtmap.c $Revision: 1.3 $ $Date: 1998/01/29 08:58:2
4 $
datastore.c $Revision: 1.8 $ $Date: 1998/07/25 18:31
:39 $
dfstore.c $Revision: /main/2 $ $Date: 1998/08/07 15:
39 UTC $
factstore.c $Revision: 1.8 $ $Date: 1998/07/25 18:36
:10 $
query.c 1.16 1996/11/20 23:28:02
sequence.c $Revision: 1.17 $ $Date: 1998/01/28 03:39
:17 $
anno_event.c $Revision: 1.18 $ $Date: 1997/08/29 00:
49:58 $
endecode.c $Revision: /main/NILGIRIS/3 $ $Date: 2000
/01/28 15:09 UTC $
value.c $Revision: /main/NILGIRIS/9 $ $Date: 2002/07
/09 09:54 UTC $
PATCH PHSS_27417, Consolidated Patch July 2002
PATCH PHSS_27335, June 2002
vstring.c $Revision: /main/2 $ $Date: 1998/08/21 10:
54 UTC $
timesync.c $Revision: 1.9 $ $Date: 1997/03/24 08:20:
28 $
container.c $Revision: 1.17 $ $Date: 1998/02/18 00:4
9:18 $
char_sets.c $Revision: /main/2 $ $Date: 1998/08/21 1
0:39 UTC $
engmgr.c $Revision: /main/NILGIRIS/7 $ $Date: 2000/0
3/01 09:41 UTC $
dictionary.c $Revision: 1.23 $ $Date: 1998/04/01 06:
13:08 $
engine_dict.c $Revision: 1.7 $ $Date: 1998/03/23 07:
30:52 $
ECS.c $Revision: 1.9 $ $Date: 1998/04/22 23:30:06 $
ECS 3.1 (A.03.10)
ECS REV: A.03.10
ecsLocale.c $Revision: /main/2 $ $Date: 1998/08/21 1
0:59 UTC $
perror.c $Revision: /main/NILGIRIS/1 $ $Date: 2002/0
6/24 05:45 UTC $
annotate.c $Revision: /main/NILGIRIS/1 $ $Date: 2000
/01/18 07:35 UTC $
annotate.c $Revision: /main/NILGIRIS/1 $ $Date: 1999
/09/29 12:35 UTC $
memory.c $Revision: /main/NILGIRIS/1 $ $Date: 2002/0
4/24 10:02 UTC $
memory.c $Revision$ $Date$
trace.c $Revision: 1.4 $ $Date: 1998/06/10 09:01:45
$
log.c 1.27 1996/06/03 04:56:34
/opt/OV/contrib/ecs/ecsevgen:
HP aC++ B3910B A.03.13 Language Support Library
ecsevgen.c $Revision: /main/NILGIRIS/7 $ $Date: 2002
/04/09 12:52 UTC $
PATCH PHSS_25339, (PTSfc01871) Sep 2001
ascii.c $Revision: /main/NILGIRIS/1 $ $Date: 2000/01
/28 14:18 UTC $
ascii_alloc.c $Revision$ $Date$
parse.c $Revision: /main/2 $ $Date: 1998/08/21 10:29
UTC $
token_set.c $Revision$ $Date$
endecode.c $Revision: /main/NILGIRIS/3 $ $Date: 2000
/01/28 15:09 UTC $
anno_event.c $Revision: 1.18 $ $Date: 1997/08/29 00:
49:58 $
sockstack.c $Revision: /main/NILGIRIS/2 $ $Date: 200
1/02/01 13:10 UTC $
DFIX12001:sockstack.c 01Sept99
eventio.c $Revision: 1.37 $ $Date: 1998/05/18 04:14:
16 $
value.c $Revision: /main/NILGIRIS/9 $ $Date: 2002/07
/09 09:54 UTC $
PATCH PHSS_27417, Consolidated Patch July 2002
PATCH PHSS_27335, June 2002
vstring.c $Revision: /main/2 $ $Date: 1998/08/21 10:
54 UTC $
container.c $Revision: 1.17 $ $Date: 1998/02/18 00:4
9:18 $
fatal.c $Revision: 1.13 $ $Date: 1998/05/07 02:26:33
$
log.c $Revision: 1.7 $ $Date: 1997/07/04 07:34:11 $
mesgbuf.c $Revision: 1.18 $ $Date: 1998/05/07 00:28:
35 $
trace.c $Revision: 1.12 $ $Date: 1998/03/12 04:48:38
$
berova.c $Revision: /main/NILGIRIS/4 $ $Date: 2001/1
0/19 04:28 UTC $
md.c $Revision$ $Date$
ECS.c $Revision: 1.9 $ $Date: 1998/04/22 23:30:06 $
ECS 3.1 (A.03.10)
ECS REV: A.03.10
DFIX15000: dtd.c 01Oct1999
DFIX15001: dict.c 21Dec1999
DFIX15014: ber.c 13Dec2000
DFIX15000: ber.c 01Oct1999, 13sep2000
DFIX15000: enum.c 01Oct1999
DFIX15000: cii_ent.c 30sep1999
PATCH PHSS_20050, 990929
DFIX15000: pm_ipc.c 30sep1999
PATCH/11.00:PHCO_13283 libc.a_ID/main/r11ros/cup_l
ibc-ros-cpe/1
/ux/core/libs/libc/archive_pa1/libc.a_ID
Nov 19 1997 13:12:09
/opt/OV/bin/ecsmgr:
HP aC++ B3910B A.03.13 Language Support Library
ecsmgr.c $Revision: /main/2 $ $Date: 1998/08/08 10:2
2 UTC $
mgrEcsmgr.c $Revision: /main/NILGIRIS/7 $ $Date: 200
2/04/09 12:56 UTC $
PATCH PHSS_26086, Jan 2002
sockmgr.c $Revision: /main/NILGIRIS/3 $ $Date: 2000/
01/18 07:46 UTC $
engsockmgr.c $Revision: 1.5 $ $Date: 1997/04/09 05:1
2:44 $
engmgr.c $Revision: /main/NILGIRIS/7 $ $Date: 2000/0
3/01 09:41 UTC $
circuit.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/
07/02 05:52 UTC $
engine.c $Revision: 1.15 $ $Date: 1997/08/14 00:08:4
2 $
stream.c $Revision: /main/NILGIRIS/5 $ $Date: 2000/0
1/18 07:32 UTC $
node.c $Revision: 1.44 $ $Date: 1998/05/01 04:33:53
$
nodeclass.c $Revision: 1.16 $ $Date: 1997/09/26 07:3
7:47 $
notify.c $Revision: 1.2 $ $Date: 1997/08/07 08:13:22
$
port.c $Revision: 1.11 $ $Date: 1996/05/15 05:45:40
$
streamio.c $Revision: /main/NILGIRIS/4 $ $Date: 2000
/02/15 15:22 UTC $
log.c 1.27 1996/06/03 04:56:34
control.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/
07/12 09:30 UTC $
engine_control.c $Revision: /main/NILGIRIS/5 $ $Date
: 2000/02/22 14:08 UTC $
annotate.c $Revision: /main/NILGIRIS/1 $ $Date: 1999
/09/29 12:35 UTC $
bus.c $Revision$ $Date$
clock.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/07
/02 05:55 UTC $
DFIX12000:clock.c 19mar99
combine.c $Revision: /main/NILGIRIS/2 $ $Date: 2001/
01/06 09:20 UTC $
count.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/09
/29 12:35 UTC $
create.c $Revision: /main/NILGIRIS/2 $ $Date: 2000/0
2/04 15:32 UTC $
extract.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/
09/29 12:36 UTC $
filter.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/0
9/29 12:36 UTC $
input.c $Revision: /main/NILGIRIS/5 $ $Date: 2001/02
/20 12:04 UTC $
loader.c $Revision$ $Date$
memory.c $Revision: /main/NILGIRIS/1 $ $Date: 2002/0
4/24 10:02 UTC $
modify.c $Revision: /main/NILGIRIS/1 $ $Date: 1999/0
9/29 12:30 UTC $
output.c $Revision$ $Date$
rate.c $Revision: /main/NILGIRIS/3 $ $Date: 1999/10/
25 11:06 UTC $
DFIX12000:rate.c 19mar99
PATCH PHSS_18006, Consolidated patch Mar 1999
rearrange.c $Revision$ $Date$
table.c $Revision: /main/NILGIRIS/2 $ $Date: 1999/09
/29 12:31 UTC $
DFIX12000:table.c 19mar99
unless.c $Revision: /main/NILGIRIS/4 $ $Date: 2002/0
6/27 14:09 UTC $
DFIX12000:unless.c 19mar99
delay.c $Revision$ $Date$
transit.c $Revision$ $Date$
assembler.c $Revision: /main/NILGIRIS/1 $ $Date: 200
0/01/28 14:19 UTC $
dicts.c $Revision: /main/NILGIRIS/2 $ $Date: 2002/06
/20 15:04 UTC $
interpreter.c $Revision: /main/NILGIRIS/9 $ $Date: 2
002/06/20 15:02 UTC $
library.c $Revision: /main/NILGIRIS/2 $ $Date: 2002/
06/20 15:06 UTC $
memory.c $Revision$ $Date$
bif_oid.c $Revision: 1.1 $ $Date: 1997/09/25 05:08:2
4 $
dicts.c $Revision: 1.18 $ $Date: 1998/03/27 09:02:35
$
endecrypt.c $Revision: 1.1 $ $Date: 1997/10/15 09:57
:37 $
opc_pattern.c $Revision: /main/2 $ $Date: 1998/08/21
10:33 UTC $
dictionary.c $Revision: 1.23 $ $Date: 1998/04/01 06:
13:08 $
engine_dict.c $Revision: 1.7 $ $Date: 1998/03/23 07:
30:52 $
ctxtmap.c $Revision: 1.3 $ $Date: 1998/01/29 08:58:2
4 $
datastore.c $Revision: 1.8 $ $Date: 1998/07/25 18:31
:39 $
dfstore.c $Revision: /main/2 $ $Date: 1998/08/07 15:
39 UTC $
factstore.c $Revision: 1.8 $ $Date: 1998/07/25 18:36
:10 $
query.c 1.16 1996/11/20 23:28:02
sequence.c $Revision: 1.17 $ $Date: 1998/01/28 03:39
:17 $
endecode.c $Revision: /main/NILGIRIS/3 $ $Date: 2000
/01/28 15:09 UTC $
anno_event.c $Revision: 1.18 $ $Date: 1997/08/29 00:
49:58 $
trace.c $Revision: 1.4 $ $Date: 1998/06/10 09:01:45
$
value.c $Revision: /main/NILGIRIS/9 $ $Date: 2002/07
/09 09:54 UTC $
PATCH PHSS_27417, Consolidated Patch July 2002
PATCH PHSS_27335, June 2002
vstring.c $Revision: /main/2 $ $Date: 1998/08/21 10:
54 UTC $
fatal.c $Revision: 1.13 $ $Date: 1998/05/07 02:26:33
$
log.c $Revision: 1.7 $ $Date: 1997/07/04 07:34:11 $
mesgbuf.c $Revision: 1.18 $ $Date: 1998/05/07 00:28:
35 $
trace.c $Revision: 1.12 $ $Date: 1998/03/12 04:48:38
$
container.c $Revision: 1.17 $ $Date: 1998/02/18 00:4
9:18 $
char_sets.c $Revision: /main/2 $ $Date: 1998/08/21 1
0:39 UTC $
patching.c $Revision: 1.8 $ $Date: 1997/12/15 06:19:
31 $
sockstack.c $Revision: /main/NILGIRIS/2 $ $Date: 200
1/02/01 13:10 UTC $
DFIX12001:sockstack.c 01Sept99
ECS.c $Revision: 1.9 $ $Date: 1998/04/22 23:30:06 $
ECS 3.1 (A.03.10)
ECS REV: A.03.10
PATCH/11.00:PHCO_13283 libc.a_ID/main/r11ros/cup_l
ibc-ros-cpe/1
/ux/core/libs/libc/archive_pa1/libc.a_ID
Nov 19 1997 13:12:09
cksum(1) Output:
OVECS.OVECS-CMG,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP:
2232738404 44692 /opt/OV/www/lib/ecs/ecsmgr.ovpl
3502586991 232327 /opt/OV/www/htdocs/classes/cmg/cmg.jar
OVECS.OVECS-DES,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP:
545967512 13533184 /opt/OV/bin/ecsdes2
477784460 2369180 /opt/OV/bin/ecdlheap
2237605577 3908 /etc/opt/OV/share/conf/ecs/modules/
ecs_defaults.ecs
OVECS.OVECS-RUN-MAN,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP:
2288411271 10100 /opt/OV/man/man1m.Z/ecsmgr.1m
OVECS.OVECS-RUN,fr=A.03.10,fa=HP-UX_B.11.00_32/64,v=HP:
697097021 1597440 /opt/OV/lib/libCE.3
2438249233 2408448 /opt/OV/contrib/ecs/ecsevgen
1904103679 2510848 /opt/OV/bin/ecsmgr
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_27335 PHSS_26086 PHSS_25339
Equivalent Patches:
PHSS_27416:
s700: 10.20
s800: 10.20
PSOV_03187:
sparcSOL: 2.6 2.7 2.8
Patch Package Size: 22270 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_27417
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27417.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27417. 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_27417.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_27417.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27417.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
BEFORE LOADING THIS PATCH...
If there is any ECS designer running, this needs to be
closed. If you are using ECS with any other process,
these sessions need to be closed.
WARNING : the patch will not install if any ECS
designer process or any other processes using ECS
engine 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 : 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_27417------------------------------------------
Document ID: PHSS_27276
Date Loaded: 20020711
Title: s700_800 11.04 Virtualvault 4.6 itcwdog startup fix
Patch Name: PHSS_27276
Patch Description: s700_800 11.04 Virtualvault 4.6 itcwdog startup fix
Creation Date: 02/06/21
Post Date: 02/07/11
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products:
VirtualVault A.04.60
Filesets:
VaultTS.VV-IWS,fr=A.04.60,fa=HP-UX_B.11.04_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_27276
Symptoms:
PHSS_27276:
If the tomcat watchdog program(itcwdog) is
terminated without updating its respective
server process id file, subsequent attempts
to start the watchdog may report that
the "Tomcat watchdog is already running"
and the server fails to start.
This will also result in stopping a wrong process
if the watchdog is restarted using vvctl.
Defect Description:
PHSS_27276:
If during some system operations itcwdog is
not cleanly stopped, the process identifier(pid)
file may contain the process id of a process
other than the watchdog process. This will
result in "Tomcat watchdog is already running"
error during startup.
In the above scenario, an attempt to restart
the watchdog will result in stopping the process
associated with the process ID in the pid file.
Resolution:
The apachectl program will perform a check to see
if the process identifier in the watchdog pid
file belongs to an executing itcwdog process
before declaring that the watchdog is already
running.
SR:
8606264443
Patch Files:
VaultTS.VV-IWS,fr=A.04.60,fa=HP-UX_B.11.04_32/64,v=HP:
/opt/vaultTS/ws-admserv/bin/apachectl
what(1) Output:
VaultTS.VV-IWS,fr=A.04.60,fa=HP-UX_B.11.04_32/64,v=HP:
/opt/vaultTS/ws-admserv/bin/apachectl:
Source: apache/ship/misc/apachectl, vaultTS, vaultTS
_4.6 $ $Date: 02/06/25 10:50:23 $ $Revision:
1.18 PATCH_11.04 (PHSS_27276) $
(#)48 1.18 apache/ship/misc/apachectl, vaultTS, v
aultTS_4.6 06/25/02 10:50:23
cksum(1) Output:
VaultTS.VV-IWS,fr=A.04.60,fa=HP-UX_B.11.04_32/64,v=HP:
3185905092 22879 /opt/vaultTS/ws-admserv/bin/apachectl
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHSS_27275:
s700: 11.04
s800: 11.04
Patch Package Size: 50 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_27276
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27276.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27276. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHSS_27276.depot
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_27276.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_27276.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27276.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHSS_27276------------------------------------------
Document ID: PHNE_26550
Date Loaded: 20020711
Title: s700_800 11.00 PCI FDDI B.11.00-B.11.00.16 cumulative patch
Patch Name: PHNE_26550
Patch Description: s700_800 11.00 PCI FDDI B.11.00-B.11.00.16 cumulative patch
Creation Date: 02/06/04
Post Date: 02/07/11
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
PCI FDDI B.11.00 B.11.00.01 B.11.00.02 B.11.00.03 B.11.00.05
B.11.00.08 B.11.00.11 B.11.00.12 B.11.00.13 B.11.00.15
B.11.00.16
Filesets:
FDDI-PCI.FDDI4-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.01,fa=HP-UX_B.11.00_64,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.02,fa=HP-UX_B.11.00_64,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.03,fa=HP-UX_B.11.00_64,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_64,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.08,fa=HP-UX_B.11.00_64,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.11,fa=HP-UX_B.11.00_64,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.12,fa=HP-UX_B.11.00_64,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.13,fa=HP-UX_B.11.00_64,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.15,fa=HP-UX_B.11.00_64,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.16,fa=HP-UX_B.11.00_64,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_32,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.08,fa=HP-UX_B.11.00_32,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.11,fa=HP-UX_B.11.00_32,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.12,fa=HP-UX_B.11.00_32,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.13,fa=HP-UX_B.11.00_32,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.15,fa=HP-UX_B.11.00_32,v=HP
FDDI-PCI.FDDI4-KRN,fr=B.11.00.16,fa=HP-UX_B.11.00_32,v=HP
FDDI-PCI.FDDI4-RUN,fr=B.11.00.05,fa=HP-UX_B.11.00_32/64,v=HP
FDDI-PCI.FDDI4-RUN,fr=B.11.00.08,fa=HP-UX_B.11.00_32/64,v=HP
FDDI-PCI.FDDI4-RUN,fr=B.11.00.11,fa=HP-UX_B.11.00_32/64,v=HP
FDDI-PCI.FDDI4-RUN,fr=B.11.00.12,fa=HP-UX_B.11.00_32/64,v=HP
FDDI-PCI.FDDI4-RUN,fr=B.11.00.13,fa=HP-UX_B.11.00_32/64,v=HP
FDDI-PCI.FDDI4-RUN,fr=B.11.00.15,fa=HP-UX_B.11.00_32/64,v=HP
FDDI-PCI.FDDI4-RUN,fr=B.11.00.16,fa=HP-UX_B.11.00_32/64,v=HP
FDDI-PCI.FDDI4-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
FDDI-PCI.FDDI4-RUN,fr=B.11.00.01,fa=HP-UX_B.11.00_64,v=HP
FDDI-PCI.FDDI4-RUN,fr=B.11.00.02,fa=HP-UX_B.11.00_64,v=HP
FDDI-PCI.FDDI4-RUN,fr=B.11.00.03,fa=HP-UX_B.11.00_64,v=HP
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.08,fa=HP-UX_B.11.00_32/64,v=HP
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.11,fa=HP-UX_B.11.00_32/64,v=HP
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.12,fa=HP-UX_B.11.00_32/64,v=HP
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.13,fa=HP-UX_B.11.00_32/64,v=HP
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.15,fa=HP-UX_B.11.00_32/64,v=HP
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.16,fa=HP-UX_B.11.00_32/64,v=HP
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
No (superseded patches were critical)
PHNE_20874: PANIC
PHNE_19542: ABORT PANIC
PHNE_18524: PANIC CORRUPTION
A reset while on the interrupt stack can cause
a panic or a data corruption.
PHNE_17517: HANG
The interface can hang while transmitting UDP
packets.
PHNE_16689: HANG
After an interface hang, manual intervention is
required to get the link going again.
PHNE_15670: PANIC HANG OTHER
The V-class system may panic or hang during boot.
With the Gigabit Ethernet card, the system may come
up, but the FDDI adapter card will be unusable.
PHNE_14555: PANIC
PHNE_13212: OTHER
The affected interface may appear to be hung.
PHNE_13184: PANIC
Category Tags:
defect_repair enhancement general_release critical panic
halts_system corruption
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_26550
Symptoms:
PHNE_26550:
1. SR: 8606227088 CR: JAGad96150
ftp/rcp applications fail on PCI FDDI link while
transferring a file from a NFS mounted file system
to a remote node. The following message is logged in
syslog.log: "More than one page crossing".
2. SR: 8606182683 CR: JAGad51900
In case of non-cache coherent A and B class systems,
PCI FDDI driver prints the following message repeatedly
on the system console or syslog.log file:
"vmunix FDDI[2] WARNING: cmd=0 failure status=lcee90".
However PCI FDDI link continues to function normally.
3. SR: 8606156934 CR: JAGad26268
ER: SNMP sub-agent for PCI FDDI is not available.
4. SR: 8606166638 CR: JAGad35925
PCI FDDI link goes DOWN on an highly loaded system with
its entry being removed from the routing table. Reset of
the adapter brings the FDDI link UP.
5. SR: 8606168617 CR: JAGad37895
If the system is installed with PHCO_21596 or its
superseding patch, and later "insf -e" is run to
re-create the device files, fddipciadmin command fails
with a message similar to the following :
"fddipciadmin:/dev/lan1 is not a valid device,
errno = 19".
6. SR: 8606220085 CR: JAGad89226
"Set user ID" bit should not be set for PCI FDDI
lanadmin shared library.
7. SR: 8606257419 CR: JAGae21722
ER: The unsolicited events logged in NetTL log file,
by PCI FDDI driver do not provide event type
information.
8. SR: 8606257686 CR: JAGae21989
Reset of PCI FDDI adapter sometimes fails with the
following message on the system console or in
syslog.log file:
"vmunix fddi4[2], reclaim_res: Card in wrong state
4, ff, 872, fddi4_rest".
9. SR: 8606263674 CR: JAGae27999
If the T_Req value is set using fddipciadmin command
and is followed by a lanadmin reset, then PCI FDDI
driver sets an invalid T_Req value in the adapter.
10.SR: 8606263677 CR: JAGae28002
PCI FDDI driver logs the same data twice in NetTL trace
file, if tracing is enabled for both HDR and PDU trace
Kinds.
PHNE_20874:
1. ER: An application that has an unbound promiscuous
stream running over a PCI FDDI interface does not see
packets that are being sent out from the host (outbound
packets) on that interface.
2. A command to clear statistics on a functional PCI FDDI
interface using the lanadmin(1M) command fails with the
message : 'Unable to clear statistics registers.'
3. ER: Storing of per-interface configuration information
across boots and hence system boot-time per-interface
automatic configuration not possible with the PCI FDDI
product.
4. Under heavy network traffic conditions over the PCI
FDDI interface, a V class system may panic with 'Epic
Channel Error'.
5. The netfmt(1M) command when run over a file containing
nettl(1M) network traces for a PCI FDDI interface may
core-dump with a 'memory fault'.
6. ER: The ioscan(1M) command does not display the PCI
FDDI card hardware revision (namely A3739A or A3739B)
installed on a system.
7. ER: The PCI FDDI product fails to function with the
Lan-Monitor product.
8. A system with the PCI FDDI product installed from the
June 2000 application release may panic with a 'data
memory protection fault' when an application running
sustained heavy loopback traffic over a PCI FDDI
interface is closed. The loopback packets have a
non-SNAP destination SAP (Service Access Point).
i.e. a destination SAP that is not equal to 0xAA.
PHNE_19542:
1. Applications using DLPI Type-2 connection oriented
protocol over the PCI FDDI interface are unable to
connect to a peer on another system.
2. On a cable disconnect/reconnect or when resetting the
card using the lanadmin(1M) command, the system panics
with: "panic: wait_for_lock: Already own this lock!"
3. The PCI FDDI interface state as seen using the
ifconfig(1M) command does not change on cable disconnects
(from UP to DOWN) and reconnects (from DOWN to UP).
PHNE_18524:
1. Panic with epic channel error on V-class and panic with
data page fault on N-class.
2. When an automatic reset of the card fails, it is not
reattempted.
3. I/O address allocation is inefficient.
4. Heavy outbound traffic can cause the timer to falsely
detect a DMA timeout, and then reset the card.
PHNE_17517:
1. The interface can hang while transmitting UDP packets
on a workstation.
2. Nettl tracing for the kinds hdrin, hdrout, and loopback
does not provide any output.
PHNE_16689:
1. A hung interface with a message "This interface appears
to be hung" in dmesg output.
2. The default t_req time is too small. It is not consistent
with the other FDDI products.
3. The multicast address displayed by fddipciadmin command
is in the wrong byte order.
4. After an online reset, the multicast list, the
promiscuous mode and the MAC address are not restored.
5. The B.11.00 version of fddipciadmin is in a different
location than other versions.
PHNE_15670:
1. On V-class systems, there are two groups of slots in
a card cage. Each group is identified by the digit X
of the hardware path X/Y/0 in the ioscan command output.
The PCI FDDI card cannot be installed in the same slot
group as Gigabit Ethernet, Token Ring, ATM, X.25 or
HyperFabric card. The system may panic or hang during
boot or the FDDI card may be unusable if the system
comes up.
2. The driver is not optimized for TPC-C.
PHNE_15269:
1. The "netstat -in" command reports an incorrect MTU size
after the "lanadmin -R" command was used to reset the
size to the FDDI standard (4352 bytes).
2. The TPC-C number is not as high as expected.
3. An unbound SAP promiscuous stream either receives packets
of unknown DSAP values or receives packets destined for
other promiscuous streams attached to this link.
PHNE_14555:
1. V-class system panic with messages like the following:
"Global error on Epic 0, Device 0, Driver fddi4" and
"Error Info: 80178000:00000012".
2. The "mk_kernel" command fails, if FDDI was the only
driver configured in the system that depends on "wsio".
3. lanadmin(1M) fails with a message "Cannot open shared
library /usr/lib/lanadmin/libdsfddi4.sl" after
repeated use of the statistics display command.
PHNE_13212:
Observed "FDDI Warning - Code: 2002 4" in dmesg during one
stress test on a 6 way V-2200. Linkloop and ping stopped
working on the affected interface. Reset the card through
lanadmin and brought the interface back.
PHNE_13184:
Using the LLA interface to the PCI FDDI driver causes a
panic.
Defect Description:
PHNE_26550:
1. SR: 8606227088 CR: JAGad96150
The problem happens when the file system is NFS mounted
with a high rsize/wsize value, which is set using mount
command. In the outbound path, PCI FDDI driver drops
packets received from upper layers, which spans more
than 2 physical pages.
Resolution:
The PCI FDDI driver is modified to handle MBLK's with
data buffers spanning more than 2 physical pages.
2. SR: 8606182683 CR: JAGad51900
On non-cache coherent IO systems, PCI FDDI driver did
not purge the processor cache while queuing the command
response buffers to the card. On command response, the
PCI FDDI driver reads the stale command response status,
thus resulting in error messages.
Resolution:
PCI FDDI driver is changed to purge the processor cache
before the command response buffers are queued.
3. SR: 8606156934 CR: JAGad26268
PCI FDDI does not have SNMP sub-agent.
Resolution:
SNMP sub-agent for PCI FDDI is provided.
4. SR: 8606166638 CR: JAGad35925
In case of transient high memory usage in the system,
the LINK-UP message sent from PCI FDDI driver during
an internal reset fails. As PCI FDDI driver did not
check the return status from the LINK-UP call and also
as there is no retry involved, the link continues to
remain DOWN.
Resolution:
The PCI FDDI driver is modified to check the return
value from LINK-UP call sent to DLPI. In case of
failure, the timer routine will retry sending the
LINK-UP event.
5. SR: 8606168617 CR: JAGad37895
Minor numbers for PCI FDDI device files were not created
and handled as per the IO-TREE standard. When "insf -e"
command is run to re-create the device files, the
PCI FDDI minor numbers got changed and hence
fddipciadmin command fails.
Resolution:
PCI FDDI startup scripts and the driver are changed to
create and handle the minor numbers as per the
IO-TREE standard.
6. SR: 8606220085 CR: JAGad89226
"Set user ID" bit is currently set in PCI FDDI lanadmin
shared library which is not required.
Resolution:
The permission of the lanadmin shared library is changed
appropriately.
7. SR: 8606257419 CR: JAGae21722
PCI FDDI driver does not interpret the event type
information passed from the adapter as part of the
unsolicited event.
Resolution:
PCI FDDI driver is enhanced to interpret the unsolicited
event and log the event with event type information in
NetTL log file.
8. SR: 8606257686 CR: JAGae21989
After issuing the reset command to the adapter, the
hardware state of the adapter is incorrectly read as
FDDI4_STATE_DMA_UNAVAIL, though the actual state is
FDDI4_STATE_RESET. This results in the failure of reset
process and the error message is logged.
Resolution:
The sampling frequency of reading the "hardware state"
is reduced, thereby reducing the chances of driver
reading an incorrect hardware state.
9. SR: 8606263674 CR: JAGae27999
When T_Req value is changed using fddipciadmin command,
PCI FDDI driver sends the correct T_Req value to
the adapter but stores an incorrect T_Req value in the
driver structure. This invalid T_Req value is later
restored in the adapter during the lanadmin reset.
Resolution:
PCI FDDI driver is changed to store the correct T_Req
value in the driver structure.
10.SR: 8606263677 CR: JAGae28002
PCI FDDI driver logs the same data twice in NetTL trace
file, if tracing is enabled for both HDR and PDU trace
Kinds.
Resolution:
PCI FDDI driver is changed to log the data in NetTL
trace file, only for PDU trace Kind.
PHNE_20874:
1. CR JAGaa22135
The driver passed all inbound packets received on the
interface to the unbound promiscuous stream but did not
pass packets being sent out of the PCI FDDI interface
(outbound packets). There is now a requirement to
allow an unbound promiscuous stream to receive inbound
as well as outbound packets.
Resolution:
The driver has been enhanced to make a copy of the
outbound packets and send the copy to the unbound
promiscuous stream.
2. CR JAGab72054 / SR 8606104480
The PCI FDDI driver did not implement the command to
clear statistics of the interface and returned an error
value on receiving such a command, resulting in
lanadmin(1M) printing the error message 'Unable to
clear statistics registers.'.
Resolution:
The driver has been enhanced to handle the command to
clear the statistics on the interface/driver and return
a value of 0 to lanadmin(1M) if the command succeeds or
a non-zero error value indicating the type of error
encountered when the command fails.
3. CR JAGab64952 / SR 5003452128
The PCI FDDI product did not have a configuration file
to store per-interface configuration. Hence the
product start up scripts that are executed at boot time
did not re-configure the interfaces to previously
configured values.
Resolution:
Starting with the application release of June 2000 and
patch PHNE_20874 (and later application releases and
superseding patches), a per-interface configuration
file, hpfddi4conf, is installed. This file enables an
user to store the station address, MTU (Maximum
Transmission Unit), the T_Req and T_Notify values for
FDDI station management on a per interface basis across
boots. The existing product start-up script
(/sbin/init.d/hppcifddi), that is automatically run
during system boot has been enhanced to read the
configured values from the above mentioned
configuration file and initialize the PCI FDDI
interfaces. See field 'Special Installation
Instructions' for the location of the configuration
file and instructions on using this feature.
4. CR JAGab76910 / SR 8606107182
On a V class, the descriptor block defining the buffers
to be used by the card is present in shared memory,
rather than the host/system memory. The PCI FDDI
driver posted a card descriptor for card receive
buffers (for inbound packets) to the shared memory
descriptor block and later wrote to card registers
indicating the availability of the new receive buffer
descriptors for the card. Under heavy network load,
the values written to the card register could reach the
card before the card descriptor reach the shared memory
block. The card then fetched the old/invalid card
descriptor and attempted to write to the memory
location specified by the descriptor resulting in a
system panic with the 'Epic Channel Error' panic
string.
Resolution:
The PCI FDDI driver has been fixed to ensure that the
descriptor write is complete before updating the card
registers, thus avoiding the situation described above.
5. CR JAGad01877 / SR 8606132729
When the netfmt(1M) command called the PCI FDDI
subsystem formatter library to format PCI FDDI traces,
an invalid parameter was passed to formatting routine
that could result in the process accessing an invalid
virtual address, resulting in the netfmt(1M) command
dumping core with a 'memory fault' message.
Resolution:
The PCI FDDI subsystem formatter library routine has
been corrected to pass correct valid values as
parameters to the formatting routine.
6. CR JAGad01893 / SR 8606132745
The driver did not store the information regarding the
PCI FDDI card revision in the database used by the
ioscan(1M) command. Hence the information on the PCI
FDDI card installed on the system was not displayed by
the ioscan(1M) command.
Resolution:
The PCI FDDI driver now determines the card hardware
revision during initialization of the card and logs the
information in the database used by the ioscan(1M)
command.
7. CR JAGad00071 / SR 8606130913
PCI FDDI driver did not have the enhancements required
to direct packets destined for the SAPs (Service Access
Points) used by the Lan Monitor product. Hence the Lan
Monitor product would not function as expected.
Resolution:
The PCI FDDI driver has been enhanced to support SAPs
used by the Lan Monitor product.
8. CR JAGad08463 / SR 8606139173
This defect could occur when the PCI FDDI product from
the June 2000 application release was installed on a
system which had a stream bound to a non-SNAP SAP (i.e.
the SAP value is not 0xAA) sending packets destined to
itself (loopback) in a sustained manner. When the
stream/application was closed, there could be a time
window during which there were packets destined for the
now closed stream. In order to decide on a valid bound
stream for the packet, the driver would attempt to
parse unaligned fields in the packets resulting in a
'data memory protection fault' panic.
Resolution:
The PCI FDDI driver now performs additional validations
for non-SNAP packets to avoid accessing unaligned
fields in the packet and drops the packet if the stream
it was destined for could not be found.
PHNE_19542:
1. The PCI FDDI driver was dropping inbound DLPI Type-2
packets. Besides the above defect in the PCI FDDI
driver, the lan-common module used to convert canonical
MAC addresses to wire format for outbound DLPI Type-2
packets before passing on the packet to the PCI FDDI
driver. The PCI FDDI card would also make the above
conversion resulting in frames with incorrect MAC
addresses being sent out on the wire. Either of the
above defects would result in DLPI Type-2 packets being
dropped and applications using DLPI Type-2 being unable
to connect to their peers.
Resolution:
Inbound DLPI Type-2 packets are now processed by the
driver and passed up to the required stream. The
lan-common defect has been fixed in the lan-common patch
PHNE_19081 (or a superseding patch).
2. When lan-common patch PHNE_19081 or a superseding patch
is installed on a system with PCI FDDI, calls from the
PCI FDDI driver to send link events upstream (as on cable
disconnects/reconnects) will be sent upstream to IP by
the lan-common module. In a STREAMS environment, during
calls to an upstream module, a turnover could occur with
a call back to the driver on the same thread, resulting
in a spinlock deadlock, due to the lock being requested
already being held by the driver. The above panic occurs
only when the lan-common patch PHNE_19081 (or a
superseding patch) is installed on the system.
Resolution:
Spinlocks are released before calls to upstream routines
and reacquired on return from the call.
3. Prior to lan-common patch PHNE_19081, link events were
not sent upstream to IP. Hence any link events generated
by the driver were ignored and not reflected in the
ifonfig(1M) output. Additionally the PCI FDDI driver was
not generating a 'link up' event upon receiving a 'link
up' indication from the adapter. This behavior will not
be exposed until PHNE_19081 ( or a superseding patch ) is
installed.
Resolution:
The driver has been changed to send 'link up' event to
the IP stream when an interrupt is received from the card
indicating link availability.
PHNE_18524:
1. An automatic reset, while the driver is still handling
inbound traffic, causes the driver to use stale DMA
descriptor indices. A spurious link available interrupt
can cause the driver to go from a DEAD state to a READY
state, causing the driver to use invalid data.
Resolution:
Always initialize the descriptor indices from the
driver's global data structure rather than local data.
Don't allow the driver to go directly from the DEAD
state to the READY state when a link available interrupt
occurs.
2. Reattempting automatic resets was not implemented.
Resolution:
If an automatic reset fails, it will be reattempted up
to six times.
3. I/O address mapping options were not optimized.
Resolution:
I/O address mapping services perform most efficiently
when a default specification of non-interleaved I/O
addresses is used when calling the mapping functions.
The driver has been modified to use such a specification
in all I/O address mapping function calls.
4. The timer assumed that a transmit DMA timeout or a
command response timeout were logical reasons to initiate
an adapter reset.
Resolution:
Timeout and reset the adapter only if there are no
transmit completion or command response completion
interrupts pending.
PHNE_17517:
1. The driver did not map the first outbound memory buffer
properly if it crossed a page boundary. This condition
may occur when running UDP applications on workstations.
2. Nettl tracing for the kinds hdrin, hdrout, and loopback
was not implemented.
PHNE_16689:
1. Driver did not have a built-in reset mechanism to
recover from a card hang, whether it is due to a DMA
timeout or a card halt event.
2. The 8ms default t_req time (as opposed to 165ms in other
products) was suspected to be the cause for ring
drops. Customer also asked for the ability to change
t_req time and t_notify time online.
3. A defect in the adapter's firmware caused the card to
return the multicast addresses in a wrong format.
4. Driver's reset routine did not restore those parameters.
As a result, for example, multicast or promiscuous mode
stopped working after a lanadmin reset.
5. The B.11.00 version of fddipciadmin was incorrectly
placed in /usr/bin. Subsequent releases place it
correctly in /usr/sbin. This patch corrects the location
if the B.11.00 version of fddipciadmin is installed.
PHNE_15670:
1. The PCI FDDI card expects the shared memory to be aligned
on an 8K byte boundary. If any of the drivers allocate
shared memory that is not a multiple of 8K before FDDI,
the shared memory allocated by the FDDI driver will not
be 8K aligned. One such failing case is to have the FDDI
card in slot 2 and an ATM card in slot 1.
The slot number is identified by the digit Y of the
hardware path X/Y/0.
2. The driver was not compiled with profile based
optimization (PBO) data to improve the driver
performance.
PHNE_15269:
1. The driver relied on an MTU size being passed to it
but no value is passed in with the "-R" option.
2. The transmit and receive code paths in the driver needed
to be shortened in order to improve the efficiency in
processing small packets.
3. The promiscuous level of the unbound stream was not kept
independent of that of bound streams. If an unbound
stream enabled SAP promiscuous and a bound stream
enabled physical promiscuous, the driver could not
differentiate the two. Hence, it duplicated every
packet onto the unbound stream.
PHNE_14555:
1. A DMA read was attempted by a card with a PCI address
that had no corresponding address mapping. Problem was
only seen on 16-way V-class system with heavy SCSI
traffic. A race condition could occur. It caused
the card to read in a descriptor entry for a DMA
address before that entry became valid.
2. The word "wsio" was missing from the dependency section
in the master file.
3. The shared library, libdsfddi4.1, opened the catalog
file every time it was invoked, but did not close the
file when it was done. The command failed when the
number of files opened exceeded the "maxfiles" for a
process.
PHNE_13212:
Reproduced the similar symptom using an UDP performance tool
on a 4 way V-2200. With three copies of that tool running
together, the outbound traffic generated can overwhelm the
driver outbound routine and consequently lock out the ISR
routine both competing for the same lock. DMA timer pops
because the ISR does not get the chance to service transmit
completion interrupt within the timeout period.
PHNE_13184:
The function pointers used by LLA incorrectly pointed to
the wrong functions within PCI FDDI. These function
pointers have been changed to point to the function "nodev"
instead. This function will return the error ENODEV
when called.
It is to be noted that LLA has been obsoleted as of the
10.30 release of HP-UX and should not be used in 11.00.
SR:
8606227088 8606182683 8606156934 8606166638 8606168617
8606220085 8606257419 8606257686 8606263674 8606263677
8606104480 5003452128 8606107182 8606132729 8606132745
8606130913 8606139173 8606103306 8606103307 1653265173
5003428722 5003441279 5003441295 1653249847 4701374314
Patch Files:
FDDI-PCI.FDDI4-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.01,fa=HP-UX_B.11.00_64,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.02,fa=HP-UX_B.11.00_64,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.03,fa=HP-UX_B.11.00_64,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_64,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.08,fa=HP-UX_B.11.00_64,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.11,fa=HP-UX_B.11.00_64,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.12,fa=HP-UX_B.11.00_64,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.13,fa=HP-UX_B.11.00_64,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.15,fa=HP-UX_B.11.00_64,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.16,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libfddi4.a
/usr/conf/master.d/fddi4
FDDI-PCI.FDDI4-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_32,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.08,fa=HP-UX_B.11.00_32,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.11,fa=HP-UX_B.11.00_32,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.12,fa=HP-UX_B.11.00_32,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.13,fa=HP-UX_B.11.00_32,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.15,fa=HP-UX_B.11.00_32,v=HP:
FDDI-PCI.FDDI4-KRN,fr=B.11.00.16,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libfddi4.a
FDDI-PCI.FDDI4-RUN,fr=B.11.00.05,fa=HP-UX_B.11.00_32/64,
v=HP:
FDDI-PCI.FDDI4-RUN,fr=B.11.00.08,fa=HP-UX_B.11.00_32/64,
v=HP:
FDDI-PCI.FDDI4-RUN,fr=B.11.00.11,fa=HP-UX_B.11.00_32/64,
v=HP:
FDDI-PCI.FDDI4-RUN,fr=B.11.00.12,fa=HP-UX_B.11.00_32/64,
v=HP:
FDDI-PCI.FDDI4-RUN,fr=B.11.00.13,fa=HP-UX_B.11.00_32/64,
v=HP:
FDDI-PCI.FDDI4-RUN,fr=B.11.00.15,fa=HP-UX_B.11.00_32/64,
v=HP:
FDDI-PCI.FDDI4-RUN,fr=B.11.00.16,fa=HP-UX_B.11.00_32/64,
v=HP:
FDDI-PCI.FDDI4-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
FDDI-PCI.FDDI4-RUN,fr=B.11.00.01,fa=HP-UX_B.11.00_64,v=HP:
FDDI-PCI.FDDI4-RUN,fr=B.11.00.02,fa=HP-UX_B.11.00_64,v=HP:
FDDI-PCI.FDDI4-RUN,fr=B.11.00.03,fa=HP-UX_B.11.00_64,v=HP:
/usr/lib/lanadmin/libdsfddi4.1
/usr/sbin/fddipciadmin
/usr/lib/nls/msg/C/fddi4.cat
/usr/lib/libfddifmt4.1
/sbin/init.d/hppcifddi
/sbin/init.d/SnmpFddi4
/sbin/SnmpAgtStart.d/K424SnmpFddi4
/sbin/SnmpAgtStart.d/S576SnmpFddi4
/sbin/rc1.d/K424SnmpFddi4
/sbin/rc2.d/S576SnmpFddi4
/usr/sbin/hpfddi4_init
/usr/sbin/fddi4subagt
/usr/newconfig/etc/rc.config.d/hpfddi4conf
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.08,
fa=HP-UX_B.11.00_32/64,v=HP:
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.11,
fa=HP-UX_B.11.00_32/64,v=HP:
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.12,
fa=HP-UX_B.11.00_32/64,v=HP:
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.13,
fa=HP-UX_B.11.00_32/64,v=HP:
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.15,
fa=HP-UX_B.11.00_32/64,v=HP:
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.16,
fa=HP-UX_B.11.00_32/64,v=HP:
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/share/man/man1m.Z/fddipciadmin.1m
what(1) Output:
FDDI-PCI.FDDI4-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
/usr/conf/lib/libfddi4.a:
PCI FDDI: PHNE_26550: B.11.00.18 $Date: 2002/06/04 1
7:00:00 $
/usr/conf/master.d/fddi4:
None
FDDI-PCI.FDDI4-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_32,v=HP:
/usr/conf/lib/libfddi4.a:
PCI FDDI: PHNE_26550: B.11.00.18 $Date: 2002/06/04 1
7:00:00 $
FDDI-PCI.FDDI4-RUN,fr=B.11.00.05,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/lib/lanadmin/libdsfddi4.1:
dsfddi4.c: PHNE_26550: B.11.00.18 $Date: 2002/03/13
17:00:00 $
/usr/sbin/fddipciadmin:
HP PCI FDDI command: fddipciadmin, Release: B.11.00.
00
fddipciadmin.c: PHNE_26550: B.11.00.18 $Date: 2002/0
3/13 17:00:00$
/usr/lib/nls/msg/C/fddi4.cat:
None
/usr/lib/libfddifmt4.1:
subsys_FDDI_fmt4.c: PHNE_26550: B.11.00.18 $Date: 20
02/03/13 17:00:00 $
/sbin/init.d/hppcifddi:
None
/sbin/init.d/SnmpFddi4:
SnmpFddi4: PHNE_26550: B.11.00.18 $ $Date: 2002/03/1
3 17:00:00 $
/sbin/SnmpAgtStart.d/K424SnmpFddi4:
SnmpFddi4: PHNE_26550: B.11.00.18 $ $Date: 2002/03/1
3 17:00:00 $
/sbin/SnmpAgtStart.d/S576SnmpFddi4:
SnmpFddi4: PHNE_26550: B.11.00.18 $ $Date: 2002/03/1
3 17:00:00 $
/sbin/rc1.d/K424SnmpFddi4:
SnmpFddi4: PHNE_26550: B.11.00.18 $ $Date: 2002/03/1
3 17:00:00 $
/sbin/rc2.d/S576SnmpFddi4:
SnmpFddi4: PHNE_26550: B.11.00.18 $ $Date: 2002/03/1
3 17:00:00 $
/usr/sbin/hpfddi4_init:
None
/usr/sbin/fddi4subagt:
-DUNIX
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
HP PCI FDDI SNMP Subagent: fddi4subagt, Release: B.1
1.00.16
fddi4subagtd.c: PHNE_26550: B.11.00.18 $Date: 2002/0
3/13 17:00:00 $
-DUNIX
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_SNMPv2
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_SNMPv2
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE_LINES
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_SNMPv2
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE_LINES
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_SNMPv2
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE_LINES
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_SNMPv2
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_SNMPv2
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_SNMPv2
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_SNMPv2
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_SNMPv2
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_SNMPv2
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE_LINES
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_SNMPv2
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE_LINES
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_SNMPv2
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE_LINES
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_SNMPv2
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE_LINES
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_SNMPv2
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE_LINES
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_HPUX10
-DSR_BSD
-DHPUX
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_HPUX10
-DSR_BSD
-DHPUX
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
-DUNIX
-DSYSV
-DSR_SNMPv2
-DSR_SNMPv1
-DSR_HPUX10
-DSR_BSD
-DHPUX
-DEMANATE
Copyright 1992-1995 SNMP Research, Incorporated
SNMP Research Distribution version 12.3
$ -s Mar 13 2002 17:41:35 $
/usr/newconfig/etc/rc.config.d/hpfddi4conf:
None
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.08,
fa=HP-UX_B.11.00_32/64,v=HP:
/usr/share/man/man1m.Z/fddipciadmin.1m:
None
cksum(1) Output:
FDDI-PCI.FDDI4-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP:
2614659761 139064 /usr/conf/lib/libfddi4.a
3603701237 3779 /usr/conf/master.d/fddi4
FDDI-PCI.FDDI4-KRN,fr=B.11.00.05,fa=HP-UX_B.11.00_32,v=HP:
309953296 75344 /usr/conf/lib/libfddi4.a
FDDI-PCI.FDDI4-RUN,fr=B.11.00.05,fa=HP-UX_B.11.00_32/64,
v=HP:
2279026856 16384 /usr/lib/lanadmin/libdsfddi4.1
2152968053 49152 /usr/sbin/fddipciadmin
814246150 7892 /usr/lib/nls/msg/C/fddi4.cat
1250558422 12288 /usr/lib/libfddifmt4.1
2797490883 3534 /sbin/init.d/hppcifddi
1751563072 2581 /sbin/init.d/SnmpFddi4
1751563072 2581 /sbin/SnmpAgtStart.d/K424SnmpFddi4
1751563072 2581 /sbin/SnmpAgtStart.d/S576SnmpFddi4
1751563072 2581 /sbin/rc1.d/K424SnmpFddi4
1751563072 2581 /sbin/rc2.d/S576SnmpFddi4
3269604101 7466 /usr/sbin/hpfddi4_init
75158578 245760 /usr/sbin/fddi4subagt
399402431 1633 /usr/newconfig/etc/rc.config.d/hpfddi4conf
FDDI-PCI.FDAD-ENG-A-MAN,fr=B.11.00.08,
fa=HP-UX_B.11.00_32/64,v=HP:
1618959572 5120 /usr/share/man/man1m.Z/fddipciadmin.1m
Patch Conflicts: None
Patch Dependencies:
s700: 11.00: PHNE_19081
s800: 11.00: PHNE_19081
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_20874 PHNE_19542 PHNE_18524 PHNE_17517 PHNE_16689 PHNE_15670
PHNE_15269 PHNE_14555 PHNE_13212 PHNE_13184
Equivalent Patches: None
Patch Package Size: 650 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_26550
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_26550.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_26550. 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_26550.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_26550.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_26550.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
If lan common patch PHNE_19081 (or a superseding patch) is
not installed on a system with PCI FDDI, then installing
patch PHNE_19542 or a superseding patch (including this
patch) will :
- Not fix defect symptom #1 and #3 for PHNE_19542
- Symptom #2 for PHNE_19542 can never occur as
long as PHNE_19081 (or a superseding patch)
is not applied.
If lan common patch PHNE_19081 (or any superseding patch)
is installed on a system with PCI FDDI, then installing
patch PHNE_19542 or a superseding patch( including this
patch) will fix all 3 defects described in patch
PHNE_19542. Note that installing PHNE_19081 (or a
superseding patch) will expose defect #2 for PHNE_19542,
mentioned in the 'Symptoms' and 'Defect Description'
fields, which is fixed by patch PHNE_19542 and
superseding patches, including this patch.
A note about the fix for item #3 listed in the 'Symptoms'
field for patch PHNE_20874:
Starting with the application release of June 2000 (and
later releases), the product has a per-interface
configuration file located at
/usr/newconfig/etc/rc.config.d/hpfddi4conf. When the
product is installed from the application release of June
2000 or a later application release, the file
(hpfddi4conf) is automatically copied into
/etc/rc.config.d/hpfddi4conf, if the file does not already
exist in the destination directory. If the file
hpfddi4conf already exists under /etc/rc.config.d
directory it may not be overwritten by the newly delivered
file under /usr/newconfig/etc/rc.config.d/ directory as it
may contain changes made by the user. The user can then
merge the changes, if any into the file under
/etc/rc.config.d directory.
When patch PHNE_20874 (or a superseding patch) is
installed, the file hpfddi4conf is always delivered under
the /usr/newconfig/etc/rc.config.d directory and the user
is required to merge/copy changes, if any into the file
under /etc/rc.config.d directory.
The hpfddi4conf file allows per-interface configuration
information to be stored across boots and automatic
initialization of of interfaces using these per-interface
parameters during system boot by the product start-up
script (/sbin/init.d/hppcifddi). The following variables
are now configurable in the hpfddi4conf file on a
per-interface basis:
HP_PCIFDDI_INTERFACE_NAME: Name of interface (lan0,
lan1 ..., lan10, ...) i.e. any lanX, where X is the
instance number of the interface being configured.
HP_PCIFDDI_STATION_ADDRESS: The desired unicast
hardware address (station address) of the interface. This
value must be '0x' followed by 12 hexadecimal digits (i.e.
0x080009xxxxxx).
HP_PCIFDDI_MTU: Maximum transmission unit (in bytes)
for the interface. A value in the range 257-4352 is
valid.
HP_PCIFDDI_TREQ: The FDDI station's T_Req value in
milli-seconds. A value in the range 4-165 is valid.
HP_PCIFDDI_TNOTIFY: The FDDI station's T_Notify value
in seconds. A value in the range 2-30 seconds is valid.
-----End of Document ID: PHNE_26550------------------------------------------
Document ID: PHCO_26813
Date Loaded: 20020711
Title: s700_800 11.00 cumulative patch for syslogd(1M)
Patch Name: PHCO_26813
Patch Description: s700_800 11.00 cumulative patch for syslogd(1M)
Creation Date: 02/06/21
Post Date: 02/07/11
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
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=HP
ProgSupport.PAUX-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/PHCO_26813
Symptoms:
PHCO_26813:
1. PHCO_22673 breaks syslogd's -a option.
2. syslogd -v option introduced in PHCO_22673
is not documented.
PHCO_24448:
1. syslog.3c man page does not have thread-safe
informations.
PHCO_22673:
1. syslogd(1M) does not provide an option to log
priority and facility information.
2. syslogd does not support Unix domain socket
/dev/log.un.
PHCO_21023:
1. New options added to syslogd.
a. do not suppress duplicate messages.
b. do not listen to the syslog socket.
2. syslogd reorders log messages.
PHCO_17252:
1. syslogd incorrectly removes /var/run/syslog.pid
file.
2. Whenever any error in sendto(2) ,syslogd stops
forwarding messages.
3. syslogd reports error when messages are sent with
the facilities CRON ,UUCP and NEWS.
Defect Description:
PHCO_26813:
1. PHCO_22673 breaks syslogd's -a option. With PHCO_
22673 installed, syslogd(1M) expects an argument
when invoked with '-a' option and if no argument
is specified, exits with usage message.
e.g :
Before installation of PHCO_22673 :
-------------------------------------------------
$ /usr/sbin/syslogd -D -a
$
-------------------------------------------------
After installation of PHCO_22673 :
--------------------------------------------------
$ /usr/sbin/syslogd -D -a
/usr/sbin/syslogd: option requires an argument --a
usage: syslogd [-a] [-d] [-D] [-m markinterval]
[-p path] [-f conffile] [-r] [-N]
--------------------------------------------------
Resolution:
The optstring passed to getopt(3C) is corrected
so that it doesnot expect an argument with '-a'
option.
2. syslogd -v option introduced in PHCO_22673 is
not documented.
e.g :
-----------------------------------------------
$ /usr/sbin/syslogd junk
usage: syslogd [-a] [-d] [-D] [-m markinterval]
[-p path] [-f conffile] [-r] [-N]
-----------------------------------------------
Resolution:
The code is modified to show the -v option in
its usage message. Also the man-page has been
modified to reflect the same.
PHCO_24448:
1. syslog.3c man page does not have thread-safe
informations.
Resolution:
syslog.3c man page is replaced with latest one.
PHCO_22673:
1. syslog(3C) supports "Priority and Facility"
information, but syslogd(1M) doesn't support
logging the same "Priority and Facility" in
the specified log file.
Resolution:
Now, we are providing this facility to HP-UX system
without disturbing the current existing behavior of
HP-UX system. Introduced "-v" option to support the
priority and facility information. This is not
mandatory, only interested user can log this "Priority
and Facility" along with syslogd message. By Default
"Priority and Facility" will not be logged with syslogd
message.
2. syslogd does not support Unix domain socket on
/dev/log.un.
Resolution:
Code is changed to support Unix domain socket on
/dev/log.un.
PHCO_21023:
1. Syslogd does not have options to allow it to:
a. listen on the syslog port
b. supress duplicate messages.
Resolution:
Added two new options ('r','N').
'r' : Option to not suppressing duplicate messages.
'N' : Option to not listen to the syslog socket.
2. Syslogd reorders messages because of enhancement
added for "suppressing duplicate logging messages".
Resolution:
A new message "-a" has been added to syslogd to take
care of reordering.
With "-a" option, the old behavior of syslogd
is restored.
PHCO_17252:
1. syslogd incorrectly removes /var/run/syslog.pid
file. This happens every time alert message is
sent to syslogd daemon.
Resolution:
Call to unlink() is removed when alert message
comes.
2. Syslogd closes the socket descriptor whenever
sendto(2) returns with an error. This causes
syslogd to stop forwarding messages.
Resolution:
Syslogd is now changed to log an error message
if the call to sendto(2) returns an errno of
EHOSTUNREACH and to not close the socket.
3. The facilities for CRON ,NEWS and UUCP are not
supported by syslogd(1M).
Resolution:
The NEWS, UUCP, and CRON facilities are now
supported.
SR:
8606241692 8606241693 8606203524 8606165810 8606135842
8606105662 8606129858 1653275719 1653230524 5003408146
Patch Files:
OS-Core.CORE-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/share/man/man1m.Z/syslogd.1m
OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/sbin/syslogd
/sbin/init.d/syslogd
/etc/rc.config.d/syslogd
ProgSupport.PAUX-ENG-A-MAN,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
/usr/share/man/man3.Z/syslog.3c
what(1) Output:
OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/sbin/syslogd:
$Revision: 82.3.1.10 $
Copyright (c) 1983 Regents of the University of Cali
fornia.
PATCH_11_00: syslogd.o 02/06/21
OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/sbin/init.d/syslogd:
$Revision: 72.12.2.1 $
OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/etc/rc.config.d/syslogd:
None
OS-Core.CORE-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/share/man/man1m.Z/syslogd.1m:
None
ProgSupport.PAUX-ENG-A-MAN,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
/usr/share/man/man3.Z/syslog.3c:
None
cksum(1) Output:
OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
3744838562 36864 /usr/sbin/syslogd
OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
2151570664 3137 /sbin/init.d/syslogd
OS-Core.UX-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
4170738502 406 /etc/rc.config.d/syslogd
OS-Core.CORE-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
690956418 4148 /usr/share/man/man1m.Z/syslogd.1m
ProgSupport.PAUX-ENG-A-MAN,fr=B.11.00,
fa=HP-UX_B.11.00_32/64,v=HP:
2462466553 4331 /usr/share/man/man3.Z/syslog.3c
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHCO_17252 PHCO_21023 PHCO_22673 PHCO_24448
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 PHCO_26813
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_26813.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_26813. 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_26813.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_26813.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_26813.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_26813------------------------------------------
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]