Patch-ID# 110946-10
Download this patch from My Oracle Support
Your use of the firmware, software and any other materials contained
in this update is subject to My Oracle Support Terms of Use, which
may be viewed at My Oracle Support.
|
For further information on patching best practices and resources, please
see the following links:
|
Copyright (c) 2012, Oracle and/or its affiliates. All rights reserved.
|
Keywords: security syslogd sighups descriptor ipv6 log messages core
Synopsis: SunOS 5.8_x86: /usr/sbin/syslogd patch
Date: Aug/08/2008
Install Requirements: See Special Install Instructions
Reboot after installing this patch to activate the changes delivered. An alternative may be specified in the Special Install Instructions.
Solaris Release: 8_x86
SunOS Release: 5.8_x86
Unbundled Product:
Unbundled Release:
Xref: This patch available for SPARC as patch 110945
Topic: SunOS 5.8_x86: /usr/sbin/syslogd patch
NOTE: Refer to Special Install Instructions section for
IMPORTANT specific information on this patch.
Relevant Architectures: i386
Bugs fixed with this patch:
Changes incorporated in this version: 6580293
Patches accumulated and obsoleted by this patch:
Patches which conflict with this patch:
Patches required with this patch:
Obsoleted by:
Files included with this patch:
/usr/sbin/syslogd
Problem Description:
6580293 syslogd should use private pool of door server threads
(from 110946-09)
6221022 syslogd grows due to hostname lookup
(from 110946-08)
4772471 console logfile corrupted due to syslogd: some logger thread(s) are stuck
4787413 syslogd Bad terminal owner; root owns '/dev/console' but utmp says LOGIN
4812764 syslogd dumps core with large size (> 1024) packet
(from 110946-07)
4674435 when msgid=0 was configured in log.conf, qfe link messages not logged
4705713 syslogd outputs error messages when shutting down system
(from 110946-06)
4243984 syslogd drops FORW messages
4424387 syslogd gathers unnecessary information
4558909 syslogd stops logging remote messages after restart
4665297 syslogd shuts down itself
4670382 syslogd opens door too early
4670414 syslogd should not close door while reconfiguring
4670468 syslogd does not log its error message
(from 110946-05)
4614036 syslogd incorrectly logs kern messages under user facility from remote machines
4519254 syslogd does not check permissions on the door file
(from 110946-04)
4385688 syslog recurses when memory is low, runs off stack
4476741 syslogd dumps core
4416744 syslogd /etc/.syslog_door should be a relative, not absolute symbolic link
4413974 syslogd syslog.pid should be in /var/run
4477565 syslogd fails to start if /etc/.syslog_door exists and does not point to /var/
4408797 syslogd "symlink failed" message takes two lines
(from 110946-03)
4463575 syslogd ignores log messages sent over IPv6
(from 110946-02)
4429942 syslog incorrectly logs emerg messages when forwarding to remote syslogd
(from 110946-01)
4309712 syslogd hangs on HUP when Lentronic terminal server has flow control enabled
4323101 syslogd on Solaris 7 stops logging if file size exceeds 2gb
4336917 syslogd inherits its parent's behavior for signal HUP
4337337 syslogd leaks file descriptors when sent repeated SIGHUP
4345133 syslogd dies when given lots of SIGHUPS
4345785 syslogd calls perror when stderr points to a bad file
4353901 syslogd can't print Japanese code to remote host
4357732 syslogd debugging information is meaningless
4374785 syslogd mark facility of syslog not time stamping log file properly
4386798 syslogd sometimes hangs when given lots of SIGHUP
Patch Installation Instructions:
--------------------------------
For Solaris 2.0-2.6 releases, refer to the Install.info file and/or
the README within the patch for instructions on using the generic
'installpatch' and 'backoutpatch' scripts provided with each patch.
For Solaris 7-10 releases, refer to the man pages for instructions
on using 'patchadd' and 'patchrm' scripts provided with Solaris.
Any other special or non-generic installation instructions should be
described below as special instructions. The following example
installs a patch to a standalone machine:
example# patchadd /var/spool/patch/104945-02
The following example removes a patch from a standalone system:
example# patchrm 104945-02
For additional examples please see the appropriate man pages.
Special Install Instructions:
-----------------------------
NOTE 1: It is necessary to restart syslogd after patch installation
in order to run with the latest version of syslogd included
in this patch. Execute the following commands as root:
# /etc/init.d/syslog stop
# /etc/init.d/syslog start
NOTE 2: The fix for bug 4309712 can cause the sending of a mail
message to the superuser. When syslogd receives a HUP
signal, it attempts to close all log files to which it
is currently logging messages. If for some reason, one
of these files does not close within a generous grace
period, syslogd shuts down, logging an error message to
the console. If the console is one of the files which
did not successfully close, syslogd instead sends a mail
message to the superuser on the current system stating
that it shut down, and that the console was not responding.
NOTE 3: The fix for bug 4353901 fully allows forwarding of messages
which contain characters defined in the system default
locale. Care should be taken to ensure that each window
displaying messages forwarded by syslogd (especially
console windows) is run in the system default locale (which
is syslogd's locale). If this advice is not followed, it
may be possible for a syslog message to alter the terminal
settings for that window, possibly even allowing remote
execution of arbitrary commands from that window.
README -- Last modified date: Friday, November 9, 2012