|
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 Sep 08 2002 - 15:42:53 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 Sep 8 3:05:38 PDT 2002
Table of Contents:
Document ID Title
--------------- -----------
PHKL_27554 s700_800 11.11 VxFS cumulative patch : VxFS 3-way deadlock
PHCO_27434 s700_800 11.11 libc cumulative patch
PHCO_25918 s700_800 11.11 sort(1) cumulative patch
PHSS_27784 s700_800 11.00 OV NNM6.1 http server fix
PHSS_27700 s700_800 11.11 CPSlib Cumulative Patch (OMP V2.0 for 11.11)
PHSS_27699 s700_800 11.X CPSlib Cumulative Patch (OMP V2.0 for 11.x)
PHSS_27680 s700_800 11.X OpenMail B.07.00 September 02 Periodic Patch
PHSS_27678 s700_800 11.X OpenMail B.06.00 September 02 Periodic Patch
PHSS_27557 s700_800 11.22 MC/ServiceGuard A.11.14.01
PHSS_27471 s700_800 11.22 FORTRAN I/O Library [libIO77]
PHSS_27453 s700_800 11.X OV OB4.10 patch - SAP packet
PHKL_27648 s700_800 11.00 VxFS cumulative,I/O Throttling/sync daemon
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHKL_27554
Date Loaded: 20020906
Title: s700_800 11.11 VxFS cumulative patch : VxFS 3-way deadlock
Patch Name: PHKL_27554
Patch Description: s700_800 11.11 VxFS cumulative patch : VxFS 3-way deadlock
Creation Date: 02/08/13
Post Date: 02/09/06
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_27554: HANG
PHKL_23374: CORRUPTION
PHKL_25022: HANG
PHKL_23241: PANIC HANG
PHKL_25463: HANG
Category Tags:
defect_repair enhancement general_release critical panic
halts_system corruption manual_dependencies
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_27554
Symptoms:
PHKL_27554:
( SR:8606262053 CR:JAGae26384 )
Filesystems commands that freeze filesystems (such as
fsadm resize) may deadlock with processes that use
F_WRLCK ioctl() to place locks on files in the filesystem.
A stack trace of the hung command will look similar to the
following:
_sleep+0x210
sleep_spinunlock+0x70
vx_event_wait+0xc0
vx_delay2+0x64
vx_freeze_level+0x278
vx_freeze+0x3c
vx_resize+0x120
vx_aioctl_full+0xf8
vx_aioctl_common+0x3b4
vx_aioctl+0xbc
vx_ioctl+0xc0
vno_ioctl+0x98
ioctl+0x120
syscall+0x750
$syscallrtn+0x0
Meanwhile, other threads will be sleeping with a stack trace
similar to the following:
_swtch+0xc4
_sleep+0x4cc
locked+0xd84
vx_rdwr+0x234
vno_rw+0x80
read+0x10c
syscall+0x204
$syscallrtn+0x0
_sleep+0x210
sleep_spinunlock+0x70
vx_event_wait+0xc0
vx_delay2+0x64
vx_active_common_flush+0xb8
vx_lockctl+0x3c
fcntl+0x2d4
syscall+0x750
$syscallrtn+0x0
PHKL_27121:
( SR:8606244250 CR:JAGae10740 )
After a file has been created with 000 permissions in a
directory with one or more default entries in its
Access Control List (ACL, see aclv(5)) on a VxFS
filesystem using the version 4 layout, all files created
in that directory will be created with 000 permissions
until the filesystem that directory is in is unmounted
and remounted, or the system is rebooted. The file which
initiated this condition need not have 000 permissions
at the end of the process that started its creation.
For example, if a file is copied into this directory
using cp(1), this condition will be triggered. cp(1)
first creates a file with 000 permissions, and then sets
the permissions as appropriate, using the permissions of
the copied file combined with the user's umask and the
parent directory's permission mask, which is based upon
the directory's default ACLs. Following this, some
commands such as cp(1) and mv(1) will behave as
documented since they explicitly set the permissions of
their target files, but others, such as touch(1) will
create files with 000 permissions since they do not
explicitly set the permissions of their targets, but
instead only use the user's umask and the parent
directory's mask. The permissions of affected files
can be corrected with chmod(1).
PHKL_26230:
( SR:8606224092 CR:JAGad93188 )
PHKL_25022 introduced behavior that can cause VxFS 3.3 file
system performance problems when sequential I/O requests of
less than 64KB are performed. This behavior can affect
backup utilities and other applications that perform
sequential I/O accesses to the file system.
PHKL_25885:
( SR:8606235772 CR:JAGae04912 )
Cannot deactivate a Volume Group that has at least one
VxFS file system, no mounted logical volumes, and no one
accessing any of the logical volumes in that VG:
# vgchange -a n /dev/vgtest
vgchange: Couldn't deactivate volume group "/dev/vgtest":
Device busy
( SR:8606221614 CR:JAGad90748 )
Access to a VxFS file system may hang when trying to
flush the intent log. A kernel stack trace of a hung
process will look similar to the following, and there
will be no process in vx_tranflush():
_sleep+0xa5c
sleep_spinunlock+0x70
vx_event_wait+0xc0
vx_delay2+0x64
vx_traninit+0x3d0
vx_write_alloc+0xc8
vx_write1+0x464
vx_rdwr+0x1e4
vno_rw+0x80
write+0x108
syscall+0x750
( SR:8606233921 CR:JAGae03144 )
VxFS performance may be slow when flushing the intent
log during intense file system modifications.
( SR:8606222925 CR:JAGad92031 )
VxFS performance may be slow when there is significant
write activity to the VxFS intent log.
PHKL_23374:
( SR:8606172239 CR:JAGad41499 )
close(2) may cause data corruption by truncating VxFS files.
PHKL_25022:
( SR:8606202113 CR:JAGad71287 )
VxFS may hang a 64 bit system by zeroing out the
interrupt mask (cr15).
( SR:8606198445 CR:JAGad67635 )
Applications invoking system calls fcntl(2) or lockf(2) may
deadlock with applications invoking system calls
truncate(2), ftruncate(2) or creat(2). An example of stack
traces of deadlocked threads is given below.
_sleep+0xa5c
sleep_spinunlock+0x70
vx_rwsleep_rec_lock_rec+0x90
vx_irwlock2_rec+0x3c
vx_getattr2+0x1b0
vx_getattr+0x58
enforcement_mode+0x48
locked+0x78
local_lockf+0xec
lockf+0x244
syscall+0xaec
syscallinit+0x554
_swtch+0x2d4
_mp_b_sema_sleep+0x108
vm_mmf_inval_lock+0x18
vx_setattr+0x304
vns_copen+0xc0
vn_open+0xb4
copen+0xa8
creat+0x44
syscall+0xaec
syscallinit+0x554
( SR:8606200313 CR:JAGad69497 )
Poor performance with VxFS compared to HP-UX 11.00 VxFS 3.1
while multiple threads/processes read from a file
simultaneously.
( SR:8606203915 CR:JAGad73093 )
PHKL_23240 introduced behavior that can cause multiple
threads to deadlock on a specific file. The behavior only
occurs if the file is being flushed at the same time it is
being remotely accessed, such as via NFS or other networking
access. The behavior could eventually lead to hung
processes and subsystems, such as NFS. This problem happens
only if VxFS fancy read ahead is turned on. Stacks of
deadlocked threads may look like as shown below.
_sleep+0x1fc
sleep_spinunlock+0x74
vx_event_wait+0xf0
vx_delay2+0x64
vx_vnode_flush+0x3bc
vx_do_putpage+0x11c
vx_idelxwri_flush+0xf8
vx_delxwri_flush+0x1dc
vx_worklist_process+0x1b0
vx_worklist_thread+0x4c
kthread_daemon_startup+0x24
_sleep+0x1fc
vx_rwsleep_lock+0x1f4
vx_iglock2+0x78
vx_iglock+0x28
vx_fancy_read_ahead+0x1c4
vx_read1+0x980
vx_vn_bread+0xfc
rfs_read+0x158
rfsexp_dispatch+0x210
svc_getreq+0x13c
svc_run+0x1e0
nfsexp_svc+0x4d4
nfs_stub_svc+0xa4
coerce_scall_args+0xcc
syscall+0x6f8
syscallinit+0x54c
PHKL_23241:
( SR:8606179185 CR:JAGad48409 )
Poor application performance with VxFS compared to VxFS 3.1
(default version of VxFS on HP-UX 11.00) when the
application does a lot of reads from random offsets of a
file.
( SR:8606183708 CR:JAGad52921 )
Data Page Fault while using Hyperfabric network. Stack of
the panic thread may look like,
panic+0x14
report_trap_or_int_and_panic+0x84
interrupt+0x1d4
$ihndlr_rtn+0x0
sendfile_rele+0x304
freeb_pullupmsg+0x238
freeb+0x7b4
CLIC_SEND+0x1ecc
clicdlpi_wput+0x140
putnext+0xcc
ip_wput_ire+0x454
ip_wput+0x470
putnext+0xcc
tcp_timer+0x334
tcp_wput+0x828
puthere+0x148
mi_timeout_exec+0x294
sw_service+0xb0
mp_ext_interrupt+0x150
ivti_patch_to_nop3+0x0
idle+0x81c
( SR:8606178276 CR:JAGad47503 )
System hang caused by a thread going through the buffer pool
to flush out dirty buffers. A buffer is marked dirty but
also marked busy, and the process or thread decides to wait
for it. Because of this, ServiceGuard commands such as
cmapplyconf and cmcheckconf hang. A typical stack of the
hung thread is given below.
_swtch+0x138
real_sleep+0x234
_sleep+0x14
syncip_flush_cache+0x190
vx_flushdev+0x10
vx_fsync+0x1cc
spec_fsync+0x17c
spec_inactive+0x14
vn_rele+0x1e8
vno_close+0x68
closef+0x68
close+0x30
syscall+0x75c
$syscallrtn+0x0
( SR:8606188296 CR:JAGad57504 )
Backup utilities such as fbackup take longer to finish
when JFS fancy read ahead is enabled, i.e., when
vx_fancyra_enable is set to a non-zero value in the system
file.
( SR:8606181938 CR:JAGad51154 )
Data Page Fault in allocbuf1(). Stack of the panic thread
may look like,
allocbuf1+0xd0
allocbuf+0x30
vx_allocbuf+0x30
vx_async_shorten+0xc30
vx_fsync+0x120
rfs3_commit+0x3a0
rfsexp_dispatch+0x810
svc_getreq+0x500
svc_run+0x930
nfsexp_svc+0x860
nfs_stub_svc+0x390
coerce_scall_args+0x570
syscall+0xe70
( SR:8606179211 CR:JAGad48435 )
sar -v and glance show ninode usage (count of active inodes
on the system) as 0.
PHKL_23240:
( SR:8606175335 CR:JAGad44577 )
Poor system performance with VxFS vs HFS, when applications
like Nastran and Abaqus, which read backward and forward
through a file which cannot be fully contained in the buffer
cache.
PHKL_25360:
( SR:8606209887 CR:JAGad79073 )
Poor vxfs mount performance on systems with large buffer
caches
PHKL_25463:
( SR:8606202670 CR:JAGad71844 )
High end systems may thrash when large number of threads
access a single VxFS filesystem. System may appear to be
hung.
Defect Description:
PHKL_27554:
( SR:8606262053 CR:JAGae26384 )
A thread trying to read a file is allowed to sleep
waiting for the read/write lock owned by another
thread while the filesystem active count is incremented.
The hang occurs when another thread tries to freeze the
filesystem before the read/write lock can be released,
and hangs in vx_freeze_level(). When the thread tries
to release the read/write lock, it hangs in
vx_active_common_flush() due to the pending freeze.
Resolution:
The active count is now decremented before calling locked()
and sleeping on the read/write lock. Once the lock is
obtained, the active count is incremented again.
PHKL_27121:
( SR:8606244250 CR:JAGae10740 )
The mode of a newly created file on a VxFS filesystem
using the version 4 layout (see vxupgrade(1M)) is
determined by the mode passed into open(2) or creat(2)
combined with the user's umask and the modemask of a
directory, determined by its default ACLs. When default
ACLs exist, the modemask of the directory would be set to
the mode passed into open(2) or creat(2). From the time
when a file is created with mode 000 on, all subsequently
created files in that directory with default ACLs would be
given 000 permissions.
Resolution:
The modemasks of directories are no longer affected by the
modes of created files.
PHKL_26230:
( SR:8606224092 CR:JAGad93188 )
The readahead algorithm was incorrectly using
max_buf_data_size (default 8Kb) to calculate the readahead
size instead of read_pref_io (default 64kb)
which resulted in a smaller readahead size.
Resolution:
Use read_pref_io to calculate the readahead size.
PHKL_25885:
( SR:8606235772 CR:JAGae04912 )
A failed VxFS mount leaves the device opened.
Resolution:
Ensure device is closed when a VxFS mount fails.
( SR:8606221614 CR:JAGad90748 )
During the flushing of a transaction, a condition
occurred such that the transaction needed to be
retried, but was not. Since the transaction was
never flushed, the intent log fills up and access
to the file system hangs.
Resolution:
Assure proper retry of transactions under all
conditions.
( SR:8606233921 CR:JAGae03144 )
VxFS intent log processing is done using 1K buffers.
Resolution:
Allow larger I/O's when flushing the intent log by
introducing a new logiosize mount option. For
example:
mount -F vxfs -o logiosize=4096
Valid values for logiosize are 1024, 2048, and 4096.
( SR:8606222925 CR:JAGad92031 )
VxFS fails to detect that the intent log is filling
up.
Resolution:
Changed internal VxFS threshold values used to detect
how full the log is to lower values to allow earlier
detection that the log is filling up.
PHKL_23374:
( SR:8606172239 CR:JAGad41499 )
While closing (close(2)) a file, VxFS tried to free up extra
space (extents) allocated to the file. While doing this, it
incorrectly modified the actual file size, causing data
loss.
Resolution:
Corrected logic to prevent modification of file size while
freeing extra extents.
PHKL_25022:
( SR:8606202113 CR:JAGad71287 )
VxFS was using a wrong data type (unsigned int) with
spinlock functions. Spinlock functions use "unsigned long".
Resolution:
Use the correct data type (unsigned long) with spinlock
functions.
( SR:8606198445 CR:JAGad67635 )
A lock was acquired in the wrong order in a VxFS function
invoked by system calls fcntl(2) and lockf(2).
Resolution:
Eliminated the cases where the lock was acquired in the
wrong order.
( SR:8606200313 CR:JAGad69497 )
1. VxFS read ahead code relies on the unexpected read
(buffer cache miss) count to determine if there is any
pressure on buffer cache. If there is pressure on buffer
cache, the amount of read ahead performed is reduced. If
the read ahead performed is less than the size of the read
size, there will be unexpected reads. This turns out into a
self fulfilling prophecy and read ahead is completely turned
off causing each read to read the data from the disk
synchronously degrading performance.
2. VxFS uses the vxtunefs(1M) tunable "read_pref_io"
to calculate the intial and maximum read ahead region
length. But the read sizes could vary and this tunable may
not trigger enough read ahead for different read sizes.
Resolution:
1. Use the current read request size as the floor for the
read ahead region length.
2. Use the current read request size times the vxtunefs(1M)
"read_nstream" as the ceiling for the read ahead region
length.
( SR:8606203915 CR:JAGad73093 )
VxFS read code was acquiring two locks in the wrong
order causing deadlock.
Resolution:
VxFS read code is rewritten eliminating the need to
acquire the locks in the wrong order.
PHKL_23241:
( SR:8606179185 CR:JAGad48409 )
A sanity check at the wrong place in a function disabled
read ahead for random reads to a file.
Resolution:
Move the sanity check to the correct place in the function
so that some read ahead can be done for random reads.
( SR:8606183708 CR:JAGad52921 )
VxFS may free a vnode while a buffer associated with that
vnode is in use in sendfile(2). Later when the sendfile
code accesses the vnode through the buffer, the system
panics.
Resolution:
Set up a dummy vnode which is not freed and use that vnode
for buffers passed to sendfile(2) so that sendfile(2)
code will always be accessing a valid vnode.
( SR:8606178276 CR:JAGad47503 )
In some corner cases, some VxFS meta buffers (map buffers)
will be left in a busy and dirty state. This leads to a
process hang for any process which is directly or indirectly
doing a buffer cache flush.
Resolution:
Make sure the VxFS meta buffers are flushed before doing
a buffer cache flush.
( SR:8606188296 CR:JAGad57504 )
The VxFS fancy read ahead feature degrades read performance
when multiple process/threads read from a file
simultaneously. Because the VxFS fancy read ahead feature
was designed to handle only one reader for a file at a
time, when there are multiple readers for a file its read
ahead pattern matching algorithm fails. This results in
many unnecessary I/Os.
Resolution:
When there are multiple readers to a file, disable fancy
read and do sequential read ahead instead.
( SR:8606181938 CR:JAGad51154 )
allocbuf1() expects a non-zero value as its second
argument, but VxFS was not always passing a non-zero
value.
Resolution:
Make sure that a non-zero value is always passed as the
second argument to allocbuf1() from VxFS code.
( SR:8606179211 CR:JAGad48435 )
VxFS was decrementing the number of active inode count
instead of incrementing it when inodes became active.
Resolution:
Increment active inode count when inodes become active.
PHKL_23240:
( SR:8606175335 CR:JAGad44577 )
An incorrect sanity check in the VxFS read path turned off
both normal read ahead and fancy read ahead when the fancy
read ahead was enabled on the system. This caused large I/O
wait times for each read.
Resolution:
Corrected the logic error in the sanity check code such that
fancy read ahead is used when enabled.
PHKL_25360:
( SR:8606209887 CR:JAGad79073 )
VXFS mount(2) performance varies depending on the size of
the buffer cache but can be poor for systems with large
buffer caches. The majority of the time is spent in
flushing/invalidation routines which search all buffer
headers then search all hash buckets respectively at VXFS
file system initialization. These flushing/invalidation
routines should not be required since no data should reside
in the buffer cache for the device being mounted.
Resolution:
To reduce the mount time aforementioned,
flushing/invalidation calls are removed.
PHKL_25463:
( SR:8606202670 CR:JAGad71844 )
VxFS logs each operation on the filesystem. When a thread
cannot find free space in the log, it sleeps 2 seconds and
tries again.
The problem arises when there is a large number of threads
operating on the filesystem causing the log to be full most
of the time. All these threads sleep 2 seconds and then
check the log space. This causes the system to thrash
keeping the processors busy all the time. The threads which
are supposed to free up the log space can never do that.
Resolution:
Increase the sleeping time of the threads in each iteration
instead of sleeping 2 seconds always.
SR:
8606172239 8606175335 8606178276 8606179185 8606179211
8606181938 8606183708 8606188296 8606198445 8606200313
8606202113 8606202670 8606203915 8606209887 8606221614
8606222925 8606224092 8606233921 8606235772 8606244250
8606262053
Patch Files:
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvxfs.a(vx_acl.o)
/usr/conf/lib/libvxfs.a(vx_ausum.o)
/usr/conf/lib/libvxfs.a(vx_bio.o)
/usr/conf/lib/libvxfs.a(vx_bitmaps.o)
/usr/conf/lib/libvxfs.a(vx_freeze.o)
/usr/conf/lib/libvxfs.a(vx_full.o)
/usr/conf/lib/libvxfs.a(vx_iflush.o)
/usr/conf/lib/libvxfs.a(vx_inode.o)
/usr/conf/lib/libvxfs.a(vx_kdmi.o)
/usr/conf/lib/libvxfs.a(vx_kdmi_machdep.o)
/usr/conf/lib/libvxfs.a(vx_lct.o)
/usr/conf/lib/libvxfs.a(vx_lwrite.o)
/usr/conf/lib/libvxfs.a(vx_machdep.o)
/usr/conf/lib/libvxfs.a(vx_message.o)
/usr/conf/lib/libvxfs.a(vx_mount.o)
/usr/conf/lib/libvxfs.a(vx_oltmount.o)
/usr/conf/lib/libvxfs.a(vx_rdwri.o)
/usr/conf/lib/libvxfs.a(vx_tran.o)
/usr/conf/lib/libvxfs.a(vx_vfsops.o)
/usr/conf/lib/libvxfs.a(vx_vnops.o)
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvxfs.a(vx_acl.o)
/usr/conf/lib/libvxfs.a(vx_ausum.o)
/usr/conf/lib/libvxfs.a(vx_bio.o)
/usr/conf/lib/libvxfs.a(vx_bitmaps.o)
/usr/conf/lib/libvxfs.a(vx_freeze.o)
/usr/conf/lib/libvxfs.a(vx_full.o)
/usr/conf/lib/libvxfs.a(vx_iflush.o)
/usr/conf/lib/libvxfs.a(vx_inode.o)
/usr/conf/lib/libvxfs.a(vx_kdmi.o)
/usr/conf/lib/libvxfs.a(vx_kdmi_machdep.o)
/usr/conf/lib/libvxfs.a(vx_lct.o)
/usr/conf/lib/libvxfs.a(vx_lwrite.o)
/usr/conf/lib/libvxfs.a(vx_machdep.o)
/usr/conf/lib/libvxfs.a(vx_message.o)
/usr/conf/lib/libvxfs.a(vx_mount.o)
/usr/conf/lib/libvxfs.a(vx_oltmount.o)
/usr/conf/lib/libvxfs.a(vx_rdwri.o)
/usr/conf/lib/libvxfs.a(vx_tran.o)
/usr/conf/lib/libvxfs.a(vx_vfsops.o)
/usr/conf/lib/libvxfs.a(vx_vnops.o)
what(1) Output:
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvxfs.a(vx_acl.o):
vx_acl.c $Date: 2002/05/16 14:11:52 $Revision: r11.1
1/2 PATCH_11.11 (PHKL_27121)
/usr/conf/lib/libvxfs.a(vx_ausum.o):
vx_ausum.c $Date: 2002/04/19 05:55:51 $Revision: r11
.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_bio.o):
vx_bio.c $Date: 2002/04/19 05:56:22 $Revision: r11.1
1/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_bitmaps.o):
vx_bitmaps.c $Date: 2002/04/19 05:56:53 $Revision: r
11.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_freeze.o):
vx_freeze.c $Date: 2002/04/19 05:57:23 $Revision: r1
1.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_full.o):
vx_full.c $Date: 2002/04/19 05:58:26 $Revision: r11.
11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_iflush.o):
vx_iflush.c $Date: 2001/08/27 08:06:20 $Revision: r1
1.11/3 PATCH_11.11 (PHKL_25022)
/usr/conf/lib/libvxfs.a(vx_inode.o):
vx_inode.c $Date: 2002/04/19 05:58:56 $Revision: r11
.11/5 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_kdmi.o):
vx_kdmi.c $Date: 2001/08/27 08:06:20 $Revision: r11.
11/1 PATCH_11.11 (PHKL_25022)
/usr/conf/lib/libvxfs.a(vx_kdmi_machdep.o):
vx_kdmi_machdep.c $Date: 2001/08/27 08:06:20 $Revisi
on: r11.11/1 PATCH_11.11 (PHKL_25022)
/usr/conf/lib/libvxfs.a(vx_lct.o):
vx_lct.c $Date: 2002/04/19 05:59:25 $Revision: r11.1
1/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_lwrite.o):
vx_lwrite.c $Date: 2002/04/19 05:59:56 $Revision: r1
1.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_machdep.o):
vx_machdep.c $Date: 2002/04/19 06:00:28 $Revision: r
11.11/3 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_message.o):
vx_message.c $Date: 2002/04/19 06:01:28 $Revision: r
11.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_mount.o):
vx_mount.c $Date: 2002/04/19 06:02:00 $Revision: r11
.11/4 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_oltmount.o):
vx_oltmount.c $Date: 2002/04/19 06:02:33 $Revision:
r11.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_rdwri.o):
vx_rdwri.c $Date: 2002/03/12 09:00:57 $Revision: r11
.11/4 PATCH_11.11 (PHKL_26230)
/usr/conf/lib/libvxfs.a(vx_tran.o):
vx_tran.c $Date: 2002/04/19 06:03:34 $Revision: r11.
11/3 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_vfsops.o):
vx_vfsops.c $Date: 2002/04/19 06:04:51 $Revision: r1
1.11/3 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_vnops.o):
vx_vnops.c $Date: 2002/07/22 08:08:47 $Revision: r11
.11/4 PATCH_11.11 (PHKL_27554)
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvxfs.a(vx_acl.o):
vx_acl.c $Date: 2002/05/16 14:11:52 $Revision: r11.1
1/2 PATCH_11.11 (PHKL_27121)
/usr/conf/lib/libvxfs.a(vx_ausum.o):
vx_ausum.c $Date: 2002/04/19 05:55:51 $Revision: r11
.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_bio.o):
vx_bio.c $Date: 2002/04/19 05:56:22 $Revision: r11.1
1/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_bitmaps.o):
vx_bitmaps.c $Date: 2002/04/19 05:56:53 $Revision: r
11.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_freeze.o):
vx_freeze.c $Date: 2002/04/19 05:57:23 $Revision: r1
1.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_full.o):
vx_full.c $Date: 2002/04/19 05:58:26 $Revision: r11.
11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_iflush.o):
vx_iflush.c $Date: 2001/08/27 08:06:20 $Revision: r1
1.11/3 PATCH_11.11 (PHKL_25022)
/usr/conf/lib/libvxfs.a(vx_inode.o):
vx_inode.c $Date: 2002/04/19 05:58:56 $Revision: r11
.11/5 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_kdmi.o):
vx_kdmi.c $Date: 2001/08/27 08:06:20 $Revision: r11.
11/1 PATCH_11.11 (PHKL_25022)
/usr/conf/lib/libvxfs.a(vx_kdmi_machdep.o):
vx_kdmi_machdep.c $Date: 2001/08/27 08:06:20 $Revisi
on: r11.11/1 PATCH_11.11 (PHKL_25022)
/usr/conf/lib/libvxfs.a(vx_lct.o):
vx_lct.c $Date: 2002/04/19 05:59:25 $Revision: r11.1
1/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_lwrite.o):
vx_lwrite.c $Date: 2002/04/19 05:59:56 $Revision: r1
1.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_machdep.o):
vx_machdep.c $Date: 2002/04/19 06:00:28 $Revision: r
11.11/3 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_message.o):
vx_message.c $Date: 2002/04/19 06:01:28 $Revision: r
11.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_mount.o):
vx_mount.c $Date: 2002/04/19 06:02:00 $Revision: r11
.11/4 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_oltmount.o):
vx_oltmount.c $Date: 2002/04/19 06:02:33 $Revision:
r11.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_rdwri.o):
vx_rdwri.c $Date: 2002/03/12 09:00:57 $Revision: r11
.11/4 PATCH_11.11 (PHKL_26230)
/usr/conf/lib/libvxfs.a(vx_tran.o):
vx_tran.c $Date: 2002/04/19 06:03:34 $Revision: r11.
11/3 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_vfsops.o):
vx_vfsops.c $Date: 2002/04/19 06:04:51 $Revision: r1
1.11/3 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_vnops.o):
vx_vnops.c $Date: 2002/07/22 08:08:47 $Revision: r11
.11/4 PATCH_11.11 (PHKL_27554)
cksum(1) Output:
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
3796376312 9504 /usr/conf/lib/libvxfs.a(vx_acl.o)
4198481589 10884 /usr/conf/lib/libvxfs.a(vx_ausum.o)
3260025450 14916 /usr/conf/lib/libvxfs.a(vx_bio.o)
1248921268 12728 /usr/conf/lib/libvxfs.a(vx_bitmaps.o)
2996258241 12376 /usr/conf/lib/libvxfs.a(vx_freeze.o)
1628969365 18128 /usr/conf/lib/libvxfs.a(vx_full.o)
3710207933 33576 /usr/conf/lib/libvxfs.a(vx_iflush.o)
3557505618 49836 /usr/conf/lib/libvxfs.a(vx_inode.o)
2641816605 24496 /usr/conf/lib/libvxfs.a(vx_kdmi.o)
218590132 7240 /usr/conf/lib/libvxfs.a(vx_kdmi_machdep.o)
3283460305 8480 /usr/conf/lib/libvxfs.a(vx_lct.o)
257345748 17592 /usr/conf/lib/libvxfs.a(vx_lwrite.o)
416780096 28572 /usr/conf/lib/libvxfs.a(vx_machdep.o)
27714084 8180 /usr/conf/lib/libvxfs.a(vx_message.o)
573507680 31320 /usr/conf/lib/libvxfs.a(vx_mount.o)
1596827858 32180 /usr/conf/lib/libvxfs.a(vx_oltmount.o)
2949381949 41836 /usr/conf/lib/libvxfs.a(vx_rdwri.o)
1260822277 23276 /usr/conf/lib/libvxfs.a(vx_tran.o)
2964603044 14052 /usr/conf/lib/libvxfs.a(vx_vfsops.o)
415591403 40072 /usr/conf/lib/libvxfs.a(vx_vnops.o)
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
295022246 18496 /usr/conf/lib/libvxfs.a(vx_acl.o)
286461698 24576 /usr/conf/lib/libvxfs.a(vx_ausum.o)
76588612 35272 /usr/conf/lib/libvxfs.a(vx_bio.o)
1476600098 30904 /usr/conf/lib/libvxfs.a(vx_bitmaps.o)
4156183916 30664 /usr/conf/lib/libvxfs.a(vx_freeze.o)
2369336865 33336 /usr/conf/lib/libvxfs.a(vx_full.o)
3028486132 81864 /usr/conf/lib/libvxfs.a(vx_iflush.o)
3050802657 117144 /usr/conf/lib/libvxfs.a(vx_inode.o)
3448801792 50720 /usr/conf/lib/libvxfs.a(vx_kdmi.o)
3454657473 12712 /usr/conf/lib/libvxfs.a(vx_kdmi_machdep.o)
3253867836 19240 /usr/conf/lib/libvxfs.a(vx_lct.o)
2561380258 29984 /usr/conf/lib/libvxfs.a(vx_lwrite.o)
1114219669 75336 /usr/conf/lib/libvxfs.a(vx_machdep.o)
2665699720 12784 /usr/conf/lib/libvxfs.a(vx_message.o)
1236102621 63904 /usr/conf/lib/libvxfs.a(vx_mount.o)
3710736912 54632 /usr/conf/lib/libvxfs.a(vx_oltmount.o)
3200443826 68136 /usr/conf/lib/libvxfs.a(vx_rdwri.o)
474714748 46080 /usr/conf/lib/libvxfs.a(vx_tran.o)
2650175339 30376 /usr/conf/lib/libvxfs.a(vx_vfsops.o)
1681280875 82304 /usr/conf/lib/libvxfs.a(vx_vnops.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies:
PHKL_25885: PHCO_26252 is needed to use logiosize=4096.
Supersedes:
PHKL_27121 PHKL_26230 PHKL_25885 PHKL_25463 PHKL_25360 PHKL_25022
PHKL_23374 PHKL_23241 PHKL_23240
Equivalent Patches: None
Patch Package Size: 1410 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_27554
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_27554.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_27554. 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_27554.text file is
available in the product readme:
swlist -l product -a readme -d 
/tmp/PHKL_27554.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_27554.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHKL_27554------------------------------------------
Document ID: PHCO_27434
Date Loaded: 20020906
Title: s700_800 11.11 libc cumulative patch
Patch Name: PHCO_27434
Patch Description: s700_800 11.11 libc cumulative patch
Creation Date: 02/09/04
Post Date: 02/09/06
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.C-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.C-MIN-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.CORE-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
OS-Core.CORE-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
ProgSupport.PROG-AUX,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
ProgSupport.PROG-AX-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
ProgSupport.PROG-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
Yes
PHCO_27434: HANG
Process Hang
PHCO_27910: ABORT CORRUPTION HANG
PHCO_26870: ABORT CORRUPTION HANG
PHCO_26124: ABORT CORRUPTION
PHCO_25452: ABORT HANG
PHCO_24942: ABORT CORRUPTION
PHCO_23427: CORRUPTION
PHCO_23772: CORRUPTION
PHCO_23093: CORRUPTION
Category Tags:
defect_repair enhancement general_release critical
halts_system corruption manual_dependencies
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_27434
Symptoms:
PHCO_27434:
( SR:8606258699 CR:JAGae23018 ) Duplicate
( SR:8606261751 CR:JAGae26070 ) Duplicate
( SR:8606265515 CR:JAGae29801 )
When using popen(3S) in different threads or
popen(3S) and fork(2) simultaneously in different
threads, the process may hang if it is using
pclose(3S) subsequently.
( SR:8606262841 CR:JAGae27171 )
strtod(3C) returns the wrong end pointer, when
the first argument is "infinity".
PHCO_27910:
( SR:8606260114 CR:JAGae24434 )
getipnodebyname() routine returns incorrect results in
multi-threaded environment when it is called with an
IP address as the argument.
( SR:8606239772 CR:JAGae08197 )
Either or both of the following symptoms may appear
on a given system.
1. Service Guard may experience umount(2) failures.
2. System throughput and/or response time may
degrade when SPUs are added to a configuration
that includes significant getcwd(3C) activity,
for example in the SDET benchmark.
( SR:8606257150 CR:JAGae21456 )
opendir(3C) performance may be slow.
( SR:8606254777 CR:JAGae19108 )
gethostbyname() routine returns incorrect results in
multi-threaded environment when it is called with an
IP address as the argument.
( SR:8606251497 CR:JAGae17562 )
32bit applications running on 64 bit kernel,which call
getresuid(3C) or getresgid(3C) may abort and dump core on
systems with greater than 2GB physical memory.
( SR:8606245321 CR:JAGae11794 )
inetd(1M) daemon may hang on 11.11 trusted systems.
Inetd services will not work until "inetd -b" is run twice.
PHCO_26870:
( SR:8606239772 CR:JAGae08197 )
Either or both of the following symptoms may appear
on a given system.
1. Service Guard may experience umount(2) failures.
2. System throughput and/or response time may
degrade when SPUs are added to a configuration
that includes significant getcwd(3C) activity,
for example in the SDET benchmark.
( SR:8606260114 CR:JAGae24434 )
getipnodebyname() routine returns incorrect results in
multi-threaded environment when it is called with an
IP address as the argument.
( SR:8606257150 CR:JAGae21456 )
opendir(3C) performance may be slow.
( SR:8606254777 CR:JAGae19108 )
gethostbyname() routine returns incorrect results in
multi-threaded environment when it is called with an
IP address as the argument.
( SR:8606251497 CR:JAGae17562 )
32bit applications running on 64 bit kernel,which call
getresuid(3C) or getresgid(3C) may abort and dump core on
systems with greater than 2GB physical memory.
( SR:8606245321 CR:JAGae11794 )
inetd(1M) daemon may hang on 11.11 trusted systems.
Inetd services will not work until "inetd -b" is run twice.
PHCO_26124:
( SR:8606231691 CR:JAGae00927 )
A user built perl executable aborted when using getpwent(3C)
API.
( SR:8606225736 CR:JAGad94809 )
Enhancement providing pre-enablement for a future release of
libnsl functionality. The changes in this patch will have no
affect on your system.
( SR:8606233401 CR:JAGae02625 )
setlocale(3C) is resulting in core dump when an application
compiled with -z option calls setlocale(3C) more than ten
times with different locales and categories other than
LC_ALL.
PHCO_25452:
( SR:8606228311 CR:JAGad97368 )
On a system with duplicate utmpx entries, logname and
getlogin were reporting incorrect login-names for
the user.
( SR:8606199060 CR:JAGad68247 )
Deadlock occurs when one thread in the process is performing
a blocking read (via stdio interfaces like fgets), another
thread performs a fork() before the blocking thread could
return.
( SR:8606225942 CR:JAGad95015 )
Improve performance of getdate() and clock() in
multi-threaded environments.
( SR:8606225355 CR:JAGad94442 )
Application which uses localtime() aborts when built
with -z and environment variable TZ set to last entry
in /usr/lib/tztab
PHCO_24942:
( SR:8606212783 CR:JAGad81970 )
res_query dumps core with large numbers of file descriptors.
( SR:8606205180 CR:JAGad74356 )
regexec() does not handle multibyte characters correctly.
( SR:8606214105 CR:JAGad83296 )
memchr() returns NULL unexpectedly.
( SR:8606203226 CR:JAGad72400 )
When a file stream is opened in write-only mode, an
immediate fread() reported failure but an fread() which was
followed by a fwrite() reported success.
( SR:8606213123 CR:JAGad82310 )
directory (3C) API's mutex contention.
( SR:8606204965 CR:JAGad74141 )
Default SBA support for C++ applications.
( SR:8606211883 CR:JAGad81071 )
delmntent libc routine deletes the entire mnttab contents.
( SR:8606202970 CR:JAGad72144 )
When a file stream is opened in read-only mode, putw()
reports a success though sets the errno to EBADF.
( SR:8606206070 CR:JAGad75245 )
Performance degradation of mktime ().
( SR:8606183079 CR:JAGad52295 )
incorrect freeing of memory in update_mnttab may
result in core dump.
( SR:8606215963 CR:JAGad85135 )
11.11 libc patches install PA1.1 version libc library
under /usr/lib on PA2.0 system.
PHCO_24400:
( SR:8606204553 CR:JAGad73735 )
getwc() incapable of handling codeset GB18030.
( SR:8606201456 CR:JAGad70632 )
The libc is not IPv6 enabled.
( SR:8606188513 CR:JAGad57721 )
fstyp returns "unknown_fstyp" on VxFS version 4 disk layout
file system
PHCO_23427:
( SR:8606177629 CR:JAGad46861 )
ptsname corrupts heap SIGBUS may result
( SR:8606196622 CR:JAGad65825 )
Multithreaded application core dumps sometimes when
it uses the Name Service Switch calls like getXXent
and endXXent.
( SR:8606179946 CR:JAGad49168 )
New feature and not a defect. Initialized TLS support
in libc for 64 bit non-threaded applications.
( SR:8606239637 CR:JAGab20870 )
When environment variable TZ is not set, the variables
tzname[2] and timezone is set to hard coded values
corresponding to Eastern Standard Time.
( SR:8606172344 CR:JAGad41604 )
(1) Trusted system calls made on an 11.0 NIS system
causes a SIGSEGV core dump.
(2) Using "dns" as a source for databases other than
"hosts" causes a SIGSEGV core dump.
( SR:8606194571 CR:JAGad63779 )
getdate fails VSU test case
( SR:8606165366 CR:JAGad34660 )
mallinfo() returns incorrect arena/uordblks.
( SR:8606186527 CR:JAGad55731 )
M_BLOCK behavior for malloc not working correctly.
( SR:8606185046 CR:JAGad54248 )
malloc(3C) has a silent data corruption in fourth quadrant.
PHCO_23772:
( SR:8606185984 CR:JAGad55189 )
For those PA-32bit Threaded C Applications which uses C++
plugins and pthread/cma calls in static
constructor/destructor, may happen that destructors will be
called twice. Non-threaded PA-32 bit applications do not
have this problem.
PHCO_23093:
( SR:8606162328 CR:JAGad31644 )
Memory Corruption when using fwscanf routine with
%lc option.
( SR:8606162140 CR:JAGad31456 )
regcomp(3C) function fails to detect an extended
regular expression
( SR:8606170481 CR:JAGad39745 )
sigwait() does not work as cancellation point if
the thread is cancelled after it enters
__sigwait_sys().
( SR:8606172179 CR:JAGad41440 )
User cannot use C++ runtime library on 32 bit
application
( SR:8606175166 CR:JAGad44410 )
gettimeofday is very slow for certain vendors who
use it for time stamping.
( SR:8606164457 CR:JAGad33756 )
Global symbols in libc can conflict with one in
program causing SIGBUS.
( SR:8606102984 CR:JAGab69119 )
No externally supported method to pthread safe
dynamically loaded libs
Defect Description:
PHCO_27434:
( SR:8606258699 CR:JAGae23018 ) Duplicate
( SR:8606261751 CR:JAGae26070 ) Duplicate
( SR:8606265515 CR:JAGae29801 )
When using popen(3S) in a multithreaded application,
the process can hang waiting in pclose(3S) because
of race conditions.
Resolution:
The popen(3S) and fork(2) were serialised to resolve
the race conditions.
( SR:8606262841 CR:JAGae27171 )
In strtod(3C), if the first argument is "infinity",
it is returning next to next character after
"infinity". But it is supposed to return next character
after "infinity".
Resolution:
strtod(3C) is modified in such a way that, if the
first argument is "infinity", then it will return
next character after "infinity".
PHCO_27910:
( SR:8606260114 CR:JAGae24434 )
When getipnodebyname() is called with an IP address
as the argument in a multi-threaded environment, the
static global variables may be corrupted as they were
not protected for threads.
Resolution:
The global variables are now protected for threads by
defining them locally to the function where they are used.
( SR:8606239772 CR:JAGae08197 )
Obtaining complete filesystem mount information can be a
performance problem for some applications on systems having
a large number of mounts.
Resolution:
Used the new system call which returns information for
multiple mounts with one call (rather than one per call).
( SR:8606257150 CR:JAGae21456 )
Path name searching is done twice which causes opendir
to be slower than necessary.
Resolution:
Path name search has been reduced to one from two calls
by altering the way the syscalls are made.
( SR:8606254777 CR:JAGae19108 )
When gethostbyname() is called with an IP address as the
argument in a multi-threaded environment, the static
global variables may be corrupted as they were not
protected for threads.
Resolution:
The global variables are now protected for threads by
defining them locally to the function where they are used.
( SR:8606251497 CR:JAGae17562 )
The APIs getresuid(3C) and getresgid(3C) call
pstat_getproc(2) syscall to get the real user,real group,
effective user, effective group, saved user and
saved group ids. But for a 32-bit application running on
a 64-bit kernel, there is a possibility of an error with
errno set to EOVERFLOW. Due to improper handling of this
errno in getresuid(3C) and getresgid(3C), made them to fail.
Resolution:
getresuid(3C) and getresgid(3C) have been modified to
handle the EOVERFLOW in the right fashion.
( SR:8606245321 CR:JAGae11794 )
Application calls any of the APIs getpwnam(3C),getpwuid(3C),
getgrgid(3C), or getgrnam(3C) and forks a new process.
In the context of the child process, it then closes all
open files.When any of the above mentioned APIs are
called again in the child context,the API tries to use
a cached file descriptor which was opened in the parent
context causing undesired results.
Resolution:
Libc source has been modified so that the APIs getpwnam(3C),
getpwuid(3C), getgrgid(3C) and getgrnam(3C) will not use
the cached file descriptor in the child context after
fork, if it is closed and reopened.
PHCO_26870:
( SR:8606239772 CR:JAGae08197 )
Obtaining complete filesystem mount information can be a
performance problem for some applications on systems having
a large number of mounts.
Resolution:
Used the new system call which returns information for
multiple mounts with one call (rather than one per call).
( SR:8606260114 CR:JAGae24434 )
When getipnodebyname() is called with an IP address
as the argument in a multi-threaded environment, the
static global variables may be corrupted as they were
not protected for threads.
Resolution:
The global variables are now protected for threads by
defining them locally to the function where they are used.
( SR:8606257150 CR:JAGae21456 )
Path name searching is done twice which causes opendir
to be slower than necessary.
Resolution:
Path name search has been reduced to one from two calls
by altering the way the syscalls are made.
( SR:8606254777 CR:JAGae19108 )
When gethostbyname() is called with an IP address as the
argument in a multi-threaded environment, the static
global variables may be corrupted as they were not
protected for threads.
Resolution:
The global variables are now protected for threads by
defining them locally to the function where they are used.
( SR:8606251497 CR:JAGae17562 )
The APIs getresuid(3C) and getresgid(3C) call
pstat_getproc(2) syscall to get the real user,real group,
effective user, effective group, saved user and
saved group ids. But for a 32-bit application running on
a 64-bit kernel, there is a possibility of an error with
errno set to EOVERFLOW. Due to improper handling of this
errno in getresuid(3C) and getresgid(3C), made them to fail.
Resolution:
getresuid(3C) and getresgid(3C) have been modified to
handle the EOVERFLOW in the right fashion.
( SR:8606245321 CR:JAGae11794 )
Application calls any of the APIs getpwnam(3C),getpwuid(3C),
getgrgid(3C), or getgrnam(3C) and forks a new process.
In the context of the child process, it then closes all
open files.When any of the above mentioned APIs are
called again in the child context,the API tries to use
a cached file descriptor which was opened in the parent
context causing undesired results.
Resolution:
Libc source has been modified so that the APIs getpwnam(3C),
getpwuid(3C), getgrgid(3C) and getgrnam(3C) will not use
the cached file descriptor in the child context after
fork, if it is closed and reopened.
PHCO_26124:
( SR:8606231691 CR:JAGae00927 )
When the domain name is set to null and when the
NSS (Name Service Switch) configuration is "files nis" for
password database, then the getpwent(3C) API dumps core
with the SIGBUS error. In the switch code, the destructor
for the same files backend is called second time.
Resolution:
The code flow is changed in such a way that the destructor
for the same files backend will not be called more than
once.
( SR:8606225736 CR:JAGad94809 )
Enhancement providing pre-enablement for a future release of
libnsl functionality. The changes in this patch will have no
affect on your system .
Resolution:
Provided a wrapper routine for libnsl.
( SR:8606233401 CR:JAGae02625 )
setlocale(3C) is dereferencing "NULL" pointer and resulting
in core dump while checking whether locales can be removed
from the cache or not.
Resolution:
setlocale(3C) will check for NULL pointer before
dereferencing a pointer during removal of locales
from the cache.
PHCO_25452:
( SR:8606228311 CR:JAGad97368 )
Due to duplicate entries problem in the utmpx file, we had
more than one entry for the same pts/pty/tty. This leads to
a situation wherein only one of the entries in the
/etc/utmpx file is correct and signifying the current
session of the user and the rest of the entries being
incorrect. They correspond to processes that no-longer
exist but still are marked as user processes. logname and
getlogin would report incorrect username in this case.
Resolution:
The fix takes into account the current session for a
particular terminal. It compares the session id of the
calling process and the session id of the ut_pid entry in
the /etc/utmpx file to get the correct entry which is
the entry corresponding to the current user's session.
( SR:8606199060 CR:JAGad68247 )
The input stdio interfaces acquire a mutex and
perform a read. The read may block if there is no data
available on the stream. At that time, when fork() is
performed by another thread, the registered
atfork-handler also tries to acquire the same mutex
but as the mutex is held by a thread which is blocked
on I/O, it results in an indefinite wait causing a
deadlock.
Resolution:
The locking of the stdio mutex in atfork-handler has been
removed. With this fix, deadlock in parent will not occur
as reported in the defect.
( SR:8606225942 CR:JAGad95015 )
Improve performance of getdate() and clock() in
multi-threaded environments.
Resolution:
Reduced locking granularity in getdate() and clock() to
improve the performance in multi-threaded environments.
( SR:8606225355 CR:JAGad94442 )
Core dump occured because of a null pointer dereference
which happens when 1) Application is built with -z and
the environment variable TZ used is not in the file
/usr/lib/tztab
Or 2) when the application is built with -z and the
environment variable TZ is the last entry in the
/usr/lib/tztab.
Resolution:
The pointer is checked for null before de-referencing.
PHCO_24942:
( SR:8606212783 CR:JAGad81970 )
res_query() dumps core when called through a large number of
threads simultaneously from a single process as the socket
descriptor may cross 2048 which is the current limit.
Resolution:
The code has been modified to handle any number of threads
(limited by system resources only) as the limit on socket
descriptor is removed.
( SR:8606205180 CR:JAGad74356 )
regexec() does not handle multibyte characters correctly.
where the second byte of a multibyte SJIS character is
interpreted as stand alone single byte character.
Resolution:
For matching a pattern containing .* , .+ , regexec travers
es the entire length of the string and then backtracks to
find out if it can match the remaining part of the
pattern.The backtracking logic currently doesn't take the
multi-byte scenario into consideration and goes back byte
by byte.In the case of a multi-byte character with a valid
character as a second byte, a match is found for the
second byte even though it is not a stand-alone character
and just forms part of a multi-byte character.
Now the code has been changed to take care of multi-byte
back tracking.
( SR:8606214105 CR:JAGad83296 )
memchr() returns NULL unexpectedly in the PA 2.0 Narrow mode
Resolution:
The above defect is because the higher order 32 bits were
not cleared. Now the instruction is added to clear the
higher order 32 bits in PA2.0 Narrow mode.
( SR:8606203226 CR:JAGad72400 )
There was a missed condition wherein a file stream which has
been opened in write-only mode, an immediate fread on the
stream failed but if the fread() followed after a fwrite()
didn't report an error.
Resolution:
Changes have been made to code in the fread() call.Check was
being made on the basis of _cnt field of the file stream and
the routine that sets the error (_filbuf()) was then being
called. The pathflow is different when the _cnt field is
greater than 0 (which is taken when fwrite() updates the
file stream and updates the _cnt field). _cnt greater than
0 denotes that there are bytes in the look-ahead buffer.
In case the file stream has been fflushed,the _cnt field
is set to 8192 (_DBUFSZ) when the stream is opened in
read-only mode. These cases, when the _cnt
is greater than 0 had not been taken into consideration
from the write-only mode of operation point of view.
Introduced a check to handle this.
( SR:8606213123 CR:JAGad82310 )
Application using the directory (3C) API's in
multithreaded environment got into mutex contention
problem, which resulted in 100% usage of the CPU resource
time.
Resolution:
The application was creating more than 1000 threads and also
openning ~50000 directories.
Since there are 50000 instances opendir(), there will be
50000 nodes in the directory mutex linked list. Under this
circumstance when multiple threads at the same time tries
to open/close directories, in an average there will be a
traversal of ~25000 nodes, during which the global mutex
will be locked.
Fix is to use 2 linked lists Inuse and Free in place of
one list. This eliminates lot of search time and mutex
contention. The 2 APIs opendir() and closedir() modified
to incorporate the new design, which provides direct
access to the required mutex.
( SR:8606204965 CR:JAGad74141 )
The existing PA C++ binaries performnace can be improved
significantly by providing the SBA support for small block
allocation.
Resolution:
mallopt(3C) is enhanced to provide a new commond M_SBA_ON
which will be used by libCsup, C++ initialization library.
The libCsup will call mallopt(M_SBA_ON, 1) in its
initialization routine, as a result the mallopt configures
the SBA with the predefined default values.
( SR:8606211883 CR:JAGad81071 )
delmntent libc routine deletes the entire contents if
mntent structure obtained from the call to getmntent
was passed to delmntent.
Resolution:
The defect is due to the returning of same global buffer
by getmntent call to an application and the same global
buffer being used in the delmntent libc call. The code
has been fixed to address the problem.
( SR:8606202970 CR:JAGad72144 )
When putw() fails, it is supposed to set the error flag
for the file stream, set the errno describing the error
occurred and return EOF. Only the errno was being set but
error flag of the file stream wasn't being updated due to
which EOF was not being returned.
Resolution:
Change has been made to flsbuf.c file in the _wrtchk()
routine wherein, in case no write permissions are found
for the file stream, the errno is set and EOF returned but
the file stream's errof flag wasn't being set. On return
from this call, file's error flag was being checked which
was not being set earlier and hence, it was being considered
as success.
( SR:8606206070 CR:JAGad75245 )
mktime takes the timezone specification from /usr/lib/tztab
file. Incase the application does a rapid switch between 2
invalid time zones then for each switch the tztab file is
accessed and searched for the required time zone. Hence for
each switch the file is read completely. This degrades the
performance of mktime.
Resolution:
The /usr/lib/tztab file is cached in memory local to the
process,the first time mktime is called,and each subsequent
call to mktime makes use of this cached data. This approach
reduces the number of disk read operations.
( SR:8606183079 CR:JAGad52295 )
freeing of an unallocated memory was done in
update_mnttab routine, which may result in coredump
of an application.
Resolution:
The problem was fixed by freeing only
the memory which was allocated through libc malloc
family calls.
( SR:8606215963 CR:JAGad85135 )
When cold installing 11.11, the postinstall script for
CORE-SHLIBS replaces the PA1.0 /usr/lib/libc.2 with a
with a PA2.0 version if needed.
When installing PHCO_23427 (or one of the superseded
patches PHCO_23772 and PHCO_23093) on a PA2.0 system,
this PA2.0 file gets replaced by a PA1.0 version.
Resolution:
Control scripts have been provided along with the
patch for placing the right version of libc library
under /usr/lib directory.
PHCO_24400:
( SR:8606204553 CR:JAGad73735 )
getwc() unable to handle Chinese codeset GB18030
Resolution:
getwc() depends on mbtopc() to convert file code to process
code.When Multibyte character is split across the buffer
mbtopc() detects this and returns number of more bytes
required to make this vaild character. The current getwc()
function works on the assumption that mbtopc() always
returns the number of more bytes required in case of a
mlltibyte split.But in case of gb18030 mbtopc() method
cannot tell the caller its a 2 or 4 byte, because both
two and four byte characters begin with the same byte
range (x81 - xFE). Now the routine mbtopc() in gb18030
method returns MB_CUR_MAX in case the multibyte character
is split across the buffer.Now to fix this getwc() is
changed not to depend on the return value from mbtopc()
in case of the multibye split.
( SR:8606201456 CR:JAGad70632 )
IPv6 functionality should be provided in libc.
Resolution:
The source code for networking APIs in libc
have been modified to effect IPv6 changes.
New APIs included :
getaddrinfo(),
getnameinfo(),
freeaddrinfo(),
gai_strerror(),
getipnodebyname(),
getipnodebyaddr(),
rcmd_af(),
rresvport_af(),
rexec_af()
The last three APIs are provided to enable IPv6 in
rcommands.
rlogin and remsh Applications call rcmd_af() and
rresvport_af() APIs and rexec calls rexec_af() API.
IP address to hostname resolution APIs:
The getaddrinfo(), getipnodebyname() APIs are provided
for name to address resolution. The getnameinfo() and
getipnodebyaddr() APIs are provided for address to name
resolution.
They work for both IPv4 and IPv6 hostnames and addresses.
freeaddrinfo() is used to free the linked list created
by getaddrinfo().
gai_strerror() is used to print error messages
corresponding to error values from getaddrinfo().
( SR:8606188513 CR:JAGad57721 )
fstyp command calls statvfsdev on VxFS version 4 disk layout
returns "unknown_fstyp". It fails on accessing initial inode
list extents block address which exceeds 32 bit addressing.
lseek64 should be used instead of lseek in __vx_fs_lseek.
Resolution:
Now the call to lseek is replaced with lseek64 by using a
compilation flag _FILE_OFFSET_BITS=64 in the makefile.
PHCO_23427:
( SR:8606177629 CR:JAGad46861 )
When the application is linked with libpthreads
ptsname() function may corrupt heap
Resolution:
The cause of this problem is instead of passing the sizeof
bytes allocated by malloc to the GET_TSS() function, the
sizeof the character pointer returned by malloc is passed
as an argument. So,it is always taking sizeof the character
pointer which is less than the number of bytes allocated
by malloc.
ptsname() is modifiied to pass the correct argument
( SR:8606196622 CR:JAGad65825 )
The getXXent call and endXXent functions call shl_unload()
function to unload the shared backend library when the
number of references to the backend instance structure is
zero. However, the library call shl_unload() on PA32
machine unloads the shared library regardless of whether
there are other references to it through other load
invocations. This causes the subsequent shl_unload call
fail with signal 11.
Resolution:
Removed the shl_unload call for PA32 architecture in
the SO_per_src_delete function.
( SR:8606179946 CR:JAGad49168 )
Initialized TLS support in libc for 64 bit non threaded
applications.
Resolution:
The initialization routine of Libc has changed to support
initialized TLS variables in a PA64 non threaded
applications. Both the archived and shared version of the
libraries have this enhancement. To get the complete
functionality of ITLS (Initilized thread local storage) the
following patches has to be installed.
PHSS_23441- linker core
PHSS_23794 - linker ISU
PHCO_23846 - libpthread
PHSS_23953 - Fortran compiler
Currently this feature is available with Fortran compiler
only.No changes are required to be done in libc when this
feature is made available for any other compilers.
( SR:8606239637 CR:JAGab20870 )
When the variable TZ is not set in the environment, in HP-UX
it defaults to EST5EDT which is the east coast time in US.
This poses problem in the environment of the processes that
(a) are started by init(1m)
(b) clear their environment (e.g. login (1), sendmail(1m) )
The hard coded value is inappropriate for any timezone other
than east coast of US and the difference is difficult to
track for countries like Australia which frequently update
their daylight timing rules
Resolution:
When the environment variable TZ is not set, tzset() checks
the default file /etc/default/tz for the timezone value and
sets timezone values based on that. The file
/etc/default/tz contains the timezone value set by tzset()
when the environment variable TZ is not set. The format for
the file is same as TZ format without the prefix "TZ=".
Please check environ(5) for TZ format. 1) if the
environment variable TZ is present, it takes precedence. 2)
if TZ is not present then the value contained in
/etc/default/tz is used for the default. 3) if
/etc/default/tz is not set then the default value is
equivalent to EST5EDT (Eastern Standard Time) of US.
(Install the Patch PHCO_24396 to get the sample
/etc/default/tz file. Please read "Special Installation
Instructions" field for more information on PHCO_24396
patch)
( SR:8606172344 CR:JAGad41604 )
When the APIs getprpwnam(), getgrnam(), getnetbyname(),
and getservbyname() are configured with the
/etc/nsswitch.conf file to search sources that do not
support these calls, the Name Server Switch engine code
unloads the sources and returns NSS_NOTFOUND. The source
"nis" doesn't support the trusted system call getprpwnam().
The source "dns" is only valid for the "hosts" database.
Thus, subsequent API getXXXbyYYY calls that try to search
sources that have been unloaded end up accessing invalid
locations, resulting in a SIGSEGV core dump.
Resolution:
If a source doesn't support an API getXXXbyYYY call,
don't unload the source. Just have the Name Server
Switch engine code return NSS_UNAVAIL.
( SR:8606194571 CR:JAGad63779 )
Insufficient handling of locale specific representation of
time in getdate(3C)
Resolution:
getdate() changed to be inline with UNIX 98 specifications.
( SR:8606165366 CR:JAGad34660 )
mallinfo() doesn't give correct memory statistics if the
application is multithreaded and uses multiple arenas. The
problem was introduced during multi arena enhancement. The
way mallinfo() designed works fine only for single arena,
but the problem starts when there are 2 or more arenas and
there is a overlapping brk value.
When multiple threads call malloc(3C) to allocate space,
each will be assigned an arena. Each arena will maintain
the start and end point of that arena. The arena_start
represents the starting heap address for this thread and
the end_arena represents the ending address. Assume 2
threads are say THREAD1 and THREAD2 running in parallel.
THREAD1 calls malloc(), malloc stores the the arena_start1
(current brk value say 0x1000 ) and extends the brk value
to predefined size and sets the end_arena1(0x4000),
similarly THREAD2(arena_start 0x4000, arena_end 0x8000). If
THREAD1 again calls malloc() and there is no pre-allocated
space in the arena, the brk value is increased and
arena_end will be set( 0x12000).
The mallinfo() will collect the size by visiting each arena
starting from arena_start till arena_end of that arena. In
the above case arena_start and arena_end of THREAD1 is
0x1000 and 0x12000 respectively, for THREAD2 arena_start is
0x4000 and arena_end is 0x8000 respectively. While counting
the size, arena for THREAD2 will be counted 2 times, once
with arena1 and once with arena2. Hence the problem. In
single arena implementation this problem will not be
revealed.
Double counting is happening because we will modify the
dummy header when lastbrk != curbrk. The dummy header which
had SIZE=0 and USED set, will be set with the difference of
curbrk and lastbrk. If the lastbrk of one thread is not
equal to the curbrk, the possibility is that either user
application called brk/sbrk or some other thread expanded
the brk value. If the curbrk value is changed from some
other thread then the other thread treats this as the user
allocation and the dummy header is modified appropriately
and fixes the arenaend for this thread.
The problem will be there if there is a overlap between the
brk values of the different arenas. So in the current
implementation USER_ID is used when
O The application directly calls brk/sbrk O The other arena
calls brk/sbrk
The problem is because of setting USER_ID when the other
arena calls brk/sbrk.
Resolution:
The resolution is basically to avoid the use of USER_ID
when the other arena calls brk/sbrk. A new memory block
identifier ARENA_ID is defined in malloc.c as
The ARENA_ID is used to mark that the memory block is used
and it is used by some arena. The used memory block will be
marked with ARENA_ID under the circumstance mentioned
below.
O When a block of memory is used by some other arena and
the last brk value maintained in the that arena is not
equal to the _curbrk. While counting memory usage
statistics in mallinfo(), the memory block with ARENA_ID as
the id we will skip because it is used by some other arena
and will be taken into account under that arena.
( SR:8606186527 CR:JAGad55731 )
The defect was due to blocking the signals after locking
the malloc mutexes in the case of multi threaded malloc.
When malloc/calloc/valloc/realloc is called in signal
handler and also the main thread of execution and there
are frequent signals to application. The application
becoming busy in locking and unlocking the malloc mutexes
resulting into application hang situation
Resolution:
Signals blocking is done before locking the mutexes.
Which avoids the too many mutex locks and unlocks.
( SR:8606185046 CR:JAGad54248 )
The defect was due to coalescing when the allocation is
switched from sbrk to mmap at 4th quadrant. The coalescing
was resulting to allocating the blocks of memory near the
stack, which leads to data corruption.
Resolution:
Resolution is to avoid coalescing near the quadrant 4
boundary.
PHCO_23772:
( SR:8606185984 CR:JAGad55189 )
When a C application uses C++ plugins and calls pthread/cma
calls in static constructor/destroctor, it was leading to
destructor being called twice. This was happening because
the C++ runtime initialization routine was invoked at a
point when the pthread library initialization would not have
been complete . During this time, constructor was invoking
pthread calls . This might have lead to destruction of the
shared data (static/global) in the libCsup.
Resolution:
Changes are made to libc so that C++ runtime initialization
routine is invoked only after the completion of pthread
library initialization.
PHCO_23093:
( SR:8606162328 CR:JAGad31644 )
Reading a single wide character with %lc or %lC
format string by fwscanf is not supposed to add a
terminating null character. This is specifically
mentioned in the man page. But fwscanf code with
%lc format string was adding a terminating null
character to the second location of the argument.
Resolution:
Code was changed to consider the "c" case for not
adding the terminating null character at the second
location of the argument to fwscanf.
( SR:8606162140 CR:JAGad31456 )
regcomp(3C) fails to detect an extended regular
expression match in the input data on HP-UX 11.00
using libc patch PHCO_20765 (or PHCO_22076) but
works on HP-UX 10.20 w/ PHCO_20441
Resolution:
Defect is fixed by adding an "alternate" flag
which is set when there is an alternate('|') option
in the regular expression.
( SR:8606170481 CR:JAGad39745 )
sigwait() does not work as cancellation point if the
thread is cancelled after it enters __sigwait_sys().
When cancelling a thread that is blocked on sigwait()
by means of pthread_cancel(), the blocked sigwait()
returns with EINTR rather than checking the cancellation
point before it returns and terminate the thread.
Resolution:
When the thread is cancelled, then __sigwait_sys returns
error EINTR and does not set errno. In sigwait we were
checking for errno and setting the cancellation point.
Now that has been modified to check for return value.
( SR:8606172179 CR:JAGad41440 )
User cannot use C++ runtime library on 32 bit application
without either using a C++ main program or explicitly
invoke the C++ runtime library's initialization
routine, _main, from the C ( or Fortran ) main program.
Resolution:
The definition of the __main_ptr variable is done in
libc_init routine. The same varible is defined as a
global variable in libcsup, which will point to the C++
runtime library initialization routine, _main. Thus,
when libcsup is linked into the program, the variable
_main_ptr will point to _main; otherwise, it will
contain 0.
Now, we have the following three scenerios when the
program is linked with libcsup.
1. Multithreaded Application linked with libc :
In this case, C++ runtime initialization routine
_main (of libcsup) is invoked through __main_ptr in
libc_init.c routine.
2. Single Threaded Application linked with libc :
In this case, C++ runtime initialization routine
_main (of libcsup) is invoked through __main_ptr in
libc _start.c routine.
3. Multithreaded Application linked with libcma :
In this case, C++ runtime initialization routine
_main (of libcsup) is invoked through __main_ptr
in libc_init routine and control won't come to
libc's _start.c routine as libcma's startup routine
is called.
( SR:8606175166 CR:JAGad44410 )
gettimeofday is very slow for certain vendors who
use it for time stamping because it calls a heavy
weight system call to get the current time of the
day.
Resolution:
A new API hrtime_t gethrtime(void) has been added
to libc. This API uses fast light weight system
call to get the nano seconds from certain time.
It does not give you the current time of day.
hrtime_t is a signed 64 bit number. This API will
only be available if the application is being
compiled in -Ae mode because 64 bit integer number
is not available in -Aa mode.
( SR:8606164457 CR:JAGad33756 )
Global symbols in libc can conflict with one in program
causing SIGBUS. In ptsname.c we have defined two global
symbols alpha and range_spec. They are symbols which are
used only by libc. They should not be visible to customers.
They can conflict with the user defined global symbols.
Resolution:
alpha is changed to __alpha and range_spec is modifed as
__range_spec, so that they follow libc conventions.
( SR:8606102984 CR:JAGab69119 )
On HP-UX if a nonthreaded application links to a
thread-safed library the link will fail due to
unresolved symbols.To resolve these symbols, it is
necessary to link the nonthreaded application to the
threads library libpthread.But linking to that library
makes the application threaded even if it creates
no threads. Providing POSIX 1c thread "stubs" in HP-UX
C language library have two direct effects for
nonthreaded applications. a) POSIX 1c threads symbols
are resolved if a nonthreaded application links to a
thread-safed library
b)We avoid the overhead of a real threads library --
especially the overhead associated with mutexes when the
nonthreaded application uses thread stubs
rather than real threads library procedures.
Resolution:
Stubs are provided for all pthread calls only in SHARED
LIBC FLAVORS of the HP-UX C Library.
These stubs do not have any functionality, these are
dummy functions returning zero except pthread_getspecific()
family of APIs which has full functionality implemented
in the stubs. Full functionality is provided in the stub
for the following pthread calls
* pthread_key_create()
* pthread_getspecific()
* pthread_setspecific()
* ptherad_key_delete()
* pthread_exit()
Stub call to pthread_self() returns 1
Stub call to pthread_equal(arg1, arg2) will return
(arg1 == arg2)
Stub call to pthread_create() and pthread_attr_init()
returns ENOSYS.
All other stub calls returns zero.
There are two special interfaces provided for checking
whether an application is linked to pthread library or not.
a) __is_threadlib_linked()
returns 1 for an applications linked to pthread
library otherwise returns zero.
b) __get_ismt()
returns 1 for applications linked with libcma
returns 2 for applications linked with libpthread
otherwise returns 0
Risks:
------
An application may inadvertantly pick up the stubs when it
intended to use the real pthreads APIs, or it may pick up
the stubs when it needs cma APIs or stubs. These are all
link order problems. An application that needs cma behavior
must link to libcma (or the cma stubs library) and must do
so in a supported link order,
i.e. the link line should be shared only and should
not contain "-lc" before -lcma.
So long as this condition is met, the correct cma functions
will be referenced. Similarly, a multithreaded application
that needs pthread threads library behavior must link to
libpthread and must do so in a supported link order, and
only use shared libc and libpthread.
eg : An applications wants to use pthread stubs then
the link order should be
$ cc test.c -lc -lpthread
An applications wants to use pthread library then the
link order should be
$ cc test.c -lpthread -lc
Enhancement:
No (superseded patches contained enhancements)
PHCO_27434:
Enhancements were delivered in a patch this one has
superseded. Please review the Defect Description
text for more information.
SR:
8606102984 8606162140 8606162328 8606164457 8606165366
8606170481 8606172179 8606172344 8606175166 8606177629
8606179946 8606183079 8606185046 8606185984 8606186527
8606188513 8606194571 8606196622 8606199060 8606201456
8606202970 8606203226 8606204553 8606204965 8606205180
8606206070 8606211883 8606212783 8606213123 8606214105
8606215963 8606225355 8606225736 8606225942 8606228311
8606231691 8606233401 8606239637 8606239772 8606245321
8606251497 8606254777 8606257150 8606258699 8606260114
8606261751 8606262841 8606265515
Patch Files:
OS-Core.C-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libc.a
/usr/lib/libcres.a
/usr/lib/unix95.o
/usr/lib/unix98.o
OS-Core.C-MIN-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libc.a
/usr/lib/pa20_64/libcres.a
/usr/lib/pa20_64/unix95.o
/usr/lib/pa20_64/unix98.o
OS-Core.CORE-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libc.2
OS-Core.CORE-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libc.2
/usr/lib/pa11_32/libc.2
/usr/lib/pa20_32/libc.2
ProgSupport.PROG-AUX,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libp/libc.a
ProgSupport.PROG-AX-64ALIB,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libp/libc.a
ProgSupport.PROG-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libpicc.a
what(1) Output:
OS-Core.C-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libc.a:
$ PATCH_11.11/PHCO_27434 Sep 4 2002 01:53:12 $
/usr/lib/libcres.a:
$ PATCH_11.11/PHCO_27434 Sep 4 2002 02:35:43 $
/usr/lib/unix95.o:
None
/usr/lib/unix98.o:
None
OS-Core.C-MIN-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libc.a:
$ PATCH_11.11/PHCO_27434 Sep 4 2002 02:11:59 $
/usr/lib/pa20_64/libcres.a:
$ PATCH_11.11/PHCO_27434 Sep 4 2002 02:36:02 $
/usr/lib/pa20_64/unix95.o:
None
/usr/lib/pa20_64/unix98.o:
None
OS-Core.CORE-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libc.2:
$ PATCH_11.11/PHCO_27434 Sep 4 2002 02:17:01 $
OS-Core.CORE-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libc.2:
$ PATCH_11.11/PHCO_27434 Sep 4 2002 02:03:41 $
/usr/lib/pa11_32/libc.2:
$ PATCH_11.11/PHCO_27434 Sep 4 2002 02:03:41 $
/usr/lib/pa20_32/libc.2:
$ PATCH_11.11/PHCO_27434 Sep 4 2002 02:22:00 $
ProgSupport.PROG-AUX,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libp/libc.a:
$ PATCH_11.11/PHCO_27434 Sep 4 2002 02:29:09 $
ProgSupport.PROG-AX-64ALIB,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libp/libc.a:
$ PATCH_11.11/PHCO_27434 Sep 4 2002 02:34:23 $
ProgSupport.PROG-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libpicc.a:
$ PATCH_11.11/PHCO_27434 Sep 4 2002 02:05:43 $
cksum(1) Output:
OS-Core.C-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
1757519152 2529924 /usr/lib/libc.a
3681012279 67556 /usr/lib/libcres.a
1400633197 868 /usr/lib/unix95.o
294124086 868 /usr/lib/unix98.o
OS-Core.C-MIN-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
4160869362 4190356 /usr/lib/pa20_64/libc.a
978284565 67206 /usr/lib/pa20_64/libcres.a
2151074788 1632 /usr/lib/pa20_64/unix95.o
2763618295 1632 /usr/lib/pa20_64/unix98.o
OS-Core.CORE-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
209450916 1856400 /usr/lib/pa20_64/libc.2
OS-Core.CORE-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
2811416697 1851392 /usr/lib/libc.2
2811416697 1851392 /usr/lib/pa11_32/libc.2
3692873218 1806336 /usr/lib/pa20_32/libc.2
ProgSupport.PROG-AUX,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
2248727279 2797076 /usr/lib/libp/libc.a
ProgSupport.PROG-AX-64ALIB,fr=B.11.11,
fa=HP-UX_B.11.11_32/64,v=HP:
3853584608 4533050 /usr/lib/pa20_64/libp/libc.a
ProgSupport.PROG-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
2746623422 2688516 /usr/lib/libpicc.a
Patch Conflicts: None
Patch Dependencies:
s700: 11.11: PHCO_24402
s800: 11.11: PHCO_24402
Hardware Dependencies: None
Other Dependencies:
PHCO_27910: 8606257150 (JAGae21456) The opendir(3C)
performance benefit requires patch PHKL_26239. Both
PHCO_27910 and PHKL_26239 patches are required to
ensure full performance benefit. Installing any of
these 2 patches alone will not cause any adverse
effects to the system.
PHCO_27910: 8606239772 (JAGae08197) The following patches
are required to ensure full performance benefit.
PHKL_26467, PHKL_26239, PHCO_26242, PHCO_27120, PHCO_26331,
PHCO_26332, PHCO_26333 and PHCO_26334. Any of these
patches may be installed independently with no adverse
effects to the system.
PHCO_26870: 8606257150 (JAGae21456) The opendir(3C)
performance benefit requires patch PHKL_26239. Both
PHCO_26870 and PHKL_26239 patches are required to ensure
full performance benefit. Installing any of these 2 patches
alone will not cause any adverse effects to the system.
PHCO_26870: 8606239772 (JAGae08197) The following patches
are required to ensure full performance benefit.
PHKL_26467, PHKL_26239, PHCO_26242, PHCO_27120, PHCO_26331,
PHCO_26332, PHCO_26333 and PHCO_26334. Any of these patches
may be installed independently with no adverse effects to
the system.
Supersedes:
PHCO_27910 PHCO_26870 PHCO_26124 PHCO_25452 PHCO_24942 PHCO_24400
PHCO_23772 PHCO_23427 PHCO_23093
Equivalent Patches: None
Patch Package Size: 23790 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_27434
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_27434.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_27434. 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_27434.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_27434.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_27434.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
If you use HP Process Resource Manager (PRM)
version 1.08 or 1.08.2, /opt/prm/bin/prm3d may
core dump at startup if this patch is loaded and
PRM is running.
The following message displays:
Assertion failed:!isLocked_,filedaemon.cc, line232
To solve the problem, load PRM C.02.00 or later
from the September 2001 (or later) Application
Release (AR) media. If you do not experience the
core dump at startup, you will probably not
encounter problems.
If libc patches are installed without rebooting,
applications currently running which are linked shared
against libc will still continue using the former version of
libc. If this presents a problem to any applications, you
should reboot.
PHCO_23427: JAGab20870
The tzset() behaviour have been changed to take default TZ
values from the file/etc/default/tz. A sample file is
released as patch PHCO_24396. The /etc/default/tz included
in the patch contains the earlier default value ie.,
EST5EDT. So unless the user explicitly changes the value
contained in the file the tzset changes are transparent to
the user. The file /etc/default/tz contains the timezone
value set by tzset() when the environment variable TZ is not
set. The format for the file is same as TZ format without
the prefix "TZ=". Please check environ(5) for TZ format.
The order of TZ setting is as follows.
1) if the environment variable TZ is present, it takes the
precedence.
2) if TZ is not present, then the value contained in
/etc/default/tz is used for default.
3) if /etc/default/tz is not set, then the default value is
equivalent to EST5EDT (Eastern Standard Time) of US.
Risks : If the customer already has made some customisations
in /etc/default/tz, installing PHCO_24396 will overwrite
the file.
-----End of Document ID: PHCO_27434------------------------------------------
Document ID: PHCO_25918
Date Loaded: 20020906
Title: s700_800 11.11 sort(1) cumulative patch
Patch Name: PHCO_25918
Patch Description: s700_800 11.11 sort(1) cumulative patch
Creation Date: 02/08/12
Post Date: 02/09/06
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_25918
Symptoms:
PHCO_25918:
( SR:8606259335 CR:JAGae23653 )
Improper handling of certain files by sort(1).
( SR:8606215245 CR:JAGad84433 )
When sorting by field, sort(1) skips the last character
if a file does not terminate with a newline character and
LANG is not set to C.
( SR:8606225452 CR:JAGad94539 )
sort '-o' option loops infinitely, and a line
repeats itself forever as an output only in certain
situations for multibyte locales.
( SR:8606202868 CR:JAGad72042 )
Improper handling of certain files by sort(1).
Defect Description:
PHCO_25918:
( SR:8606259335 CR:JAGae23653 )
Improper handling of certain files by sort(1).
Resolution:
The code has been modified to handle the files
appropriately.
( SR:8606215245 CR:JAGad84433 )
When sorting (by field) a file which does not have a
terminating newline, and where the LANG variable is not
set to C, the command does not output the last character
of the file. The problem occured because the integer
counter was not being incremented to handle the new line
character.
Here are the steps to reproduce the problem:
# echo 'one one\ntwo two\c' > TST
# cat TST
one one
two two
[ note that there is no newline at the end of file ]
# unset LANG ## First, the correct results:
# sort -k 1,1 TST
sort: Warning: A newline character was added to the
end of file TST.
one one
two two
# export LANG=french
# sort -k 1,1 TST
sort: Warning: A newline character was added to the
end of file TST.
sort: Warning: A newline character was added to the
end of file TST.
one one
two tw <=== the "o" in "two" has been removed
Resolution:
The problem was due to one of the internal variable
(used to count the number of newlines) not getting
properly incremented when the newline appears.
The problem was corrected by incrementing the counter
to handle the newline character appropriately.
( SR:8606225452 CR:JAGad94539 )
The sort(1) command loops infinitely in certain cases,
and the problem was due the incorrect return value
on encountering WEOF.It was not returning a NULL at end
of file hence sort(1) went into an infinite loop as it
was not able to find the end of file.This occured only
in case of multibyte locales.
Resolution:
The sort(1) code has been modified to return
NULL when sort(1) encounters EOF.
( SR:8606202868 CR:JAGad72042 )
Improper handling of certain files by sort(1).
Resolution:
The code has been modified to handle the files
appropriately.
SR:
8606202868 8606215245 8606225452 8606259335
Patch Files:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/bin/sort
what(1) Output:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/bin/sort:
$Revision: (#) sort CUP11.11_BL2002_0812_3 PATCH_11
.11 PHCO_25918
Mon Aug 12 07:41:57 PDT 2002 $
cksum(1) Output:
OS-Core.UX-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
4244478368 45056 /usr/bin/sort
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 70 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHCO_25918
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_25918.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_25918. 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_25918.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_25918.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_25918.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_25918------------------------------------------
Document ID: PHSS_27784
Date Loaded: 20020905
Title: s700_800 11.00 OV NNM6.1 http server fix
Patch Name: PHSS_27784
Patch Description: s700_800 11.00 OV NNM6.1 http server fix
Creation Date: 02/08/27
Post Date: 02/09/05
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
OpenView Network Node Manager 6.1
Filesets:
OVPlatform.OVWWW-SRV,fr=B.06.10.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_27784
Symptoms:
PHSS_27784:
http server process cannot handle bad HTTP request types
correctly.
Defect Description:
PHSS_27784:
http server process was not handling the bad requests
properly.
Resolution:
Code has been added for handling the bad requests properly.
Enhancement:
No
SR:
8606274132
Patch Files:
OVPlatform.OVWWW-SRV,fr=B.06.10.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/httpd/bin/ab
/opt/OV/httpd/bin/apachectl
/opt/OV/httpd/bin/apxs
/opt/OV/httpd/bin/dbmmanage
/opt/OV/httpd/bin/htdigest
/opt/OV/httpd/bin/htpasswd
/opt/OV/httpd/bin/httpd
/opt/OV/httpd/bin/logresolve
/opt/OV/httpd/bin/rotatelogs
what(1) Output:
OVPlatform.OVWWW-SRV,fr=B.06.10.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/httpd/bin/ab:
None
/opt/OV/httpd/bin/apachectl:
None
/opt/OV/httpd/bin/apxs:
None
/opt/OV/httpd/bin/dbmmanage:
None
/opt/OV/httpd/bin/htdigest:
None
/opt/OV/httpd/bin/htpasswd:
None
/opt/OV/httpd/bin/httpd:
patched for CAN-2002-0392 [CERT VU#944335]
/opt/OV/httpd/bin/logresolve:
None
/opt/OV/httpd/bin/rotatelogs:
None
cksum(1) Output:
OVPlatform.OVWWW-SRV,fr=B.06.10.00,fa=HP-UX_B.11.00_32/64,
v=HP:
2015943931 28796 /opt/OV/httpd/bin/ab
1446960109 6579 /opt/OV/httpd/bin/apachectl
2908369870 18554 /opt/OV/httpd/bin/apxs
3168729259 6428 /opt/OV/httpd/bin/dbmmanage
2081019407 32884 /opt/OV/httpd/bin/htdigest
1736902611 24677 /opt/OV/httpd/bin/htpasswd
2980400674 446464 /opt/OV/httpd/bin/httpd
3282197105 24658 /opt/OV/httpd/bin/logresolve
4013327400 24653 /opt/OV/httpd/bin/rotatelogs
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHSS_27783:
s700: 10.20
s800: 10.20
PSOV_03207:
sparcSOL: 2.5 2.6 2.7 2.8
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 PHSS_27784
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27784.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27784. 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_27784.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_27784.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27784.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
========================================================
BEFORE LOADING THIS PATCH...
If there are any ovw sessions running on either the
Management Station or on any Management Consoles, these
sessions need to be closed. The "ovstop" command
should then be executed.
WARNING : the patch will not install if any
Network Node Manager processes are
detected.
BACKUP ALL OpenView DIRECTORIES TO TAPE. This
pre-caution ensures that if you have problems after
installing the patch, you will be able to restore your
current state from tape.
NOTE : ovstart is NOT executed after the patch is loaded
You will need to manually run ovstart.
Also, in order to keep a history of the patches
installed on your system the post-install script
will attempt to copy this <patch_name>.text file
to /usr/OV/ReleaseNotes/patches
(or /opt/OV/ReleaseNotes/patches). Please make
sure this file is in /tmp before installation.
========================================================
-----End of Document ID: PHSS_27784------------------------------------------
Document ID: PHSS_27700
Date Loaded: 20020905
Title: s700_800 11.11 CPSlib Cumulative Patch (OMP V2.0 for 11.11)
Patch Name: PHSS_27700
Patch Description: s700_800 11.11 CPSlib Cumulative Patch (OMP V2.0 for 11.11)
Creation Date: 02/08/14
Post Date: 02/09/05
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
CPS.CPS-32SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
CPS.CPS-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
CPS.CPS-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
No (superseded patches were critical)
PHSS_25029: MEMORY_LEAK
Category Tags:
defect_repair enhancement general_release critical
memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_27700
Symptoms:
PHSS_27700:
SR 8606238742 / DTS JAGae07765:
Nested OpenMP do/for loops can cause programs to
abort in the right cases.
PHSS_27075:
SR 8606241730 / DTS JAGae08988:
OMP program won't go parallel in a child process
after a fork call.
PHSS_26913:
1 OpenMP support routines are slow
2 Need support for OpenMP V2.0.
3 libcps aborted when enviornment variable OMP_NESTED
is set.
PHSS_25029:
SR 8606216202 / DTS JAGad85372:
1 Guided Scheduling does not scale pass 2x
2 There are missing routines to support aCC
OpenMP code.
3 There is a memory leak when running OpenMP
codes.
PHSS_24673:
The following symbols are missing from libcps.1
__HLO_out_cleanup, __HLO_out_lock,
__HLO_out_reduce_partials, __HLO_out_startup,
__HLO_out_tmp_file_flush, __HLO_out_unlock and
__HLO_out_write_results.
PHSS_24379:
Add support for OpenMP library routines for 11.11.
Defect Description:
PHSS_27700:
SR: 8606238742 CR: JAGae07765
omp begin/end loop and single code does not work in a
orphan recursion parallel region.
PHSS_27075:
SR: 8606241730 CR: JAGae08988
After a fork the child process can now
go parallel.
PHSS_26913:
1 Increase performance of OpenMP routines.
2 Added support for OpenMP V2.0.
3 Fixed abort when env variable OMP_NESTED
is set.
PHSS_25029:
SR: 8606216202 CR: JAGad85372
1 Fixed Guided scheduluing to scale better then 2x.
2 Add missing routines to support aCC OpenMP code.
3 Fixed memory leak problem when running OpenMP codes.
PHSS_24673:
Add the missing symbols to libcps.1.
PHSS_24379:
Add missing OpenMP support libraries for 11.11.
Enhancement:
Yes
PHSS_27700:
Both libcps and libomp have been enhance to increase
performance of the following internal constructs: OpenMP
locks and parallel support routines for OMP DO/FOR loops.
SR:
8606238742 8606241730 8606216202 8606208372
Patch Files:
CPS.CPS-32SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libcps.sl
/usr/lib/libcps.2
/usr/lib/libcps.1
/usr/lib/libcps.a
/usr/lib/libomp.sl
/usr/lib/libomp.1
/usr/lib/libomp.a
CPS.CPS-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libcps.sl
/usr/lib/pa20_64/libcps.2
/usr/lib/pa20_64/libcps.1
/usr/lib/pa20_64/libcps.a
/usr/lib/pa20_64/libomp.sl
/usr/lib/pa20_64/libomp.1
/usr/lib/pa20_64/libomp.a
CPS.CPS-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/include/spp_prog_model.h
/usr/include/cps.h
/usr/include/omp.h
what(1) Output:
CPS.CPS-32SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libcps.sl:
libcps.sl HP HPUX [pa32/32: Release 6.1.1]: Fri Aug
16 13:23:09 CDT 2002
/usr/lib/libomp.sl:
libomp.sl HP HPUX [pa32/32: Release 6.1.1]: Fri Aug
16 13:23:18 CDT 2002
/usr/lib/libcps.a:
libcps.a HP HPUX [pa32/32: Release 6.1.1]: Fri Aug 1
6 13:22:51 CDT 2002
/usr/lib/libomp.a:
libomp.a HP HPUX [pa32/32: Release 6.1.1]: Fri Aug 1
6 13:23:04 CDT 2002
/usr/lib/libcps.1:
libcps.sl HP HPUX [pa32/32: Release 6.1.1]: Fri Aug
16 13:23:23 CDT 2002
/usr/lib/libcps.2:
libcps.sl HP HPUX [pa32/32: Release 6.1.1]: Fri Aug
16 13:23:09 CDT 2002
/usr/lib/libomp.1:
libomp.sl HP HPUX [pa32/32: Release 6.1.1]: Fri Aug
16 13:23:18 CDT 2002
CPS.CPS-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libcps.sl:
libcps.sl HP HPUX [pa32/64: Release 6.1.1]: Fri Aug
16 13:23:48 CDT 2002
/usr/lib/pa20_64/libomp.sl:
libomp.sl HP HPUX [pa32/64: Release 6.1.1]: Fri Aug
16 13:23:58 CDT 2002
/usr/lib/pa20_64/libcps.a:
libcps.a HP HPUX [pa32/64: Release 6.1.1]: Fri Aug 1
6 13:23:35 CDT 2002
/usr/lib/pa20_64/libomp.a:
libomp.a HP HPUX [pa32/64: Release 6.1.1]: Fri Aug 1
6 13:23:44 CDT 2002
/usr/lib/pa20_64/libcps.1:
libcps.sl HP HPUX [pa32/64: Release 6.1.1]: Fri Aug
16 13:24:03 CDT 2002
/usr/lib/pa20_64/libcps.2:
libcps.sl HP HPUX [pa32/64: Release 6.1.1]: Fri Aug
16 13:23:48 CDT 2002
/usr/lib/pa20_64/libomp.1:
libomp.sl HP HPUX [pa32/64: Release 6.1.1]: Fri Aug
16 13:23:58 CDT 2002
CPS.CPS-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/include/spp_prog_model.h:
None
/usr/include/cps.h:
None
/usr/include/omp.h:
None
cksum(1) Output:
CPS.CPS-32SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
2927966733 184320 /usr/lib/libcps.sl
2816525984 49152 /usr/lib/libomp.sl
2802150393 198968 /usr/lib/libcps.a
2167501797 33968 /usr/lib/libomp.a
759470434 192512 /usr/lib/libcps.1
2927966733 184320 /usr/lib/libcps.2
2816525984 49152 /usr/lib/libomp.1
CPS.CPS-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
4286854720 202840 /usr/lib/pa20_64/libcps.sl
4251039834 43224 /usr/lib/pa20_64/libomp.sl
468661291 372714 /usr/lib/pa20_64/libcps.a
1311630673 65360 /usr/lib/pa20_64/libomp.a
3693574717 217504 /usr/lib/pa20_64/libcps.1
4286854720 202840 /usr/lib/pa20_64/libcps.2
4251039834 43224 /usr/lib/pa20_64/libomp.1
CPS.CPS-MIN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
2246408098 17798 /usr/include/cps.h
2717233737 3435 /usr/include/omp.h
2419712672 6499 /usr/include/spp_prog_model.h
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies:
9000/889/K460
9000/800/V2200
Other Dependencies: None
Supersedes:
PHSS_27075 PHSS_26913 PHSS_25029 PHSS_24673 PHSS_24379
Equivalent Patches:
PHSS_27699:
s700: 11.00 11.10
s800: 11.00 11.10
PHSS_27702:
s700: 11.22
s800: 11.22
Patch Package Size: 1590 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_27700
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27700.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27700. 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_27700.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_27700.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27700.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHSS_27700------------------------------------------
Document ID: PHSS_27699
Date Loaded: 20020905
Title: s700_800 11.X CPSlib Cumulative Patch (OMP V2.0 for 11.x)
Patch Name: PHSS_27699
Patch Description: s700_800 11.X CPSlib Cumulative Patch (OMP V2.0 for 11.x)
Creation Date: 02/08/14
Post Date: 02/09/05
Hardware Platforms - OS Releases:
s700: 11.00 11.10
s800: 11.00 11.10
Products: N/A
Filesets:
CPS.CPS-32SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
CPS.CPS-32SLIB,fr=B.11.10,fa=HP-UX_B.11.10_32/64,v=HP
CPS.CPS-64SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
CPS.CPS-64SLIB,fr=B.11.10,fa=HP-UX_B.11.10_32/64,v=HP
CPS.CPS-MIN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
CPS.CPS-MIN,fr=B.11.10,fa=HP-UX_B.11.10_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical:
No (superseded patches were critical)
PHSS_25028: MEMORY_LEAK
Category Tags:
defect_repair enhancement general_release critical
memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_27699
Symptoms:
PHSS_27699:
SR 8606238742 / DTS JAGae07765:
Nested OpenMP do/for loops can cause programs to
abort in the right cases.
PHSS_27074:
SR 8606241730 / DTS JAGae08988:
OMP program won't go parallel in a child process
after a fork call.
PHSS_26912:
1 OpenMP support routines are slow
2 Need support for OpenMP V2.0.
3 libcps aborted when enviornment variable OMP_NESTED
is set.
PHSS_25028:
SR 8606216202 / DTS JAGad85372:
1 Guided Scheduling does not scale pass 2x.
2 There are missing routines to support aCC
OpenMP code.
3 There is a memory leak when running OpenMP codes.
PHSS_24672:
The following symbols are missing from libcps.1
__HLO_out_cleanup, __HLO_out_lock,
__HLO_out_reduce_partials, __HLO_out_startup,
__HLO_out_tmp_file_flush, __HLO_out_unlock and
__HLO_out_write_results.
PHSS_24378:
Add support for OpenMP library routines for 11.00/11.10.
PHSS_22177:
1. Unnamed critical sections abort at runtime with an
internal CPS fatal error.
2. Added missing symbol cps_set_thread_.
PHSS_17116:
Poor parallel performance when the application is
processing signals.
PHSS_15914:
Poor parallel application performance when using +FDP
linker option.
PHSS_14149:
1. This patch fixes a class of wrong answer bugs
associated with parallel applications.
2. Fixed use of size_t in spp_prog_model.h.
3. Fixed cps_set_threads to work correctly.
Defect Description:
PHSS_27699:
SR: 8606238742 CR: JAGae07765
omp begin/end loop and single code does not work in a
orphan recursion parallel region.
PHSS_27074:
SR: 8606241730 CR: JAGae08988
After a fork the child process can now
go parallel.
PHSS_26912:
1 Increase performance of OpenMP routines.
2 Added support for OpenMP V2.0.
3 Fixed abort when env variable OMP_NESTED
is set.
PHSS_25028:
SR: 8606216202 CR: JAGad85372
1 Fixed Guided scheduluing to scale better then 2x.
2 Add missing routines to support aCC OpenMP code.
3 Fixed memory leak problem when running OpenMP codes.
PHSS_24672:
Add the missing symbols to libcps.1.
PHSS_24378:
Add missing OpenMP support libraries.
PHSS_22177:
Fixed unnamed critical sections abort at runtime with an
internal CPS fatal error and missing symbol
cps_set_threads_.
PHSS_17116:
Suspended threads when processed signals, would not
resuspend themselves, but would spin wait for work.
PHSS_15914:
Child threads where not inheriting parent thread floating
point status register on thread creation.
PHSS_14149:
Bug in cps_set_threads() causes loop_parallel directive
to fail.
Enhancement:
Yes
PHSS_27699:
Both libcps and libomp have been enhance to increase
performance of the following internal constructs: OpenMP
locks and parallel support routines for OMP DO/FOR loops.
SR:
8606238742 8606241730 8606216202 8606208372
Patch Files:
CPS.CPS-32SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
CPS.CPS-32SLIB,fr=B.11.10,fa=HP-UX_B.11.10_32/64,v=HP:
/usr/lib/libcps.sl
/usr/lib/libcps.2
/usr/lib/libcps.1
/usr/lib/libcps.a
/usr/lib/libomp.sl
/usr/lib/libomp.1
/usr/lib/libomp.a
CPS.CPS-64SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
CPS.CPS-64SLIB,fr=B.11.10,fa=HP-UX_B.11.10_32/64,v=HP:
/usr/lib/pa20_64/libcps.sl
/usr/lib/pa20_64/libcps.2
/usr/lib/pa20_64/libcps.1
/usr/lib/pa20_64/libcps.a
/usr/lib/pa20_64/libomp.sl
/usr/lib/pa20_64/libomp.1
/usr/lib/pa20_64/libomp.a
CPS.CPS-MIN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
CPS.CPS-MIN,fr=B.11.10,fa=HP-UX_B.11.10_32/64,v=HP:
/usr/include/spp_prog_model.h
/usr/include/cps.h
/usr/include/omp.h
what(1) Output:
CPS.CPS-32SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/libcps.sl:
libcps.sl HP HPUX [pa32/32: Release 6.1.1]: Fri Aug
16 13:23:09 CDT 2002
/usr/lib/libomp.sl:
libomp.sl HP HPUX [pa32/32: Release 6.1.1]: Fri Aug
16 13:23:18 CDT 2002
/usr/lib/libcps.a:
libcps.a HP HPUX [pa32/32: Release 6.1.1]: Fri Aug 1
6 13:22:51 CDT 2002
/usr/lib/libomp.a:
libomp.a HP HPUX [pa32/32: Release 6.1.1]: Fri Aug 1
6 13:23:04 CDT 2002
/usr/lib/libcps.1:
libcps.sl HP HPUX [pa32/32: Release 6.1.1]: Fri Aug
16 13:23:23 CDT 2002
/usr/lib/libcps.2:
libcps.sl HP HPUX [pa32/32: Release 6.1.1]: Fri Aug
16 13:23:09 CDT 2002
/usr/lib/libomp.1:
libomp.sl HP HPUX [pa32/32: Release 6.1.1]: Fri Aug
16 13:23:18 CDT 2002
CPS.CPS-64SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/lib/pa20_64/libcps.sl:
libcps.sl HP HPUX [pa32/64: Release 6.1.1]: Fri Aug
16 13:23:48 CDT 2002
/usr/lib/pa20_64/libomp.sl:
libomp.sl HP HPUX [pa32/64: Release 6.1.1]: Fri Aug
16 13:23:58 CDT 2002
/usr/lib/pa20_64/libcps.a:
libcps.a HP HPUX [pa32/64: Release 6.1.1]: Fri Aug 1
6 13:23:35 CDT 2002
/usr/lib/pa20_64/libomp.a:
libomp.a HP HPUX [pa32/64: Release 6.1.1]: Fri Aug 1
6 13:23:44 CDT 2002
/usr/lib/pa20_64/libcps.1:
libcps.sl HP HPUX [pa32/64: Release 6.1.1]: Fri Aug
16 13:24:03 CDT 2002
/usr/lib/pa20_64/libcps.2:
libcps.sl HP HPUX [pa32/64: Release 6.1.1]: Fri Aug
16 13:23:48 CDT 2002
/usr/lib/pa20_64/libomp.1:
libomp.sl HP HPUX [pa32/64: Release 6.1.1]: Fri Aug
16 13:23:58 CDT 2002
CPS.CPS-MIN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/include/spp_prog_model.h:
None
/usr/include/cps.h:
None
/usr/include/omp.h:
None
cksum(1) Output:
CPS.CPS-32SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
2927966733 184320 /usr/lib/libcps.sl
2816525984 49152 /usr/lib/libomp.sl
2802150393 198968 /usr/lib/libcps.a
2167501797 33968 /usr/lib/libomp.a
759470434 192512 /usr/lib/libcps.1
2927966733 184320 /usr/lib/libcps.2
2816525984 49152 /usr/lib/libomp.1
CPS.CPS-64SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
4286854720 202840 /usr/lib/pa20_64/libcps.sl
4251039834 43224 /usr/lib/pa20_64/libomp.sl
468661291 372714 /usr/lib/pa20_64/libcps.a
1311630673 65360 /usr/lib/pa20_64/libomp.a
3693574717 217504 /usr/lib/pa20_64/libcps.1
4286854720 202840 /usr/lib/pa20_64/libcps.2
4251039834 43224 /usr/lib/pa20_64/libomp.1
CPS.CPS-MIN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
2246408098 17798 /usr/include/cps.h
2717233737 3435 /usr/include/omp.h
2419712672 6499 /usr/include/spp_prog_model.h
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies:
9000/889/K460
9000/800/V2200
Other Dependencies: None
Supersedes:
PHSS_27074 PHSS_26912 PHSS_25028 PHSS_24672 PHSS_24378 PHSS_22177
PHSS_17116 PHSS_15914 PHSS_14149
Equivalent Patches:
PHSS_27700:
s700: 11.11
s800: 11.11
PHSS_27702:
s700: 11.22
s800: 11.22
Patch Package Size: 1600 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_27699
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27699.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27699. 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_27699.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_27699.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27699.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHSS_27699------------------------------------------
Document ID: PHSS_27680
Date Loaded: 20020905
Title: s700_800 11.X OpenMail B.07.00 September 02 Periodic Patch
Patch Name: PHSS_27680
Patch Description: s700_800 11.X OpenMail B.07.00 September 02 Periodic Patch
Creation Date: 02/08/16
Post Date: 02/09/05
Hardware Platforms - OS Releases:
s700: 11.00 11.04 11.11
s800: 11.00 11.04 11.11
Products:
OpenMail B.07.00
Filesets:
OpenMail.OM-ADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-AMECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-AMEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-AMEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-AMEPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-APPL,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-BB,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-CHSCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-CHSICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-CHSPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-CORE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-DESK,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-DSYNC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-ENGCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-ENGICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-ENGPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-ENGPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-FINCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-FINICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-FINPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-FRECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-FREICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-FREPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-GERCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-GERICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-GERPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-IMAP4,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-ITACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-ITAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-ITAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-KORCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-KORICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-KORPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-LC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-LDAP,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-MAN,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-NIPCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-NIPICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-NIPPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-PMOVER,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-POP3,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-PTBCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-PTBICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-PTBPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-RC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-SMS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-SPACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-SPAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-SPAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-SWECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-SWEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-SWEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-UNIX,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-WEBADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
OpenMail.OM-X400,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_27680
Symptoms:
PHSS_27680:
CR: JAGad71050 SR: 8606201876
Symptoms: Downloaded quoted-printable .CSV (Comma Separated
Values) file attachment to PC is missing carriage returns.
Despite it being perfectly acceptable to MS Excel.
Problem: OM does not know that .CSV files are really text
files and therefore they need their newlines uprated to
CRLF on PCs.
CR: JAGae07887 SR: 8606238864
omcpinu with the '-e' option fails to correctly merge
folders whose names contain multibyte data.
CR: JAGae18540 SR: 8606254208
The check_relay feature of sendmail does not work when
sendmail is invoked from omredirtcp.
CR: JAGae24659 SR: 8606260336
The "man" page for omupdtis etc. gives the directory path
containing the Item Structure Server database (default or
otherwise) as "/var/opt/openmail/dir/../is/" in 3 places.
Although this is correct, it is not clear to the reader
that the UNIX directory convention of "../" is being used
here to mean "the parent of".
This is confusing and prone to be misinterpreted.
CR: JAGae24724 SR: 8606260401
OpenMail does not support sendmail on AIX 5.1L. The
sendmail.cf file is in a different location compared with
AIX 4.x. In addition, omrc needs to check file permissions
when sendmail versions later than 8.9 are in use.
CR: JAGae26104 SR: 8606261785
The autotests imap_JAGae15283.u and imap_JAGae12028.u fail
about 80% of the time on Linux because they run "StartSvc
imap" immediately after "StopSvc imap" and the imap daemon
fails to start.
On HPUX11, running omoff -s imap followed by omon -s imap,
several times in quick succession causes the state of the
imap to fail to start properly.
CR: JAGae27170 SR: 8606262840
When Bulletin Board changes are being synchronised - if a
basic item (i.e. message content rather than a whole
message) is added to a Bulletin Board and then deleted in
the same email client session the ADD will be synchronised
but the DELETE will not be.
CR: JAGae31209 SR: 8606266965
omredirtcp sometimes cannot be restarted. It either fails
silently or writes a "bind failed: Address already in use"
error message to the syslog.
CR: JAGae32060 SR: 8606267820
Some messages from Exchange to OpenMail contain
incorrectedly encoded WINMAIL.DAT attachments. This illegal
encoding can cause the unix.in process to abort with a
segmentation violation. (This is another example of the
problem described in JAGad95079.)
CR: JAGae32230 SR: 8606267991
Mime Browser Controller terminates, without logging, when a
client connection, ual.remote, goes away between requesting
a browse and getting the reply.
This most likely occurs when some user stops browsing in
the midstream, on a heavily loaded system; maybe closing
his client.
Mime Browser Controller then chooses to terminate itself
rather than service all the other many connections.
CR: JAGae32345 SR: 8606268107
When a large number of users are connected to OpenMail on a
machine running RedHat Linux, there are memory management
problems resulting in segmentation violations and other
errors.
CR: JAGae33094 SR: 8606268859
A message with a "Mail from" command containing a
comment-only email address coming into OpenMail via the
Internet gateway causes a message with no originator to be
generated. If this message is routed via the X.400 gateway
it is rejected as an originator is a mandatory field.
CR: JAGae33310 SR: 8606269075
When the outbound Internet gateway processes a message that
contains recipients on both the TNEF and MIME routes the
steering file used may be either the MIME one
(~openmail/sys/mimeout.str) or the TNEF one
(~openmail/sys/tnefout.str) depending on the order of the
recipients. The message should be split in this case and
the appropriate steering file used for each type of
recipient.
CR: JAGae33867 SR: 8606269632
Using PC Admin new PDL members cannot be successfully
added. An OM16095 error is reported:
"Illegal attribute type within compound value."
The PDL member can be added successfully using the backend
OpenMail 'omaddpdln' command.
CR: JAGae35717 SR: 8606271509
On AIX 5.1L, the omrc command may give incorrect '[OM
10350] Warning: File system is full' messages. The message
does not state which file system is meant to be full.
CR: JAGae36951 SR: 8606272845
A message from an Internet user with a non-ASCII comment in
his name cannot be successfully replied to when using the
Outlook client. The reply is rejected at the Internet
gateway with a 'Name cannot be mapped' error. A
non-delivery report is returned. The same message can be
successfuly replied to with the OMGUI client.
PHSS_27062:
CR: JAGad38110 SR: 8606168832
The Web Clients create temporary files under /var/tmp which
may have world-writable permissions, and always have
world-readable permissions.
CR: JAGae05328 SR: 8606236267
omtclsh (used within the webadmin interface) could hang on
Linux RedHat 7.2
CR: JAGae12028 SR: 8606245558
Using an IMAP client to copy/move a message from a local
folder to an OpenMail folder leaves the new message with
the user running the IMAP session as the message creator
and an incorrect received date.
This is only a problem if a non-IMAP client is subsequently
used to read the message.
CR: JAGae12031 SR: 8606245561
Using the ICE web client to log on to Openmail - as soon as
you select a button or click on something in the Main Menu
you get the logon page again with a SESSION EXPIRED error
message.
CR: JAGae17136 SR: 8606251070
Handling of the SIGCLD (SIGCHLD) interrupt changed at Dec.
2000 to make the code suitable for both SystemV and BSD
unix variants. However this change has caused some problems
now that the death of a child process is not ignored. These
problems include:
1. ual.remote zombie process accumulating.
2. scripts no longer executable from TCL within web client
page templates.
3. omredirtcp not invoking sendmail successfully in some
circumstances.
CR: JAGae18238 SR: 8606253906
When a new password is supplied as a result of an old
password being either expired or pre-expired by the
administrator the new password is not checked against any
password composition rules set using omconfpwd. (This
problem only occurs with OpenMail B.07.00)
CR: JAGae19347 SR: 8606255018
It is not possible to configure the Internet gateway to
produce simple inline RTF content without associated
filename information. This filename info. often causes
email clients to treat the RTF as an attachment.
Configuration for this feature is possible when a
multipart/alternative MIME structure is being generated.
However a Content Disposition of 'inline' isn't
configurable for a simple (non-multipart/alternative)
content unless a 'filename' attribute is added as well.
CR: JAGae22300 SR: 8606257997
When the Internet Gateway is configured to use the content
T.61 subject as the MIME 'filename' a long T.61 subject can
cause a Segmentation Violation in unix.out.
CR: JAGae22536 SR: 8606258235
A badly formed RCPT TO: address of the form:
";"dept.acme.com
results in a looping unix.in process.
CR: JAGae23835 SR: 8606259517
This is a problem in B.07.00 only
When the IMAP_AUTOMATIC_MDN tweak is set to TRUE, the
server does not automatically generate read
acknowledgements.
PHSS_26278:
CR: JAGad84900 SR: 8606215723
The individual X.400 printable string attributes of a mail
address, of all ORNs within a message, are being truncated
to the size limits imposed by the X.400 Standard, by the
incoming Internet Gateway.
This can cause confusing and incomplete addresses in the
ORN, particularly in the fields holding the Internet
address.
CR: JAGad95079 SR: 8606226007
Some messages from Exchange to OpenMail contain
incorrectedly encoded WINMAIL.DAT attachments. This illegal
encoding can cause the unix.in process to abort with a
segmentation violation.
CR: JAGad97183 SR: 8606228125
When a Service Router rule is set up to REJECT a message
using the RECIPIENT-SERVICE-LEVEL criterion the
non-delivery notification (NDN) generated incorrectly
specifies the NDN reason as "Mailbox exceeds size limit".
The correct text should be:
"The message could not be delivered to the recipient as the
service level for their mailbox doesn't allow that
operation".
CR: JAGad97593 SR: 8606228536
With Portal Access enabled, when a duplicate username is
entered, the ICE Web Client 6.0 user program should display
the Duplicate Usernames page containing a list of
alternative names from which to pick the correct name.
When used with a Web Client 5.10 profile, this list of
alternative names is not displayed and the Duplicate
Usernames page stalls at this point: Please select an
alternative from:
At GR6, the Duplicate Usernames page is not even displayed
at all; the Logon page remains without any feedback that
something is amiss.
CR: JAGad98210 SR: 8606229157
general.cfg setting UAL_LOCAL_IGNORE_PASSWORD=TRUE does not
work with GR7. If set a password is still required for
local UAL clients (e.g omlist) that are run within the
mailbox user's unix logon.
CR: JAGae02798 SR: 8606233575
For some IMAP clients (e.g. Outlook Express) the date of
messages in a sub-folder is the date the message was copied
to the folder rather than the date the message was
received.
CR: JAGae03973 SR: 8606234784
There is a problem with omlogon and omlogoff on Linux.
If the omlogoff command is issued to terminate a user
session, followed by a omlogon command to start a new
session, the omlogon is not always successful. The omlogon
is able to recognise that there is no other user session
running, and so doesn't fail to start. However, it then
terminates the session which was starting, so that further
commands such as omlist expect a username and password to
be provided.
If the omlist is part of an autotest, the test will hang
until a password is manually provided.
The problem does not occur if a sleep is placed between the
omlogoff and the next omlogon.
CR: JAGae03977 SR: 8606234788
If a ualth.sck call is made followed by a omlogon, then the
omlogon call may fail.
This failure seems to be intermittent - 50% of the time
approx and only occurs on Linux RedHat 7.2. It is
predominently a timing problem which goes away if a sleep
is places between the 2 calls when part of an autotest.
CR: JAGae06468 SR: 8606237428
omdosur fails with the error message "(OM 24602) Cannot
create file"
CR: JAGae07450 SR: 8606238426
The first mailnode created on a system is not always made
the Primary Mailnode. Shown by absence of '**' in omshowmn
output.
Virtual Licensing assumes that this mailnode to be the
Primary Mailnode, which it needs to refer to.
As a result, Virtual License Server crashes, with
Segmentation Violation, when trying to grant licenses that
have been requested but not yet granted.
May occur during start-up if the request was made while the
system is shut down, or at the time of the request if
system is up.
PHSS_25648:
CR: JAGad83534 SR: 8606214343
If an auto-redirect is enabled for a users inbox, then all
other auto- actions are excluded from execution for that
mailbox.
CR: JAGad83915 SR: 8606214723
If, when creating an auto-forward rule using the PAW-client
the user deletes the auto-forward covering text, local
delivery fails to forward the message.
CR: JAGad83932 SR: 8606214740
B.06 and B.07
This concerns the UAL Checklist command, when the flag is
set to search the directory on the internet-addr (167)
attribute.
When more than one match is found, the command does not
return the entries found as alternatives. This is unlike
UAL Checkname, which does.
This affects the OMGUI, for example. When entering the
duplicate internet address into a DL, the behaviour varies
depending on whether the Auto Name Checking option is on.
If on, Checkname is used, and you see the X400 attributes
of the entries. If off, you get an error when the message
is Mailed. When you click on the name in error, you get a
message that no alternatives can be displayed, or else you
get an empty box that is supposed to show the alternatives.
CR: JAGad84893 SR: 8606215716
If a message that contains an ORN with a DDVn field greater
than the maximum 128 bytes, the X400 outgoing gateway
correctly rejects this message, and will generate a
non-delivery if appropriate.
If the message is a return of contents (the normal type of
non-delivery), then all subsequent messages that are not
return of contents will be rejected by the gateway. An
error 6019 appears in the omshowlog output for each
rejected message.
After a number of the 6019 errors (200 at most), the
gateway will abort, with log output showing 'too many
transaction files open'.
CR: JAGad84922 SR: 8606215745
If no auto-reply text is provided for an auto-reply rule,
then local delivery fails to send the auto-reply message.
CR: JAGad87535 SR: 8606218386
B.07: omtidyu -B alters the last signon time of the user.
In previous releases it did not.
CR: JAGad87649 SR: 8606218500
Using the Outlook client delegate permissions cannot be set
if the delegate has the Common Name (CN) attribute set. An
error is displayed in the Outlook interface.
CR: JAGad88671 SR: 8606219531
When the X400 outgoing gateway processes a message with a
non-textual content item, and with GENERATE_FTPBP=TRUE in
the ~sys/madmd.cfg file, x400.hpx.out leaks approximately
4Kbytes of memory on the message.
The workaround is to stop and start the X400 gateway
periodically, before the process fails with insufficient
memory.
CR: JAGad88889 SR: 8606219749
IMAP: rereading messages with many attachments can result
in raw base64 encoded information being displayed.
CR: JAGad89888 SR: 8606220752
Signatures which include 8-bit text will appear corrupted
when added to the message body using the B.07.00 ICE
client.
CR: JAGad90057 SR: 8606220921
An Internet Ack which contains a NULL character will cause
unix.in to fail.
CR: JAGad90490 SR: 8606221356
Reading Non-Delivery Notifications for a non-english user
(e.g. German) using an IMAP cleint (e.g. Netscape
Navigator) gives text where the accented characters (e.g.
umlaute) are displayed incorrectly.
CR: JAGad90761 SR: 8606221627
Failure to check if enough memory is available before doing
a write results in the corruption of the shared memory used
by the notification server. The result of this is that
local delivery and UAL remote abort.
CR: JAGad91276 SR: 8606222161
omupdtis does not return an error result when interrupted.
CR: JAGad93282 SR: 8606224187
The unix.out gateway, when processing tnef routed messages,
should generate IDs for Mapi Named Properties, in the range
8000-FFFE. The gateway increments the ID each time that a
named property is processed, generating IDs like 80000003,
8001000b, 80020003....
If the gateway runs for some time, the Named Property IDs
become undefined, once FFFE has been reached.
CR: JAGad93317 SR: 8606224222
The audit log only contains entries for successful signons.
At B.06 unsuccessful signons (e.g. password wrong) were
logged to the audit file with an indication of the signon
error.
CR: JAGad94573 SR: 8606225486
When connecting to the OpenMail message store via the Web
Client 5.10 on a Virtual Vault machine with the portal
access disabled, the error message "cannot connect to the
specified host" is displayed.
CR: JAGad94888 SR: 8606225815
The OpenMail daemons omvvrelay, ompop3, omimap and omportal
(B.06.00) cannot be started or stopped manually by root in
a VirtualVault 4.5 environment, due to root not having
sufficient authorisation.
CR: JAGad95463 SR: 8606226394
This applies to B.06 and B.07 of the Openmail Server. See
also JAGad 94299, against the MAPI Service Providers.
With the outgoing internet tnef gateway configured to
convert rtf to text (tnefout.str), and with the
/var/opt/openmail/sys/general.cfg option
UXO_NO_RETAIN_IF_CONVERTED=TRUE set,
1) In Outlook/OpenMail begin to create a 'New Message'.
2) Add a Subject, an Exchange users name and some message
text to the body.
3) Save and close the message.
4) Open message; add some more text and send it to the
Exchange user.
5) The Exchange user receives a message with a blank
message body.
PHSS_24876:
CR: JAGad30137 SR: 8606160818
OpenMail B.06.00.00 + MayPP00
unix.in might hang and a message queued on the sendmail
queue when the message contains one part only, which is a
distribution list.
Workaround: Prior to sending the DL, add some text in the
body part of the message.
CR: JAGad31466 SR: 8606162150
One-way disrsync agreement between OpenMail and Exchange
(over OMEXCONN). Updates are done on the Exchange server.
When modifying attributes 111 and PHONE-1, then the next
dirsync results in the full loss of tis modified entry
within the OM directory. (However, the next dirsync cycle
will add the corrected entry again).
CR: JAGad49568 SR: 8606180347
Defining more than one sender name on the omtidyu
command-line makes omtidyu substitute the last defined name
as all defined names.
For example:
omtidyu -B -u "daniel wink" -R -T i -n -w "gren elliot" -n
-w "iain parker"
will return :
CRITERIA : Messages in the InTray NOT matching "iain parker
" in SENDER field AND NOT matching "iain parker " in SENDER
field.
CR: JAGad65896 SR: 8606196695
HPUX 11.x - 10.x
Openmail 6.0 Dec '00 PP
The incoming internet gateway, unix.in, loops if supplied
with a bad RCPT_TO or Arpa ORN that contains more than one
sign.
For instance,
To:
_//org/co/admd/prmd////RFC-822/ppinetia.coma.b.c
CR: JAGad67601 SR: 8606198411
Message with a large distribution list (thousands of
recipients) can take a long, long time to pass through the
X.400 gateway (from OpenMail to X.400).
CR: JAGad68810 SR: 8606199624
omshowcda -d <dir_name> displays the mask used to extract
directory entries. The format of this mask changed with GR6
PP-Mar. It used to be:
S/G/I
and now it is:
S=/G=/I=
This will also occur for other directory related commands
that display attribute masks.
CR: JAGad69036 SR: 8606199850
WC6.0 and PAW corrupts the autoreply covering text in the
languages Japenese, Korean and simplified Chinese when the
rule is listed. The covering text is not corrupted when
viewed from within the auto-replied message.
CR: JAGad69543 SR: 8606200362
Occasionally some message body parts, which require base 64
mime encoding, cause the item.browse binary to perform a
segmentation violation. This occurs when a user attempts to
read the message from the intray or folder area using an
IMAP client (Netscape communicator).
CR: JAGad70640 SR: 8606201464
Some scripts included in the OM-APPL component assume that
the 'cut' command is located in /usr/bin. In RedHat 7.1,
'cut' is located in /bin. The scripts affected are
omaddapp, omaddapppdl, omaddapppdln, omdelapp, omdelapppdl,
omdelapppdln, omshowapp, omshowapppdl and omshowapppdln.
CR: JAGad70641 SR: 8606201465
During installation of patch PHSS_23491 the script vvice
attempts to create the directory
/var/opt/openmail/temp/vv_bkp_log and fails. The directory
/var/opt/openmail/temp has the sensitivity label "SYSTEM
INSIDE" and the vvice script is executed from within the
"SYSTEM" environment and therefore does not have
sufficient privileges to perform the operation.
During installation of the patch PHSS_23491, vvsync
attempts to copy the portal.daemon and kill.portal binaries
from /opt/openmail/bin to the CHROOTED bin directory and
fails. These binaries do not form part of the OpenMail
B.07.xx.xx components and therfore are not present in the
OpenMail bin directory.
During installation of the patch PHSS_23491, user
configurable settings are not retained in the general.cfg
CR: JAGad71090 SR: 8606201916
Web Client 6.0 may, under certain cirumstances, display the
incorrect item count when listing items in the tray areas
or the folder areas.
CR: JAGad71959 SR: 8606202785
Clear/signed S/MIME message sent into OpenMail via Internet
g/w cannot be browsed by IMAP client. The multipart/signed
part of the message is empty.
The message can be successfully read by the OMGUI client.
CR: JAGad74578 SR: 8606205403
Some messages that have come from the internet contain
attachments that cannot be opened when using an IMAP client
(eg. Internet Explorer or Netscape).
Typically these are messages that only contain an
attachment and no covering text, but other types of message
structure may also suffer from this problem.
The user typically sees a copy progress bar that just
stops, the transfer of the attachment does not complete.
The format of attachment within the MIME message is not
correct - it should be base64 and in fact the data is
unencoded.
CR: JAGad74715 SR: 8606205540
This applies to B.06.00.00 and B.07.00.00
Use of ldapmodify to replace the mhsORAddress or omAddress
attributes does not work if attempting to replace existing
individual attributes, other than S, S-TX, G and G-TX.
For instance, if the entry for S=user111 has an OU1
configured, then
# ldapmodify -L UTF8-N -D "cn=clim, o=Openmail" -v
dn: cn=user111, o=OpenMail
changetype: modify
replace: mhsORAddresses
mhsORAddresses: S=user111/ou1=japan3
gives
ldap_modify: Operations error
ldap_modify: additional info: [OM 16092] An attribute has
multiple values, but is notconfigured as multi-value.
Parameter : Directory Entry Modifier
Attribute : OU1Max allowed size : 32
Required syntax : PRINTABLE-STRING
The error can also be seen on the server side, on the
omslapd debug output.
The recommended method is to use ldapmodify to modify the
individual attributes explicitly.
For instance, the input to ldapmodify would be
dn:...
changetype: modify
replace: 5
5: <new_OU1_value>
The internal names of the OU<n> attributes are used as they
are not mapped by default in the ~openmail/sys/ldap.attribs
file. Mappings could of course be added to this file, so
that more meaningful tags could be used in ldapmodify.
CR: JAGad75038 SR: 8606205863
Directory entries added using omaddent that contain
OCTET-STRING attributes have octets with certain values
stripped out. ommodent shows the same problem.
The FREEBUSY directory attributes used by Outlook FreeBusy
lookup are examples of OCTET-STRING data. A situation where
the FREEBUSY attributes may become incorrect is when
omdiropt is run on the FREEBUSY directory. This is because
omdiropt uses omaddent.
Octet 014 (14 decimal) is one value that gets stripped.
There may be some other values.
CR: JAGad75517 SR: 8606206344
The problem is seen on Linux with OM 7 only.
The problem is that issuing a valid IMAP command causes the
IMAP4 server to crash, which should not happen.
With the test mailbox, issuing the commands:
. login "username" "password"
. select inbox
. fetch 2 (BODY.PEEK[3.HEADER.FIELDS (Resent-Date)])
causes the crash.
CR: JAGad75975 SR: 8606206802
An address list, such as a TO: field, may be corrupted if
it contains a quote character ("). This occurs because of
the way that sendmail converts the address and OpenMail
subsequently parses it. In the following text, # is used to
represent the <backslash> character.
If an entry has the format #", then sendmail quotes it and
adds an extra <backslash> to the #" sequence.
So us#"er <user.local>, becomes to "us##"er" <user/local>,
OpenMail then splits up the address list using commas as
the separator. If a separator is in a quote, it is ignored.
In the above example, the quote after the ## is taken to be
a closing quote. This means that things get out of sync, as
the last quote is taken to be an opening, rather than
closing, quote and the address list becomes mangled.
In addition, the mangled address list may now contain
entries in excess of 1024 characters. This can cause a
fatal error.
CR: JAGad79081 SR: 8606209895
Certain printable chars may be used in the components, e.g.
Surname, of OM Personal Names, but should be represented by
special characters on input (see man page omattribs). Such
a char is that 'space' should be input as '_' to allow for
Surnames like "Van Gogh".
IMAP makes no allowance for this mapping, and so fails to
login because the username as input does not exist as an OM
user.
CR: JAGad80029 SR: 8606210842
OpenMail may fail to configure auxiliary child processes
correctly when using the omsetscv command. This results in
the child processes not terminating via the omshut command.
CR: JAGad83734 SR: 8606214543
This applies to B.07, when configured to allow duplicate
internet addresses in the directory. This is the default
for servers upgraded from an earlier version of OpenMail,
but not for new B.07 installations.
Using OMGUI to send a message, if an internet name is
entered that is in the OpenMail system directory twice and
the Dist. List is checked then a System Error 2 is
generated and the connection is lost (the UAL session is
terminated). This only occurs if individual name checking
is turned off.
This is caused by an error in the UAL Checklist command,
when attempting to return the duplicate entries as
alternatives. Note that, prior to B.07, UAL CheckList did
not actually return alternatives when searching on the
internet address field.
See also the related CR JAGad 83932, which is not planned
for fixing in the September 2001 Periodic Patch.
PHSS_23491:
CR: JAGab39939 SR: 8606100957
Omfmtent -u creates output that is corrupted. This occures
when an attribute name is specified and the attribute value
is not. The format of the output is incorrect because it
lists the attribute name but assigns no value to it making
the output unusable in scripts.
ie:
Input to omfmtent :
s=kessler/i=c/g=richard/q=/ou1=hdqt
Output of omfmtent :
1=kessler/3=c/2=richard/4/5=hdqt
As you can see by the above example, the output from the
omfmtent command is missing an "=" after the 4.
CR: JAGab68963 SR: 8606102906
The new server feature of REPEAT REMINDERS in the OMGUI and
MOB GUI do not stop sending out reminders after the Expiry
date.
CR: JAGad31664 SR: 8606162348
Can't reply in OMGUI and ccMail to messages from internet
whose address has comments.
CR: JAGad35090 SR: 8606165799
If 2 OpenMail users have the same name (but different
mailnodes) Single User Restore sometimes selects the wrong
message store to be restored.
CR: JAGad40563 SR: 8606171299
The web clients do not work with HTTPS and the Apache web
server.
When the user tries to signon they are presented with the
following message:
Bad Request
Your browser sent a request that this server could not
understand.
Reason: You're speaking plain HTTP to an SSL-enabled server
port.
CR: JAGad41471 SR: 8606172211
The UAL sometimes aborts on Redhat 7.0 systems when using
the directory relay service, with the following in the
OpenMail log:
SERIOUS ERROR Remote Client (U/I Access) 11.30.00 07:47:57
[OM 10250] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 28277;
code = 0. Procedure trace follows:
-> pc_recv_logical_block
<- pc_recv_logical_block
<- pc_recvmessage
-> ual_SendMessage
<- ual_SendMessage
-> ual_RecvReply
-> ual_GetFreeBusyTime
-> ual_ConvORNCheck
-> ual_ConvertORN
-> ual_GetUserCharSet
<- ual_GetUserCharSet
<- ual_ConvertORN
<- ual_ConvORNCheck
-> ual_GetUsersHost
-> nm_ParseORN
<- nm_ParseORN
User Name: UAL TestUser2 / Test, UAL
Pid of logging process: 28277
CR: JAGad42968 SR: 8606173711
It is possible using Outlook with a MAPI connection to
OpenMail to send a message with an internet address
containing 8-bit characters in the domain name.
The outgoing Internet Gateway discards these domain names,
causing an attempt to be made to deliver the message to a
recipient with the same address but no domain name.
This is not correct: if an address is invalid, message
delivery should not be attempted to a partial address in
this manner, as there are potential privacy issues.
CR: JAGad43052 SR: 8606173797
When a message with accented characters in the subject is
copied across message stores using Netscape messenger, the
subject of the message has the MIME character set specifier
in it when viewed using omcontain, OMGUI, Outlook. The
subject appears OK when using Netscape Messenger.
CR: JAGad44030 SR: 8606174784
Openmail does not have a converter from unicode to IA5, but
it does have one from unicode to ISO8859_1.
When the item browser is used to display a text message
using the default format, it has no problem in displaying
the message if OM_DEF_USER_CHAR is set to ISO8859_1 in the
configuration file.
However, if OM_DEF_USER_CHAR is set to IA5, then the item
browser isn't able to do the conversion and reports an
error. As the error reported in the log file was that a
character set conversion between MIME-UTF8 and IA5 was
failing, then this is probably the case.
The second problem is the way that the item browser
displays the message in MIME format.
Adding the mapping of UTF-8 to UTF8 in the mime.cs file
means that the character set for the message is now UTF8
which is recognised by OpenMail and the message is
correctly displayed on most clients. However, for Netscape
Messenger, which uses the item browser MIME option, there
is a problem.
The steering file ~sys/brwmime.str specified that generally
character sets should be converted to ISO8859_1 unless
otherwise specified. This means that the item browser
attempts a conversion from UTF8 to ISO8859_1 and fails.
It should be noted that UNICODE is not generally supported
on OpenMail when messages are in the MIME format.
CR: JAGad45429 SR: 8606176189
When using PAW and Web Client 6.0 rule names may be
displayed incorrectly in Korean, Japanese and Simplified
Chinese versions. This may cause the browser to hang.
CR: JAGad45449 SR: 8606176209
Outlook OFS: Item created offline and synced, and then
modified offline but synced online causes a duplicate to be
created.
CR: JAGad45880 SR: 8606176642
The IMAP/item.browse aborts with a segmentation violation
on LINUX, when trying to encode an html attachment into
"Quoted-Printable" format.
CR: JAGad46439 SR: 8606177205
For an OpenMail server that is configured to support
Czech...
Messages being sent from X400 with 1992 standard General
Text: context-specific 0 (23 octets):
GeneralString (21 octets):
1b 28 42 0f 1b 2d 42 1b 7e 31 31 31 31 b1 ea 32 32 32
. ( B . . - B . ~ 1 1 1 1 . . 2 2 2
are not correctly converted by the X400 In Mapper. They
should be converted to files of type 1736 with character
set T61BASE, and the data of the file should be consistent
with this.
CR: JAGad46896 SR: 8606177664
The OpenMail Internet gateway rejects multipart/signed
messages if one of its composite, multipart or message,
part's boundary-end markers is missing.
CR: JAGad47713 SR: 8606178486
1) omtidyu -l, -t and -w options - wildcards may get
confused in MB.
If a multibyte string contains an *, this is assumed to be
a wildcard.
2) Username incorrectly displayed if it contains TX fields.
The TX fields are concatenated to earlier field values.
This is also a problem with other address list attributes.
3) The -l option is not displayed.
This displays a list of the requested folders and should be
displayed in the full listing.
4) The error/usage string is not displayed if not options
are specified.
omtidyu either returns nothing, or prompts for the password
for the defult user.
5) The -q option does not work.
The -q option produce similar output to a full report, and
more information than a summary report.
6) The msg type selection is not output.
When a full report is requested, the information on each
item should include the message type.
7) The -f option no longer includes WB.
CR: JAGad48103 SR: 8606178878
If omprepsur is not able to salvage certain files, omdosur
is supposed to substitute some dummy containers instead and
then continue to create a valid omcpoutu archive. Infact,
omdosur was aborting straight after processing the missing
container and so was creating a corrupt omcpoutu archive.
CR: JAGad50818 SR: 8606181602
If a message is sent from a user who has an INTERNET_ADDR
defined, to another machine, e.g. via the SMINTFC gateway,
replies to that message do not get returned via the same
route - they always get returned via the INTERNET gateway.
This occurs when the receiving server does does not have
the user's INTERNET_ADDR defined in the directory, and when
the sending server is version GR7
CR: JAGad52689 SR: 8606183476
This applies to omsmtpd in Release 7.
With heavy usage, the SMTP Relay port 25 listener
occasionally stops with a Select error - Bad File Number.
The omshowlog output contains:
ERROR SMTP Relay (SMTPD Relay
Pr) 03.02.01 13:34:27
[OM.DMON 2163] Failed in select.
Error: 'Bad file number'
Alternatively, after logging this error, omsmtpd may hang.
In this case, there will be more than one copy of omsmtpd
running, and the parent will be waiting for the child
processes, and vice versa.
Temporary Workaround:
Stop and restart the daemon.
Or, if Authorisation or Anti-spam features are not in use,
turn off the relay, and rely on sendmail & ommapsmtp to
route incoming messages correctly.
CR: JAGad55411 SR: 8606186206
When shutting down the Remote Client Interface a
segmentation violation is occuring in the Notification
Monitor occasionally because of a buffer over-run or
under-run.
CR: JAGad56484 SR: 8606187277
The OpenMail delegate implementation does not include an
equivalent for Exchange's "Delegate can see my private
items" option (disabled by default in Exchange). Hence when
forwarding Meeting Requests no distinction is made between
Private items and others.
CR: JAGad56620 SR: 8606187413
Message delivery rulesets are not working with empty
subjects.
CR: JAGad57754 SR: 8606188546
omredirtcp logs errors "getsockname: Bad file number" when
no error has occurred.
CR: JAGad58840 SR: 8606189626
MAPI addressbook download fails when trying to download a
directory whose first entry is a large entry such as a pdl
because a buffer overflow occurs.
CR: JAGad63387 SR: 8606194177
A coding defect while processing MIME data sometimes causes
a fatal error within the item.browse binary.
On the Netscape Client the user is presented with the
message:
"The current command did not succeed. The mail server
responded: Some of the requested messages no longer exist."
CR: JAGad64229 SR: 8606195023
Some of the OpenMail patch install scripts may use return
codes which are invalid in Software Distibutor (SD). In
addition, symbolic names such as $SUCCESS, $FAILURE and
$WARNING should be instead of 0, 1 and 2.
Some of the messages do not follow the conventions, with a
word such as ERROR in column 1 of the first line only, and
the text indented to column 10.
CR: JAGad64671 SR: 8606195467
When performing searches of large message stores if the
ual.remote associated with the in.imap41d terminates due to
inactivity or is deliberately killed then in.imap41d goes
into a spin. When using TOP or glance the in.imap41d
processes appear to be consuming a lot of CPU activity,
however, they will not impact on system performance
because the kernel will have assigned them a low priority.
CR: JAGad66344 SR: 8606197150
When installing OpenMail B.07.00, file
~openmail/release.sys/smtpd.cfg is updated to contain the
current domain name in place of the string %LOCALDOMAIN%.
This is also done whenever a new OpenMail instance is
created.
When a patch is installed, the patch scripts need to repeat
this edit.
This does not affect ~openmail/sys/smtpd.cfg which is
intended to be tailored by the OpenMail administrator. This
file is not changed during patch installation.
Defect Description:
PHSS_27680:
CR: JAGad71050 SR: 8606201876
The only file attachment that OM recognises as of type text
are .TXT files.
It is not told that .CSV files need treating in the same
way with regard to newlines.
CR: JAGae07887 SR: 8606238864
The failure to merge folders whose names contain multibyte
data correctly was due to only the downgraded folder names
being compared for matches, ignoring any existance of T61
folder names.
CR: JAGae18540 SR: 8606254208
When sendmail is invoked from omredirtcp it is called with
the -bs option for single execution. When this option is
used the 'check-relay' functionality is not performed, so
connections from IP addresses that should be rejected are
allowed.
To overcome this deficiency in the omredirtcp environment
the -x option has been added to omredirtcp to allow a file
of IP addresses to be rejected to be specified. See the
omredirtcp MAN page for details.
CR: JAGae24659 SR: 8606260336
Although obscure and indirect, the directory path:
"/var/opt/openmail/dir/../is/"
is strictly correct and in fact necessary, due to the
possibility that "~openmail/dir" may be a symbolic link to
a completely different location, and "is/" is always within
the physical parent of the "~openmail/dir".
This needs pointing out to the user by rewording the man
page in 2 places.
However, understanding the location of the ISDB is simply
background information; it is not necessary for the use of
these commands.
CR: JAGae24724 SR: 8606260401
AIX 5.1L keeps the sendmail.cf files in /etc/mail. 8.9 is
no longer the latest version of sendmail.cf, so omrc is
changed to check certain file permissions for sendmail 8.9
or later.
CR: JAGae26104 SR: 8606261785
The problem is caused by omon failing to wait for the
Required state of a service to move from "disabling" to
"disabled" before attempting to start a service.
CR: JAGae27170 SR: 8606262840
The code that handles the delete of the item does not think
that the newly added item is within a Bulletin Board as a
this information has not been added to the transient record
that represents the item in the BB list.
CR: JAGae31209 SR: 8606266965
When omredirtcp fork/execs sendmail to handle an incoming
SMTP connection the sendmail process inherits the SMTP
socket. While the sendmail process is servicing this SMTP
connection the SMTP socket cannot be re-established (the
'bind' call will fail). Therefore if omredirtcp is killed
it cannot be restarted until all its sendmail children have
exited.
CR: JAGae32060 SR: 8606267820
The primary cause of the problem is the fact that the TNEF
file after decoding from the MIME encoding
(quoted-printable in this instance) is corrupt and contains
field length information that points beyond the end of the
TNEF data.
The secondary problem is that the quoted-printable encoding
of a TNEF attachment is illegal according to Microsoft's
rules for this type of attachment.
The fix detects when a TNEF attachment is not encoded as
"base64" and logs an informative error to the OpenMail log.
The TNEF file is decoded according to the general.cfg
UX_PRE_5_20_COMPATIBILITY_MODE setting. If any corruption
is detected the TNEF attachment will either be treated as a
text attachment or the message will be rejected according
to the general.cfg UXI_NON_DELIVER_BAD_TNEF setting.
CR: JAGae32230 SR: 8606267991
A design defect, in the Mime Browser Controller, of
shutting down immediately on encountering a SIGPIPE signal
from any broken connections (client or child) out of its
many connections.
CR: JAGae32345 SR: 8606268107
The problems occur because ual.remote is built with thread
support, even though each logged-in user has a separate
copy. As similar problems could happen in the IMAP server,
the MIME browser and the item browser, these components
should be built without the use of threads.
CR: JAGae33094 SR: 8606268859
When the Sender name is examined the fact that it has a
comment means that it is treated as a non-null email
address. After stripping out the comments a null email is
left and this is then treated as a valid originator.
CR: JAGae33310 SR: 8606269075
The code does not differentiate enough between a TNEF
recipient and a MIME recipient to split the message and
allow different steering for the different types of
recipient.
As the fix for this problem will cause a change in
behaviour on systems that have different TNEF and MIME
steering files then the old (incorrect) behaviour can be
reinstated by setting the following general.cfg option:
UXO_OLD_TNEFOUT=TRUE
CR: JAGae33867 SR: 8606269632
When using PC Admin to create/modify PDLs the ommodpdln
command is used on the server. If the user being
added/modified has an INTERNET-ADDR (IA) attributed
configured in the directory then this attribute is supplied
in the entry. The presence of this IA attribute is causing
'ommodpdln' to report an error.
CR: JAGae35717 SR: 8606271509
On AIX 5.1L, the df command lists an entry for a file
system called /proc. All the sizing parameters for this
file system are listed as hyphens. This confuses the
omdiskfull command which issues a message announcing a full
file system. The 'omeval omdf' command (for AIX) has been
changed to ignore this entry.
CR: JAGae36951 SR: 8606272845
The non-ASCII characters in the comment part of the ARPA
name confuse unix.out and it thinks that the name is
illegal and therefore refuses to process the name and
generates a NDN for the message.
It seems that only Outlook (under some circumstances)
preserves the comment field when generating a reply, other
clients discard the comment and therefore are not affected
by this problem.
PHSS_27062:
CR: JAGad38110 SR: 8606168832
Both Web Clients create workfiles in /var/tmp. The umask
system call should be invoked to ensure that the files are
neither world-readable nor world-writable.
CR: JAGae05328 SR: 8606236267
If a program loads a dynamic library which has been
compiled with threads enabled, then file I/O is unstable
within the dll unless there has been file I/O within the
calling program first. This appears to be a problem in
Linux Redhat 7.2.
CR: JAGae12028 SR: 8606245558
When an APPEND command is issued by an IMAP client the
OpenMail creator of the item being appended is not set to
be the Sender of the item. Neither is the OpenMail create
date set to be the IMAP internal date of the item. The
existing code does make the message Sender a FROM recipient
in the distribution list - this means that other IMAP
clients see the correct sender/creator, however non-IMAP
clients see an incorrect msg creator.
A new general.cfg option is introduced with the fix for
this problem:
IMAP_ALLOW_MOD_CREATOR=TRUE
will set up the OpenMail creator to be the message Sender -
this is the default.
IMAP_ALLOW_MOD_CREATOR=FALSE
will reinstate the old behaviour.
CR: JAGae12031 SR: 8606245561
The ICE session is terminated because the REMOTE_ADDR value
passed to the cgi program changes during the course of the
email session. The code expects this value not to change,
but there are circumstances when it does. It can happen
when web access is provided by an ISP.
In order to provide flexibility in this situation a new web
access and profile option will be provided to control the
behaviour of the web profile with respect to a changing
value of REMOTE_ADDR during a session.
The REMOTE_ADDR value can legitimately change if an ISP is
being used, so this behaviour is now contolled by the
option:
Allow-Remote-Addr-Change = 0 # REMOTE_ADDR value can't
# change (default and old
# behaviour)
Allow-Remote-Addr-Change = 1 # REMOTE_ADDR can change
# if SessId is in cookie.
Allow-Remote-Addr-Change = 2 # REMOTE_ADDR can change
# with no checking.
This option can be set at the individual profile level:
~openmail/omhmtl/<Profile_Name>/profile
or for all web profiles:
~openmail/omhtml/config
The individual profile setting (if set) will take
precedence.
An Allow-Remote-Addr-Change setting of 1 is recommended to
overcome any premature SESSION EXPIRED problems - this will
work if the web browser is using cookies to provide session
id hiding. A setting of 2 means that no checking of
REMOTE_ADDR is done at all and if cookies are not being
used then the session id information is passed within URLs
that are visible on the computer screen and could be used
from another web browser.
CR: JAGae17136 SR: 8606251070
The handling of the SIGCLD (SIGCHLD) interrupt has changed
from being ignored to being trapped ('reaped'). This change
has had some unforeseen side-effects.
CR: JAGae18238 SR: 8606253906
The code to check a new password against any password
composition rules was removed when the PAM mechanism was
incorporated in the B.07.00 code.
CR: JAGae19347 SR: 8606255018
Content Disposition of 'inline' should be configurable
without a 'filename' value. A new general.cfg option has
been added to allow this to be configured:
INET_INLINE_FILETYPES=nnnn
where 'nnnn' is an OpenMail filetype. Several filetypes can
be specfied by separating with commas, for example:
INET_INLINE_FILETYPES=2130,2133
will cause both RTF and HTML to be given a Content
Disposition of 'inline'.
The INET_INLINE_FNAME_ALLOWED=FALSE option should still be
set in general.cfg to suppress the 'filename'.
Additionally the ~openmail/sys/mimeout.str file should be
editted to uncomment the lines for 2130 and 2133 if the
multipart/alternative structure is not required for these
filetypes.
CR: JAGae22300 SR: 8606257997
The T.61 subject can become large when encoded as a MIME
string as each separate T.61 sub-string will be preceded by
a character set specification. This long string can then
overflow the buffer used to hold the MIME filename string
causing a Segmentation Violation.
CR: JAGae22536 SR: 8606258235
A coding defect, in the incoming Internet Gateway, of
failing to increment a loop count on encountering a NULL
X400 address, as occurs in this case, causes an infinite
loop.
CR: JAGae23835 SR: 8606259517
There is no test for whether read acknowedgements are
required when an IMAP message is read, and no attempt is
made to generate an acknowledgement if it is.
PHSS_26278:
CR: JAGad84900 SR: 8606215723
The incoming Internet Gateway normally truncates all X.400
printable string attributes, of all ORNs within a message,
to the size limits stipulated in the X.400 standard, just
in case the message is sent through the X.400 Gateway.
A new Tweak, INET_NO_TRUNC_X400_ATTS, has been introduced
to inhibit this truncation.
CR: JAGad95079 SR: 8606226007
The primary cause of the problem is the fact that the TNEF
file after decoding from the MIME encoding
(quoted-printable in this instance) is corrupt and contains
field length information that points beyond the end of the
TNEF data.
The secondary problem is that the quoted-printable encoding
of a TNEF attachment is illegal according to Microsoft's
rules for this type of attachment.
The fix detects when a TNEF attachment is not encoded as
"base64" and logs an informative error to the OpenMail log.
The TNEF file is decoded according to the general.cfg
UX_PRE_5_20_COMPATIBILITY_MODE setting. If any corruption
is detected the TNEF attachment will either be treated as a
text attachment or the message will be rejected according
to the general.cfg UXI_NON_DELIVER_BAD_TNEF setting.
CR: JAGad97183 SR: 8606228125
The text in the message catalogue for the message rejection
due to a recipient user's 'service level' value is
incorrect. It describes this error as a mailbox size limit
violation.
CR: JAGad97593 SR: 8606228536
There is no code whatsoever in the Web ICE Client 6.0 to
cope with the %%SIGNONALTS%% markup in the Duplicate
Usernames page of the 5.10 profiles, which is significantly
different from the 6.0 profiles. It has no code of its own
to do all the extra work that the Web Client 5.10 does in
this case.
Also, at GR6, the Portal Access facility was not available
with the Web Client 5.10, and so when its profiles are used
with the ICE Client 6.0, it has no ability to display a
list of alternative names; the Duplicate Usernames page is
absent.
CR: JAGad98210 SR: 8606229157
Pluggable Authentication Modules (PAM) changes to GR7 have
accidently removed the UAL_LOCAL_IGNORE_PASSWORD option.
CR: JAGae02798 SR: 8606233575
The code of the in.imap41d program does not use the
'received date' information when retrieving the
INTERNALDATE attribute of a message.
CR: JAGae03973 SR: 8606234784
The problem was that omlogoff terminates while the omlogon
process is still running. If running another omlogon
immediately afterwards, the first omlogon would delete out
the user pipes which the second omlogon had just created.
Although this second omlogon appeared to have succeeded, it
was unable to process further requests - e.g. omlist. An
omlist call would then expect the username and password to
be entered manually. This caused various of the OpenMail
autotests to hang.
CR: JAGae03977 SR: 8606234788
The cause of the problem was the errno value being changed
when a successful accept() call was made. It is possible
for this to happen on Linux. The pcmonitor returns an error
condition to a calling function if the errno indicates an
error, even if the accept call was successful. This caused
omlogon to fail.
CR: JAGae06468 SR: 8606237428
The failure of omdosur was caused by trying to access files
in the live message store rather than those in the
alternative working directory which is specified when
omdosur is called.
Each time a Content Record is opened in omdosur a transient
flag is set to indicate that the alternative working
directory should be used when opening files. For IMAP
object file information this did not succeed as the Content
Record was reread unsetting this flag.
CR: JAGae07450 SR: 8606238426
A coding defect of an uninitiallised return parameter, in
the User Directory Access component, causes the return of a
spurious Primary Mailnode when none exists, in very rare
circumstances. The caller does not defend against this
condition.
Encountered only on Solaris 8, but could occur rarely
anyplace, anytime.
PHSS_25648:
CR: JAGad83534 SR: 8606214343
This is an enhancement to the behaviour of the
auto-actions. Auto- redirect may now be controlled by two
directives from the config file; EXECUTE_AA_ON_REDIRECT and
DELETE_INTRAY_MSG_ON_REDIRECT. The values they take are 0
or 1. Before the introduction of this enhancement an
auto-redirect prevented other auto-actions from being
honoured. The first of these two directives ensures that if
any other auto-actions are enabled then they are honoured,
however the trigger message is delivered to the intray. The
second directive will delete the trigger message from the
intray.
CR: JAGad83915 SR: 8606214723
An empty auto-forward covering text string prevents the
file, held within the users g directory, which holds the
covering text from being generated. If this file is not
present the local delivery agent fails to forward the
message.
CR: JAGad83932 SR: 8606214740
The UAL checklist command did a check to see if the
specified address matched the internet address before
looking for a match on the X400 attributes.
If alternatives were found, then the list of alternatives
was compiled by researching the directory. however, the
search to create the list was only being done on the X400
attributes and no internet search was done on the internet
directory. This resulted in no matches being found and the
list being empty.
In addition, the internet search was done only on the
internet attribute. So if X400 attributes had been
specified, these were ignored when determining a match from
the internet directory.
CR: JAGad84893 SR: 8606215716
After processing a erroneous Return of Contents, the X400
outgoing gateway failed to clear a global data item. This
led to subsequent messages being incorrectly handled, and
rejected with 6019 log error numbers. Processing following
the detection of the 6019 errors failed to close the
transaction file of the message or distibution list, and
eventually the limit for the maximum number of open
transaction files was reached.
CR: JAGad84922 SR: 8606215745
An empty auto-reply covering text string prevents the file,
held within the users g directory, which holds the covering
text from being generated. If this file is not present the
local delivery agent fails to generate an auto-reply
message.
CR: JAGad87535 SR: 8606218386
In GR7 a session monitor daemon was introduced which does
some of the work of the UAL. One thing it does is to update
the user's signon information, and the functionality of
when to update the last signon time was not implemented.
Instead, the last signon time is always updated - which
does not correspond to the GR6 functionality when an admin
session or a session run by a trusted user is doing the
signon.
CR: JAGad87649 SR: 8606218500
The UAL_BBACL command that set Outlook permissions on
folders uses the ACL name checking code which (incorrectly)
will not allow the Common Name field to be specified with
other Mnemonic ORN fields. Eg. Teresa
Green/acme,sales/CN=tg will be rejected as an invalid
delegate name.
CR: JAGad88671 SR: 8606219531
The code in the X400 intrinsics, that processes non-textual
content items using the EMA BodyPart 15 rules, allocates
memory on a per message basis for a number of linked data
structures, and fails to release all of them at the end of
the message.
CR: JAGad88889 SR: 8606219749
Extra spurious content is displayed for an IMAP client when
there are more that 9 top level contents. This is due to an
incorrect comparison of the content item number.
CR: JAGad89888 SR: 8606220752
An internal format error within TCL strings caused 8-bit
strings to appear corrupted.
CR: JAGad90057 SR: 8606220921
When the message type is multipart/report, the message is
written out to a temporary file. The length of the line is
noted and if less than 1, an error is reported. If the
first character of a line is null, then the length is 0,
incorrectly causing a fatal error.
CR: JAGad90490 SR: 8606221356
Non-ascii NDN text from message catalogue is not given the
correct charset specification in the MIME header.
CR: JAGad90761 SR: 8606221627
One write to the shared memory used by the Notification
Server failed to check if enough space was available before
commencing the write.
CR: JAGad91276 SR: 8606222161
The omupdtis code traps the SIGHUP and SIGTERM to allow
processing of the omupdtis command to be interrupted but
does not set a error return when this happens.
CR: JAGad93282 SR: 8606224187
The Named Property Id is incremented each time a named
property is generated. There is no check for the actual
maximum of FFFE, or for overflow at FFFF. So once the value
FFFE was exceeded, the named property id's take undefined
values.
CR: JAGad93317 SR: 8606224222
PAM changes for B.07 cause unsuccessful signons to return
early without doing any audit logging.
CR: JAGad94573 SR: 8606225486
The tweaks DEFAULT-OMSERVER and OMSERVER where not honoured
if the portal access mechanism was disabled.
CR: JAGad94888 SR: 8606225815
At VV4.5 root does not have the required authorisation
level to execute the setlevel command.
CR: JAGad95463 SR: 8606226394
The cause appears to be the value of the PR_RTF_SYNC*
properties, in particular the PR_RTF_SYNC_BODY_COUNT.
These properties are correctly set when the message is
initially created. However, after the message has been
saved and re-edited, these properties are NOT updated
causing a mismatch between the properties and the actual
content of the sent message.
PHSS_24876:
CR: JAGad30137 SR: 8606160818
This form of message is not a multi-part message, and the
code that reads and processes the '.' terminator in this
case omitted to include the newline character in the check.
Hence the code attempted to continue to read stdin, and
hence the hang, as unix.in is waiting for more from
sendmail
CR: JAGad31466 SR: 8606162150
Exchange Connector resyncs were removing any
entry that had a non-addressing attribute changed on the
Exchange side - this was caused by the fact that the DS
entries coming from Exchange do NOT have a LID attribute so
the normal method of getting the entry using DA_SOURCE_LID
does not work.
CR: JAGad49568 SR: 8606180347
Multiple sender names on the omtidyu command line were all
held in a single buffer resulting in the last senders name
to be registered for all the sender names.
CR: JAGad65896 SR: 8606196695
This was caused by an error in the code that scans Arpa
ORNs, when attempting to map domain names to Openmail
mailnodes using the unixmap.in configuration file.
CR: JAGad67601 SR: 8606198411
The code that is used to build the PDUs for outgoing X.400
messages is not under our control, we use XAPI libraries to
give us a higher level interface to ASN.1 structures and
independence from the underlying MTA. This code is not
particularly efficient and it uses quite large structures
in memory when a PDU is being contructed. In the case of a
message that has a Distribution List with 10,000 names it
will take a long time and use a lot of resources.
The fix for this problem is to add some general.cfg options
to replace large distribution lists with a single name
distribution list. This will not prevent the message from
reaching the intended recipients, but it will speed up the
transfer of the message through the X.400 gateway. If this
DL replacement occurs then the message cannot be
successfully replied to 'all' (as the original distribution
list has been removed).
The general.cfg options are:
X4O_MAX_DL_NAMES=n
where n is the maximum number of names allowed in a
DistList before they get replaced with a single stub DL
name. Default is the current behaviour... there is no
limit.
where the string contains the stub DistList name in
positional ORN format (each ORN field separated with a '/'
character). %s can be used in this string and will be
substituted with the number of names found in the original
DistList. For example: X4O_MAX_DL_NAMES=1000
X4O_MAX_DL_NAMES_ORN=DistList/%s-Name///Black/Hole
will produce a name that the user sees as:
TO: 1001-Name DistList /Black,Hole
when a DistList with 1001 names is send through the X.400
gateway. The default for this ORN string is:
DISTRIBUTION-LIST/%s-NAME///MAIL-SYS
CR: JAGad68810 SR: 8606199624
The fix for JAGab39939 (omfmtent produces illegal directory
entries for entries with null values) has caused omshowcda
to display the directory mask to be displayed differently.
CR: JAGad69036 SR: 8606199850
The cause of the corrupted Korean, Japanese and Simplified
Chinese strings was due to an internal formating error.
CR: JAGad69543 SR: 8606200362
A coding defect within the item.browse binary resulted in a
failure while mime encoding a message.
CR: JAGad70640 SR: 8606201464
Some scripts supplied with OM-APPL specified the full path
name for the 'cut' command. They needed to be enhanced to
support a different location on some OS versions.
CR: JAGad70641 SR: 8606201465
The scripts vvice and vvysnc where not updated for OpenMail
B.07.00 periodic patches
CR: JAGad71090 SR: 8606201916
Hidden items within the message store were included within
the item count when listing the tray or folder areas.
CR: JAGad71959 SR: 8606202785
The mime browsing library only expects to be dealing with
message components in a serialised file. There are
occasions when the components of a message are not
serialised - when this is the case the browse of that item
returns nothing.
CR: JAGad74578 SR: 8606205403
The MIME header is slightly strange inasmuch as the value
is separated from the tag by two spaces. For example:
Content-Transfer-Encoding: base64
This causes the MIME generation routines (in some
circumstances) to misinterpret the MIME header field value.
In this particular case the MIME header has come in from
outside of OpenMail and is being retained in the
inetMessageHeader object file associated with the message.
CR: JAGad74715 SR: 8606205540
A coding error resulted in the mhsORAddress and omAddress
attribute being mapped only to the the Openmail S, S-TX, G
and G-TX attributes for the modify:replace option.
Consequently, when building the OpenMail modification data,
only the former surname and givenname attributes were
deleted and 2 values were supplied for OU1 and other
modified attributes.
CR: JAGad75038 SR: 8606205863
When processing ORNs, omaddent converts to T61 and then
breaks the ORN down into a set of T61 substrings. This may
mean adding some bytes (T61 characters) at the start of
each substring. For non-T61 values, these bytes are later
removed before the value is stored in the directory. This
defect was also removing bytes whose values are the same as
the T61 characters, but which were not added by the initial
parsing.
CR: JAGad75517 SR: 8606206344
The code that constructs the command output was erroneously
attempting to dereference a pointer whose value was NULL.
CR: JAGad75975 SR: 8606206802
In the following text, # is used to represent the
<backslash> character. Sendmail modifies entries of the
form
user#"test <user/test>
to
"user##"test" <user/test>.
Openmail takes this and assumes that the second " ends the
quoted text, then the third quote opens further quoted text
and the To: input can become out of sync.
Further, it becomes possible for mangled addresses to be
greater in size than expected causing a serious error to
occur.
CR: JAGad79081 SR: 8606209895
A coding defect in the IMAP Server does not take any
account of the special chars in OM Personal Names as input
and therefore fails to map them into those they represent.
CR: JAGad80029 SR: 8606210842
The child process IDs were corrupted within the process ID
configuration file due to incorrect file locking mechanisms
CR: JAGad83734 SR: 8606214543
UAL Checklist searches on the internet address field, and
records in the DL the entries with alternatives/duplicates.
Later it reprocesses the DL, re-searching to get the
alternatives in a new file, which is then appended to the
DL. However, the re-search is on the X400 attributes, not
on the internet address, and the alternatives file is not
created. But the attempt to append continued anyway, and
tried to open a non-existent file.
PHSS_23491:
CR: JAGab39939 SR: 8606100957
The parser does not take into account the case when there
is an attribute name but no attribute value.
CR: JAGab68963 SR: 8606102906
When a Repeat Reminder is set, the message is placed in the
message list DEFER.UA by the UAL. While calculating the
next submission date-time of the message, the final
reminder date is calculated based on the current date and
the value of the current reminder.
If the next submission date of the reminder message is less
than the final reminder date, then the message is placed on
the Service router for routing. Otherwise it is deleted
from the message list, so that no more repeat reminders
will be sent. But since the final reminder date is
calculated using the current date the submission date is
ALWAYS less than the final reminder date.
CR: JAGad31664 SR: 8606162348
The Outgoing Internet Gateway is confused by addresses that
can be generated by the cc:Mail client, such as :
"S=Friendly Name .gren/OU1=mime/
DDT1=RFC-822/DDV1=Friendly Name <grennowhere.hp.com>/
INTERNET-ADDR=Friendly Name <grennowhere.hp.com>"
===========================================================
A coding defect in the ux component tries to enclose the
"Comment <userdomain>" within angle brackets <>, by only
inserting a start bracket < at the beginning, before
passing it to Sendmail, resulting in unmatched brackets,
which naturally generates a Sendmail error.
CR: JAGad35090 SR: 8606165799
The algorithm used to select the approprate user's message
store to restore selects the last message store that
matches just the name part of the user's address.
CR: JAGad40563 SR: 8606171299
The Root-URL is used initially when sending back the
Location: header on signon. The SERVER-PROTOCOL environment
variable is used to construct part of the URL. It appears
that the Apache web server sets the SERVER-PROTOCOL
variable to HTTP/1.0 regardless of whether you are talking
HTTP or HTTPS, however it identifies the fact that we are
talking HTTPS by setting the environment variable
HTTPS="on"
CR: JAGad41471 SR: 8606172211
A segmentation fault occures when parsing a blank line at
the top of the mnMapFile which is located in the
var/opt/openmail/sys directory.
CR: JAGad42968 SR: 8606173711
A design defect in the mim component restricts the search
for an internet address within an ORN to the ordinary DDA
fields of the ORN. However an 8-bit address is stored in a
teletex DDA-TX field, which is ignored by this search and
so the internet address is effectively discarded.
CR: JAGad43052 SR: 8606173797
The IMAP daemon was not converting MIME subject before
copying an item into the OpenMail message store.
CR: JAGad44030 SR: 8606174784
The item browser fails to convert UTF8 to ISO8859_1 when a
message is in MIME format, even though a converter exists.
It recognises that a converter exists, but fails to convert
the UTF8 characters to UCS2 first in the case of the MIME
format. The conversion is then incorrect. In the case of
non MIME text, this two stage conversion is completed
successfully.
UNICODE conversions for MIME formatted messages are not
generally supported in OpenMail and so the 2 step
conversion required had not been implemented.
CR: JAGad45429 SR: 8606176189
When the rule name is read from the OpenMail Auto-Actions
file, tcl expects the format of the string to be UTF-8.
OpenMail does not store the rule names in UTf-8 format,
thus if the rule name is modified in anyway then it becomes
corrupted.
CR: JAGad45449 SR: 8606176209
When a folder is listed (UAL_PRPLST/UAL_LIST) any messages
in the list that not have TextPreview data setup get it
dynamically generated. This causes the ModifiedDate in the
ctner to be updated. This updated ModifiedDate in the ctner
means that the sync. process treats this as a conflict. The
fix is to suppress the ModifiedDate update for this
behind-the-scenes modification. As far a synchronisation
goes the TextPreview is a 'computed' field, dynamically
created in an offline store and is not synchronised data-
so this change is good both architecturally and
pragmatically.
CR: JAGad45880 SR: 8606176642
The attempted encoding of a ' ' character followed by a
'n' as the 1015 and 1016 characters of a line in an html
attachment resulted in the premature abort of the
item.browser and a subsequent segmentation violation.
CR: JAGad46439 SR: 8606177205
The General Text handling code at the incoming X400
interface was written on the assumption that the
interchange charset for non-Latin-1 single byte languages
would be based on an ISO8859_n charset, as used in General
Text bodyparts.
When the Czech version of OpenMail was done, it was decided
to use T61BASE as the interchange charset. However, the
X400 incoming mapper was not changed to properly convert
and map the bodyparts.
CR: JAGad46896 SR: 8606177664
A coding defect in the ux component tries to run off the
end of the temporary file holding the Multipart/Signed part
of the Sendmail message, when this part has missing
end-boundaries of composite contents types, Multipart or
Message.
CR: JAGad47713 SR: 8606178486
) omtidyu -l, -t and -w options - wildcards may get
confused in MB.
The * character is assumed to be the wildcard character in
all cases. This may not be so for certain MB strings.
2) Username incorrectly displayed if it contains TX fields.
The display routine does not take the address group
separator 027 into consideration.
3) The -l option is not displayed.
This is an enhancement request.
4) The error/usage string is not displayed if not options
are specified.
A check to no parameters is not done.
5) The -q option does not work.
The reporting mechanism displays a full report if a SUMMARY
report is not requested, rather than if a FULL report is
requested.
6) The msg type selection is not output.
This is an enhancement request.
7) The -f option no longer includes WB.
In GR7, the -T w option is used to display the waste basket
CR: JAGad48103 SR: 8606178878
Some changes introduced to omdosur as part of the 5.20 MAPI
work, was failing to take into account the possibility of a
missing container.
CR: JAGad50818 SR: 8606181602
When the OMGUI processes a reply, it takes the Distribution
List of the original message and supplies it to UAL
Checklist, requesting Lookup of the 167 attribute in the
UnixMap directory for ORNs that have a group 5 internet
address field.
Messages received from GR7 may contain the internet address
of Openmail users as well as of internet users. If the GR7
internet addresses are not present in the directory of the
server where the reply is constructed, the 167 lookup will
fail to find a match. The code then assumes the recipient
is an internet user and adds the address of the internet
Gateway to the ORN.
CR: JAGad52689 SR: 8606183476
When the relay is heavily loaded, it creates one or more
child relay processes to share the incoming requests. The
child processes later stop when they have been idle for a
while (30 seconds by default). The select error can occur
when the parent is processing the Termination signal from
the child, if the signal is received between when the code
decides to look for input from the child (FD SET) and doing
the select.
After hitting this error, the code does not explicitly stop
the child relay processes, but does wait for them to die.
As the child processes may be waiting for instructions from
the parent, a hang can occur.
CR: JAGad55411 SR: 8606186206
The segmentation violation in the Notification Monitor is
caused by dirty data in a buffer which then causes a buffer
under-run or over-run to then occur. This dirty data
appears to be generated by a large number of
deregistrations for notifications which happens when the
RCI is shut down and timing problems cause a write to the
buffer to be killed thus generating the dirty data which is
then read. The current write is in two stages with the
possibility that the process can be terminated inbetween
these two writes.
CR: JAGad56484 SR: 8606187277
Currently the client does not set up a filter on the
Outlook delegate redirection to prevent private items being
redirected.
The best solution to this problem is to change the server
code so that by default a private Outlook meeting request
will NOT be redirected to a delegate. This behaviour can be
overridden by the LD_SENSITIVE_ITEM_DELEG_REDIR=TRUE
config option (user.cfg and general.cfg)
CR: JAGad56620 SR: 8606187413
Subject is not currently matched (via user-supplied script)
if the subject of the message is null (blank).
The fix is to change the code to allow a blank subject to
be matched. The old behaviour will be reinstated by setting
the RSL_MATCH_BLANK_SUBJECT=FALSE
general.cfg option.
CR: JAGad57754 SR: 8606188546
Porting changes for Linux have caused a problem with the
EINTR signal handling to become visible in the syslog.
EINTR signal handling corrected so that this interrupt is
silently swallowed.
CR: JAGad58840 SR: 8606189626
The failure to download the directory was caused by a
buffer overflow when reading in a large directory entry in
order to pass them to the client.
CR: JAGad63387 SR: 8606194177
The cause of this failure was due to incorrectly parsing
the Content-Disposition response header which sometimes
resulted in corrupted memory.
CR: JAGad64229 SR: 8606195023
The patch installation scripts contained hard-coded exit
codes of 0, 1 and 2, instead of the preferred $SUCCESS,
etc. Also, there were some cases where values other than 0,
1 or 2 could be returned.
CR: JAGad64671 SR: 8606195467
in.imap41d was going into a spin in the function imapsearch
because although conn->state was set to TERMINATED when the
ual socket had died this was not checked for.
CR: JAGad66344 SR: 8606197150
~openmail/release.sys/smtpd.cfg was replaced by an
unconfigured file during patch installation. It is now
edited so it contains a domain name. This is similar to the
work done during initial B.07.00 installation.
Enhancement:
No
SR:
8606201876 8606238864 8606254208 8606260336 8606260401
8606261785 8606262840 8606266965 8606267820 8606267991
8606268107 8606268859 8606269075 8606269632 8606271509
8606272845 8606168832 8606236267 8606245558 8606245561
8606251070 8606253906 8606255018 8606257997 8606258235
8606259517 8606215723 8606226007 8606228125 8606228536
8606229157 8606233575 8606234784 8606234788 8606237428
8606238426 8606214343 8606214723 8606214740 8606215716
8606215745 8606218386 8606218500 8606219531 8606219749
8606220752 8606220921 8606221356 8606221627 8606222161
8606224187 8606224222 8606225486 8606225815 8606226394
8606160818 8606162150 8606180347 8606196695 8606198411
8606199624 8606199850 8606200362 8606201464 8606201465
8606201916 8606202785 8606205403 8606205540 8606205863
8606206344 8606206802 8606209895 8606210842 8606214543
8606100957 8606102906 8606162348 8606165799 8606171299
8606172211 8606173711 8606173797 8606174784 8606176189
8606176209 8606176642 8606177205 8606177664 8606178486
8606178878 8606181602 8606183476 8606186206 8606187277
8606187413 8606188546 8606189626 8606194177 8606195023
8606195467 8606197150
Patch Files:
OpenMail.OM-ADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ADM
OpenMail.OM-AMECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMECAT
OpenMail.OM-AMEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMEICE
OpenMail.OM-AMEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMEPAW
OpenMail.OM-AMEPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMEPSS
OpenMail.OM-APPL,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-APPL
OpenMail.OM-BB,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-BB
OpenMail.OM-CHSCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-CHSCAT
OpenMail.OM-CHSICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-CHSICE
OpenMail.OM-CHSPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-CHSPAW
OpenMail.OM-CORE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/PHSS_27680/ompatch.idx
/opt/openmail/patch/PHSS_27680/omunpatch
/opt/openmail/patch/filesets/OM-CORE
/opt/openmail/patch/ompatch
OpenMail.OM-DESK,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-DESK
OpenMail.OM-DSYNC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-DSYNC
OpenMail.OM-ENGCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGCAT
OpenMail.OM-ENGICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGICE
OpenMail.OM-ENGPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGPAW
OpenMail.OM-ENGPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGPSS
OpenMail.OM-FINCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FINCAT
OpenMail.OM-FINICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FINICE
OpenMail.OM-FINPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FINPAW
OpenMail.OM-FRECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FRECAT
OpenMail.OM-FREICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FREICE
OpenMail.OM-FREPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FREPAW
OpenMail.OM-GERCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-GERCAT
OpenMail.OM-GERICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-GERICE
OpenMail.OM-GERPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-GERPAW
OpenMail.OM-IMAP4,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-IMAP4
OpenMail.OM-ITACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ITACAT
OpenMail.OM-ITAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ITAICE
OpenMail.OM-ITAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ITAPAW
OpenMail.OM-KORCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-KORCAT
OpenMail.OM-KORICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-KORICE
OpenMail.OM-KORPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-KORPAW
OpenMail.OM-LC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-LC
OpenMail.OM-LDAP,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-LDAP
OpenMail.OM-MAN,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-MAN
OpenMail.OM-NIPCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-NIPCAT
OpenMail.OM-NIPICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-NIPICE
OpenMail.OM-NIPPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-NIPPAW
OpenMail.OM-PMOVER,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PMOVER
OpenMail.OM-POP3,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-POP3
OpenMail.OM-PTBCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PTBCAT
OpenMail.OM-PTBICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PTBICE
OpenMail.OM-PTBPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PTBPAW
OpenMail.OM-RC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-RC
OpenMail.OM-SMS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SMS
OpenMail.OM-SPACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SPACAT
OpenMail.OM-SPAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SPAICE
OpenMail.OM-SPAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SPAPAW
OpenMail.OM-SWECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SWECAT
OpenMail.OM-SWEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SWEICE
OpenMail.OM-SWEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SWEPAW
OpenMail.OM-UNIX,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-UNIX
OpenMail.OM-WEBADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-WEBADM
OpenMail.OM-X400,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-X400
what(1) Output:
OpenMail.OM-ADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ADM:
No what strings
OpenMail.OM-AMECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMECAT:
No what strings
OpenMail.OM-AMEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMEICE:
No what strings
OpenMail.OM-AMEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMEPAW:
No what strings
OpenMail.OM-AMEPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-AMEPSS:
No what strings
OpenMail.OM-APPL,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-APPL:
No what strings
OpenMail.OM-BB,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-BB:
No what strings
OpenMail.OM-CHSCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-CHSCAT:
No what strings
OpenMail.OM-CHSICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-CHSICE:
No what strings
OpenMail.OM-CHSPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-CHSPAW:
No what strings
OpenMail.OM-CORE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-CORE:
No what strings
OpenMail.OM-DESK,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-DESK:
No what strings
OpenMail.OM-DSYNC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-DSYNC:
No what strings
OpenMail.OM-ENGCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGCAT:
No what strings
OpenMail.OM-ENGICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGICE:
No what strings
OpenMail.OM-ENGPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGPAW:
No what strings
OpenMail.OM-ENGPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ENGPSS:
No what strings
OpenMail.OM-FINCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FINCAT:
No what strings
OpenMail.OM-FINICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FINICE:
No what strings
OpenMail.OM-FINPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FINPAW:
No what strings
OpenMail.OM-FRECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FRECAT:
No what strings
OpenMail.OM-FREICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FREICE:
No what strings
OpenMail.OM-FREPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-FREPAW:
No what strings
OpenMail.OM-GERCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-GERCAT:
No what strings
OpenMail.OM-GERICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-GERICE:
No what strings
OpenMail.OM-GERPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-GERPAW:
No what strings
OpenMail.OM-IMAP4,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-IMAP4:
No what strings
OpenMail.OM-ITACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ITACAT:
No what strings
OpenMail.OM-ITAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ITAICE:
No what strings
OpenMail.OM-ITAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-ITAPAW:
No what strings
OpenMail.OM-KORCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-KORCAT:
No what strings
OpenMail.OM-KORICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-KORICE:
No what strings
OpenMail.OM-KORPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-KORPAW:
No what strings
OpenMail.OM-LC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-LC:
No what strings
OpenMail.OM-LDAP,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-LDAP:
No what strings
OpenMail.OM-MAN,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-MAN:
No what strings
OpenMail.OM-NIPCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-NIPCAT:
No what strings
OpenMail.OM-NIPICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-NIPICE:
No what strings
OpenMail.OM-NIPPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-NIPPAW:
No what strings
OpenMail.OM-PMOVER,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PMOVER:
No what strings
OpenMail.OM-POP3,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-POP3:
No what strings
OpenMail.OM-PTBCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PTBCAT:
No what strings
OpenMail.OM-PTBICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PTBICE:
No what strings
OpenMail.OM-PTBPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-PTBPAW:
No what strings
OpenMail.OM-RC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-RC:
No what strings
OpenMail.OM-SMS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SMS:
No what strings
OpenMail.OM-SPACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SPACAT:
No what strings
OpenMail.OM-SPAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SPAICE:
No what strings
OpenMail.OM-SPAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SPAPAW:
No what strings
OpenMail.OM-SWECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SWECAT:
No what strings
OpenMail.OM-SWEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SWEICE:
No what strings
OpenMail.OM-SWEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-SWEPAW:
No what strings
OpenMail.OM-UNIX,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-UNIX:
No what strings
OpenMail.OM-WEBADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-WEBADM:
No what strings
OpenMail.OM-X400,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/filesets/OM-X400:
No what strings
OpenMail.OM-CORE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/openmail/patch/ompatch:
$Header: sh_patch.gen /main/gr7_patch/4 2002/04/26 1
8:35:41 pl $
/opt/openmail/patch/PHSS_27680/omunpatch:
$Header: sh_unpat.gen,v
/opt/openmail/patch/PHSS_27680/ompatch.idx:
No what strings
cksum(1) Output:
OpenMail.OM-ADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3005810758 883169 /opt/openmail/patch/filesets/OM-ADM
OpenMail.OM-AMECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2063755214 224617 /opt/openmail/patch/filesets/OM-AMECAT
OpenMail.OM-AMEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
482627314 17018 /opt/openmail/patch/filesets/OM-AMEICE
OpenMail.OM-AMEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2727039800 13851 /opt/openmail/patch/filesets/OM-AMEPAW
OpenMail.OM-AMEPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3088362064 106416 /opt/openmail/patch/filesets/OM-AMEPSS
OpenMail.OM-APPL,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2343977273 185507 /opt/openmail/patch/filesets/OM-APPL
OpenMail.OM-BB,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
838541086 85444 /opt/openmail/patch/filesets/OM-BB
OpenMail.OM-CHSCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3316418595 124055 /opt/openmail/patch/filesets/OM-CHSCAT
OpenMail.OM-CHSICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3953054192 17077 /opt/openmail/patch/filesets/OM-CHSICE
OpenMail.OM-CHSPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1980391945 14141 /opt/openmail/patch/filesets/OM-CHSPAW
OpenMail.OM-CORE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3862330438 12094552 /opt/openmail/patch/filesets/OM-CORE
OpenMail.OM-DESK,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1333808759 106323 /opt/openmail/patch/filesets/OM-DESK
OpenMail.OM-DSYNC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3362399548 176685 /opt/openmail/patch/filesets/OM-DSYNC
OpenMail.OM-ENGCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3106784538 224614 /opt/openmail/patch/filesets/OM-ENGCAT
OpenMail.OM-ENGICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1394947289 16986 /opt/openmail/patch/filesets/OM-ENGICE
OpenMail.OM-ENGPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3003016822 13847 /opt/openmail/patch/filesets/OM-ENGPAW
OpenMail.OM-ENGPSS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
894234866 106408 /opt/openmail/patch/filesets/OM-ENGPSS
OpenMail.OM-FINCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2620329312 251737 /opt/openmail/patch/filesets/OM-FINCAT
OpenMail.OM-FINICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
220141658 17090 /opt/openmail/patch/filesets/OM-FINICE
OpenMail.OM-FINPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2551433107 14246 /opt/openmail/patch/filesets/OM-FINPAW
OpenMail.OM-FRECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2896750362 251562 /opt/openmail/patch/filesets/OM-FRECAT
OpenMail.OM-FREICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2102227137 17041 /opt/openmail/patch/filesets/OM-FREICE
OpenMail.OM-FREPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
4030317735 14169 /opt/openmail/patch/filesets/OM-FREPAW
OpenMail.OM-GERCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3867108161 252209 /opt/openmail/patch/filesets/OM-GERCAT
OpenMail.OM-GERICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3084462970 17064 /opt/openmail/patch/filesets/OM-GERICE
OpenMail.OM-GERPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
324909271 14095 /opt/openmail/patch/filesets/OM-GERPAW
OpenMail.OM-IMAP4,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3615739694 84370 /opt/openmail/patch/filesets/OM-IMAP4
OpenMail.OM-ITACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
25331491 249989 /opt/openmail/patch/filesets/OM-ITACAT
OpenMail.OM-ITAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2667437204 17046 /opt/openmail/patch/filesets/OM-ITAICE
OpenMail.OM-ITAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2309767535 14059 /opt/openmail/patch/filesets/OM-ITAPAW
OpenMail.OM-KORCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2261879814 125612 /opt/openmail/patch/filesets/OM-KORCAT
OpenMail.OM-KORICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2719459048 17084 /opt/openmail/patch/filesets/OM-KORICE
OpenMail.OM-KORPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1644423008 14294 /opt/openmail/patch/filesets/OM-KORPAW
OpenMail.OM-LC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1233347347 725555 /opt/openmail/patch/filesets/OM-LC
OpenMail.OM-LDAP,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
51903753 86064 /opt/openmail/patch/filesets/OM-LDAP
OpenMail.OM-MAN,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3214416993 10319 /opt/openmail/patch/filesets/OM-MAN
OpenMail.OM-NIPCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2542585972 125732 /opt/openmail/patch/filesets/OM-NIPCAT
OpenMail.OM-NIPICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2257628985 17115 /opt/openmail/patch/filesets/OM-NIPICE
OpenMail.OM-NIPPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
4241816912 14313 /opt/openmail/patch/filesets/OM-NIPPAW
OpenMail.OM-PMOVER,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2107954746 65720 /opt/openmail/patch/filesets/OM-PMOVER
OpenMail.OM-POP3,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1406703616 68161 /opt/openmail/patch/filesets/OM-POP3
OpenMail.OM-PTBCAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2736192790 252366 /opt/openmail/patch/filesets/OM-PTBCAT
OpenMail.OM-PTBICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2505644982 17062 /opt/openmail/patch/filesets/OM-PTBICE
OpenMail.OM-PTBPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3881910581 14111 /opt/openmail/patch/filesets/OM-PTBPAW
OpenMail.OM-RC,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3205337893 481604 /opt/openmail/patch/filesets/OM-RC
OpenMail.OM-SMS,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1610135645 208690 /opt/openmail/patch/filesets/OM-SMS
OpenMail.OM-SPACAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1472712311 251077 /opt/openmail/patch/filesets/OM-SPACAT
OpenMail.OM-SPAICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
657166368 17077 /opt/openmail/patch/filesets/OM-SPAICE
OpenMail.OM-SPAPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3004241008 14111 /opt/openmail/patch/filesets/OM-SPAPAW
OpenMail.OM-SWECAT,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3640782740 250064 /opt/openmail/patch/filesets/OM-SWECAT
OpenMail.OM-SWEICE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
678131334 17046 /opt/openmail/patch/filesets/OM-SWEICE
OpenMail.OM-SWEPAW,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3265817662 14094 /opt/openmail/patch/filesets/OM-SWEPAW
OpenMail.OM-UNIX,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1478771317 130493 /opt/openmail/patch/filesets/OM-UNIX
OpenMail.OM-WEBADM,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
3596666487 775378 /opt/openmail/patch/filesets/OM-WEBADM
OpenMail.OM-X400,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
2715849462 1018072 /opt/openmail/patch/filesets/OM-X400
OpenMail.OM-CORE,fr=B.07.00,fa=HP-UX_B.11.00_32/64,v=HP:
1357410443 26524 /opt/openmail/patch/ompatch
4120277454 11249 /opt/openmail/patch/PHSS_27680/omunpatch
2049977476 146538 /opt/openmail/patch/PHSS_27680/ompatch.idx
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_23491 PHSS_24876 PHSS_25648 PHSS_26278 PHSS_27062
Equivalent Patches:
PHSS_27679:
s700: 10.20
s800: 10.20
PFSS_17040:
sparcSUN: 5.6 5.7 5.8
PASS_17040:
AIX: 4.3 5.1
PLSS_17044:
intelLinux: RedHat7.0 RedHat7.1 RedHat7.2 RedHat7.3
Patch Package Size: 20410 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_27680
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27680.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27680. 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_27680.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_27680.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27680.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
SUBSYSTEM_SHUT
=================================================
PHSS_27680:
=================================================
CR: JAGae33310 SR: 8606269075
-------------------------------
The old behaviour - not splitting the message when MIME
and TNEF recipients are present and a separate steering
file exists for these routes (~openmail/sys/mimeout.str
and ~openmail/sys/tnefout.str) - can be reinstated by
setting the general.cfg option: UXO_OLD_TNEFOUT=TRUE
=================================================
PHSS_27062:
=================================================
CR: JAGae12028 SR: 8606245558
-------------------------------
The old behaviour can be reinstated by setting the
IMAP_ALLOW_MOD_CREATOR=FALSE option in
~openmail/sys/general.cfg
CR: JAGae12031 SR: 8606245561
-------------------------------
To fix the problem of a premature SESSION EXPIRED error
when using web clients via an ISP web connection a new web
client configuration option has been introduced. This
option controls the behaviour of the ice.user program with
respect to the value of the REMOTE_ADDR environment
variable supplied by the Web server:
Allow-Remote-Addr-Change = 0 # not allowed (default and
# old behaviour)
Allow-Remote-Addr-Change = 1 # Remote Addr can change
# if SessId is in cookie.
Allow-Remote-Addr-Change = 2 # Remote Addr can change
# with no checking.
This option can be set at the individual profile level:
~openmail/omhmtl/<Profile_Name>/profile
or for all web profiles:
~openmail/omhtml/config
The individual profile setting (if set) will take
precedence.
An Allow-Remote-Addr-Change setting of 1 is recommended to
overcome any premature SESSION EXPIRED problems - this will
work if the web browser is using cookies to provide session
id hiding. A setting of 2 means that no checking of
REMOTE_ADDR is done at all and if cookies are not being
used then the session id information is passed within URLs
that are visible on the computer screen and could be used
from another web browser.
CR: JAGae19347 SR: 8606255018
-------------------------------
A new general.cfg option has been added to allow a
specified OpenMail filetype to have a MIME
Content-Disposition of 'inline':
INET_INLINE_FILETYPES=nnnn
where 'nnnn' is an OpenMail filetype. Several filetypes can
be specfied by separating with commas, for example:
INET_INLINE_FILETYPES=2130,2133
will cause both RTF and HTML to be given a
Content-Disposition of 'inline'.
The INET_INLINE_FNAME_ALLOWED=FALSE option should still be
set in general.cfg to suppress the 'filename' attribute.
Additionally the ~openmail/sys/mimeout.str file should be
editted to uncomment the lines for filetypes involved (2130
and 2133 in the example above) if the multipart/alternative
structure is not required.
=================================================
PHSS_26278:
=================================================
CR: JAGad84900 SR: 8606215723
-------------------------------
The incoming Internet Gateway normally truncates all X.400
printable string attributes, of all ORNs within a message,
to the size limits stipulated in the X.400 standard, just
in case the message is sent through the X.400 Gateway. A
new Tweak has been introduced to prevent this truncation :-
INET_NO_TRUNC_X400_ATTS
If set TRUE: The X.400 attributes of an ORN are never
truncated.
If set FALSE: The X.400 attributes of an ORN are truncated
to the limits set by the standard, as usual.
Default: FALSE
OpenMail does not need to be restarted for this option to
take effect.
CR: JAGad95079 SR: 8606226007
-------------------------------
The fix detects when a TNEF attachment is not encoded as
"base64" and logs an informative error to the OpenMail log.
The TNEF file is decoded according to the general.cfg
UX_PRE_5_20_COMPATIBILITY_MODE setting. If any corruption
is detected the TNEF attachment will either be treated as a
text attachment or the message will be rejected according
to the general.cfg UXI_NON_DELIVER_BAD_TNEF setting (see
JAGac39658).
=================================================
PHSS_25648:
=================================================
CR: JAGad83534 SR: 8606214343
-------------------------------
The behaviour of the redirect rule can be controlled by the
directives EXECUTE_AA_ON_REDIRECT and
DELETE_INTRAY_MSG_ON_REDIRECT specified in the
/var/opt/openmail/omhtml/config file. The values these
directives can take are 0 or 1.
The directive EXECUTE_AA_ON_REDIRECT will force local
delivery to retain a copy of the message in the users
intray, thus allowing the auto-actions to be executed.
The directive DELETE_INTRAY_MSG_ON_REDIRECT will force
deletion of the message from the users intray after it has
been delivered and the auto actions have been executed.
=================================================
PHSS_24876:
=================================================
CR: JAGad75038 SR: 8606205863
-------------------------------
Directory entries that have been affected by the defect
should be rewritten with the correct values.
A way to force the republishing the FreeBusy info.
is for the user to do the following in Outlook:
Tools/Options/Preferences tab
- Calendar Options
- FreeBusy Options
- Set publish <n> months... to 0 and hit OK
- FreeBusy Options
- Set publish <n> months... to what is was
before (eg 2) and hit OK
This will cause the FreeBusy info to be rewritten to the
server.
NOTE: OpenMail must be shutdown before installing
this patch.
----------------------------------------------------------
This patch will need the following minimum disk
space requirements:
/opt/openmail/patch : 70 MB
NOTE: ServiceGuard Installations will need twice
this amount.
----------------------------------------------------------
-----End of Document ID: PHSS_27680------------------------------------------
Document ID: PHSS_27678
Date Loaded: 20020905
Title: s700_800 11.X OpenMail B.06.00 September 02 Periodic Patch
Patch Name: PHSS_27678
Patch Description: s700_800 11.X OpenMail B.06.00 September 02 Periodic Patch
Creation Date: 02/08/16
Post Date: 02/09/05
Hardware Platforms - OS Releases:
s700: 11.00 11.04 11.11
s800: 11.00 11.04 11.11
Products:
OpenMail B.06.00
Filesets:
OpenMail.OM-ADM,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-AMECAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-AMEICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-AMEWEB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-APPL,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-BB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-CCMOB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-CHSCAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-CHSICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-CHSPSS,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-CHSWEB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-CORE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-DESK,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-DSYNC,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-ENGCAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-ENGICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-ENGWEB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-FINCAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-FINICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-FINWEB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-FRECAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-FREICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-FREWEB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-GERCAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-GERICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-GERWEB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-IMAP4,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-ITACAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-ITAICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-ITAWEB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-KORCAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-KORICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-KORPSS,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-KORWEB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-LC,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-LDAP,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-MAN,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-NIPCAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-NIPICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-NIPPSS,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-NIPWEB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-NOTES,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-PMOVER,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-POP3,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-PTBCAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-PTBICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-PTBWEB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-RC,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-SMS,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-SPACAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-SPAICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-SPAWEB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-SWECAT,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-SWEICE,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-SWEWEB,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-UNIX,fr=B.06.00,fa=HP-UX_B.10.20_700/800,v=HP
OpenMail.OM-X400,fr=B.06.00,fa=HP-UX_B.10.20_700/800,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_27678
Symptoms:
PHSS_27678:
CR: JAGad71050 SR: 8606201876
Symptoms: Downloaded quoted-printable .CSV (Comma Separated
Values) file attachment to PC is missing carriage returns.
Despite it being perfectly acceptable to MS Excel.
Problem: OM does not know that .CSV files are really text
files and therefore they need their newlines uprated to
CRLF on PCs.
CR: JAGae07887 SR: 8606238864
omcpinu with the '-e' option fails to correctly merge
folders whose names contain multibyte data.
CR: JAGae18540 SR: 8606254208
The check_relay feature of sendmail does not work when
sendmail is invoked from omredirtcp.
CR: JAGae24659 SR: 8606260336
The "man" page for omupdtis etc. gives the directory path
containing the Item Structure Server database (default or
otherwise) as "OMDATADIR/dir/../is/" in 3 places.
Although this is correct, it is not clear to the reader
that the UNIX directory convention of "../" is being used
here to mean "the parent of".
This is confusing and prone to be misinterpreted.
CR: JAGae24724 SR: 8606260401
OpenMail does not support sendmail on AIX 5.1L. The
sendmail.cf file is in a different location compared with
AIX 4.x. In addition, omrc needs to check file permissions
when sendmail versions later than 8.9 are in use.
CR: JAGae24726 SR: 8606260403
omsendin does not recognize the sendmail.cf versions later
than 8.9 included with some releases of Solaris and AIX.
This does not occur with OpenMail B.07 or with OpenMail
B.06 on RedHat Linux.
CR: JAGae26104 SR: 8606261785
The autotests imap_JAGae15283.u and imap_JAGae12028.u fail
about 80% of the time on Linux because they run "StartSvc
imap" immediately after "StopSvc imap" and the imap daemon
fails to start.
On HPUX11, running omoff -s imap followed by omon -s imap,
several times in quick succession causes the state of the
imap to fail to start properly.
CR: JAGae27170 SR: 8606262840
When Bulletin Board changes are being synchronised - if a
basic item (i.e. message content rather than a whole
message) is added to a Bulletin Board and then deleted in
the same email client session the ADD will be synchronised
but the DELETE will not be.
CR: JAGae31209 SR: 8606266965
omredirtcp sometimes cannot be restarted. It either fails
silently or writes a "bind failed: Address already in use"
error message to the syslog.
CR: JAGae32060 SR: 8606267820
Some messages from Exchange to OpenMail contain
incorrectedly encoded WINMAIL.DAT attachments. This illegal
encoding can cause the unix.in process to abort with a
segmentation violation. (This is another example of the
problem described in JAGad95079.)
CR: JAGae33094 SR: 8606268859
A message with a "Mail from" command containing a
comment-only email address coming into OpenMail via the
Internet gateway causes a message with no originator to be
generated. If this message is routed via the X.400 gateway
it is rejected as an originator is a mandatory field.
CR: JAGae33310 SR: 8606269075
When the outbound Internet gateway processes a message that
contains recipients on both the TNEF and MIME routes the
steering file used may be either the MIME one
(~openmail/sys/mimeout.str) or the TNEF one
(~openmail/sys/tnefout.str) depending on the order of the
recipients. The message should be split in this case and
the appropriate steering file used for each type of
recipient.
CR: JAGae33867 SR: 8606269632
Using PC Admin new PDL members cannot be successfully
added. An OM16095 error is reported:
"Illegal attribute type within compound value."
The PDL member can be added successfully using the backend
OpenMail 'omaddpdln' command.
CR: JAGae35717 SR: 8606271509
On AIX 5.1L, the omrc command may give incorrect '[OM
10350] Warning: File system is full' messages. The message
does not state which file system is meant to be full.
PHSS_27060:
CR: JAGad38110 SR: 8606168832
The Web Clients create temporary files under /var/tmp which
may have world-writable permissions, and always have
world-readable permissions.
CR: JAGae12028 SR: 8606245558
Using an IMAP client to copy/move a message from a local
folder to an OpenMail folder leaves the new message with
the user running the IMAP session as the message creator
and an incorrect received date.
This is only a problem if a non-IMAP client is subsequently
used to read the message.
CR: JAGae12031 SR: 8606245561
Using the ICE web client to log on to Openmail - as soon as
you select a button or click on something in the Main Menu
you get the logon page again with a SESSION EXPIRED error
message.
CR: JAGae15283 SR: 8606248886
There are 3 problems in B.06.00
1) The IMAP_AUTOMATIC_MDN general.cfg option is not always
being checked. This means that an acknowledgement may be
sent by the server when this option is not set to TRUE and
the client has not generated an acknowledgement.
This usually happens for the first user. See also
JAGac 78827.
2) Disposition notifications generated by Netscape are not
always detected as such. This means that a message appears
in the sending user's intray, rather than being recorded
against the saved copy of the message in the Pending Tray
being updated. See also JAGad 45462.
3) If an item requires an acknowledgement and
IMAP_AUTOMATIC_MDN is set to FALSE (default), then the item
is not marked as read when opened.
CR: JAGae17136 SR: 8606251070
Handling of the SIGCLD (SIGCHLD) interrupt changed at Dec.
2000 to make the code suitable for both SystemV and BSD
unix variants. However this change has caused some problems
now that the death of a child process is not ignored. These
problems include:
1. ual.remote zombie process accumulating.
2. scripts no longer executable from TCL within web client
page templates.
3. omredirtcp not invoking sendmail successfully in some
circumstances.
CR: JAGae19347 SR: 8606255018
It is not possible to configure the Internet gateway to
produce simple inline RTF content without associated
filename information. This filename info. often causes
email clients to treat the RTF as an attachment.
Configuration for this feature is possible when a
multipart/alternative MIME structure is being generated.
However a Content Disposition of 'inline' isn't
configurable for a simple (non-multipart/alternative)
content unless a 'filename' attribute is added as well.
CR: JAGae22300 SR: 8606257997
When the Internet Gateway is configured to use the content
T.61 subject as the MIME 'filename' a long T.61 subject can
cause a Segmentation Violation in unix.out.
CR: JAGae22536 SR: 8606258235
A badly formed RCPT TO: address of the form:
";"dept.acme.com
results in a looping unix.in process.
PHSS_26276:
CR: JAGad84900 SR: 8606215723
The individual X.400 printable string attributes of a mail
address, of all ORNs within a message, are being truncated
to the size limits imposed by the X.400 Standard, by the
incoming Internet Gateway.
This can cause confusing and incomplete addresses in the
ORN, particularly in the fields holding the Internet
address.
CR: JAGad95079 SR: 8606226007
Some messages from Exchange to OpenMail contain
incorrectedly encoded WINMAIL.DAT attachments. This illegal
encoding can cause the unix.in process to abort with a
segmentation violation.
CR: JAGad97183 SR: 8606228125
When a Service Router rule is set up to REJECT a message
using the RECIPIENT-SERVICE-LEVEL criterion the
non-delivery notification (NDN) generated incorrectly
specifies the NDN reason as "Mailbox exceeds size limit".
The correct text should be:
"The message could not be delivered to the recipient as the
service level for their mailbox doesn't allow that
operation".
CR: JAGad97593 SR: 8606228536
With Portal Access enabled, when a duplicate username is
entered, the ICE Web Client 6.0 user program should display
the Duplicate Usernames page containing a list of
alternative names from which to pick the correct name.
When used with a Web Client 5.10 profile, this list of
alternative names is not displayed and the Duplicate
Usernames page stalls at this point: Please select an
alternative from:
At GR6, the Duplicate Usernames page is not even displayed
at all; the Logon page remains without any feedback that
something is amiss.
CR: JAGae02798 SR: 8606233575
For some IMAP clients (e.g. Outlook Express) the date of
messages in a sub-folder is the date the message was copied
to the folder rather than the date the message was
received.
CR: JAGae06468 SR: 8606237428
omdosur fails with the error message "(OM 24602) Cannot
create file"
CR: JAGae07450 SR: 8606238426
The first mailnode created on a system is not always made
the Primary Mailnode. Shown by absence of '**' in omshowmn
output.
Virtual Licensing assumes that this mailnode to be the
Primary Mailnode, which it needs to refer to.
As a result, Virtual License Server crashes, with
Segmentation Violation, when trying to grant licenses that
have been requested but not yet granted.
May occur during start-up if the request was made while the
system is shut down, or at the time of the request if
system is up.
PHSS_25646:
CR: JAGad83534 SR: 8606214343
If an auto-redirect is enabled for a users inbox, then all
other auto- actions are excluded from execution for that
mailbox.
CR: JAGad83915 SR: 8606214723
If, when creating an auto-forward rule using the PAW-client
the user deletes the auto-forward covering text, local
delivery fails to forward the message.
CR: JAGad83932 SR: 8606214740
B.06 and B.07
This concerns the UAL Checklist command, when the flag is
set to search the directory on the internet-addr (167)
attribute.
When more than one match is found, the command does not
return the entries found as alternatives. This is unlike
UAL Checkname, which does.
This affects the OMGUI, for example. When entering the
duplicate internet address into a DL, the behaviour varies
depending on whether the Auto Name Checking option is on.
If on, Checkname is used, and you see the X400 attributes
of the entries. If off, you get an error when the message
is Mailed. When you click on the name in error, you get a
message that no alternatives can be displayed, or else you
get an empty box that is supposed to show the alternatives.
CR: JAGad84893 SR: 8606215716
If a message that contains an ORN with a DDVn field greater
than the maximum 128 bytes, the X400 outgoing gateway
correctly rejects this message, and will generate a
non-delivery if appropriate.
If the message is a return of contents (the normal type of
non-delivery), then all subsequent messages that are not
return of contents will be rejected by the gateway. An
error 6019 appears in the omshowlog output for each
rejected message.
After a number of the 6019 errors (200 at most), the
gateway will abort, with log output showing 'too many
transaction files open'.
CR: JAGad84922 SR: 8606215745
If no auto-reply text is provided for an auto-reply rule,
then local delivery fails to send the auto-reply message.
CR: JAGad87649 SR: 8606218500
Using the Outlook client delegate permissions cannot be set
if the delegate has the Common Name (CN) attribute set. An
error is displayed in the Outlook interface.
CR: JAGad88671 SR: 8606219531
When the X400 outgoing gateway processes a message with a
non-textual content item, and with GENERATE_FTPBP=TRUE in
the ~sys/madmd.cfg file, x400.hpx.out leaks approximately
4Kbytes of memory on the message.
The workaround is to stop and start the X400 gateway
periodically, before the process fails with insufficient
memory.
CR: JAGad90057 SR: 8606220921
An Internet Ack which contains a NULL character will cause
unix.in to fail.
CR: JAGad91276 SR: 8606222161
omupdtis does not return an error result when interrupted.
CR: JAGad93282 SR: 8606224187
The unix.out gateway, when processing tnef routed messages,
should generate IDs for Mapi Named Properties, in the range
8000-FFFE. The gateway increments the ID each time that a
named property is processed, generating IDs like 80000003,
8001000b, 80020003....
If the gateway runs for some time, the Named Property IDs
become undefined, once FFFE has been reached.
CR: JAGad94888 SR: 8606225815
The OpenMail daemons omvvrelay, ompop3, omimap and omportal
(B.06.00) cannot be started or stopped manually by root in
a VirtualVault 4.5 environment, due to root not having
sufficient authorisation.
CR: JAGad95463 SR: 8606226394
This applies to B.06 and B.07 of the Openmail Server. See
also JAGad 94299, against the MAPI Service Providers.
With the outgoing internet tnef gateway configured to
convert rtf to text (tnefout.str), and with the
OMDATADIR/sys/general.cfg option
UXO_NO_RETAIN_IF_CONVERTED=TRUE set,
1) In Outlook/OpenMail begin to create a 'New Message'.
2) Add a Subject, an Exchange users name and some message
text to the body.
3) Save and close the message.
4) Open message; add some more text and send it to the
Exchange user.
5) The Exchange user receives a message with a blank
message body.
PHSS_25462:
CR: JAGad88889 SR: 8606219749
IMAP: rereading messages with many attachments can result
in raw base64 encoded information being displayed.
CR: JAGad90490 SR: 8606221356
Reading Non-Delivery Notifications for a non-english user
(e.g. German) using an IMAP cleint (e.g. Netscape
Navigator) gives text when the accented characters (e.g.
umlaute) are displayed incorrectly.
PHSS_24874:
CR: JAGad30137 SR: 8606160818
OpenMail B.06.00.00 + MayPP00
unix.in might hang and a message queued on the sendmail
queue when the message contains one part only, which is a
distribution list.
Workaround: Prior to sending the DL, add some text in the
body part of the message.
CR: JAGad31466 SR: 8606162150
One-way disrsync agreement between OpenMail and Exchange
(over OMEXCONN). Updates are done on the Exchange server.
When modifying attributes 111 and PHONE-1, then the next
dirsync results in the full loss of tis modified entry
within the OM directory. (However, the next dirsync cycle
will add the corrected entry again).
CR: JAGad65896 SR: 8606196695
HPUX 11.x - 10.x
Openmail 6.0 Dec '00 PP
The incoming internet gateway, unix.in, loops if supplied
with a bad RCPT_TO or Arpa ORN that contains more than one
sign.
For instance,
&