Patch-ID# 110945-08
Keywords: security syslogd sighups descriptor ipv6 log messages syslog.pid core
Synopsis: SunOS 5.8: /usr/sbin/syslogd patch
Date: May/29/2003


Install Requirements: See Special Install Instructions                      
                      
Solaris Release: 8

SunOS Release: 5.8

Unbundled Product: 

Unbundled Release: 

Xref: This patch available for x86 as patch 110946

Topic: SunOS 5.8: /usr/sbin/syslogd patch
	NOTE:   Refer to Special Install Instructions section for
                IMPORTANT specific information on this patch.

Relevant Architectures: sparc

BugId's fixed with this patch: 4243984 4309712 4323101 4336917 4337337 4345133 4345785 4353901 4357732 4374785 4385688 4386798 4408797 4413974 4416744 4424387 4429942 4463575 4476741 4477565 4519254 4558909 4614036 4665297 4670382 4670414 4670468 4674435 4705713 4772471 4787413 4812764

Changes incorporated in this version: 4772471 4787413 4812764

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:

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 110945-07)
 
4674435 When msgid=0 was configured in log.conf, qfe link messages wasn't logged.
4705713 *syslogd* outputs error messages when shutting down the system
 
(from 110945-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 110945-05)
 
4614036 *syslogd* incorrectly logs kern messages under user facil. from remote machines
4519254 *syslogd* does not check the permissions on the door file
 
(from 110945-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 110945-03)
 
4463575 syslogd ignores log messages sent over IPv6
 
(from 110945-02)
 
4429942 syslog incorrectly logs emerg messages when forwarding to remote syslogd
 
(from 110945-01)
 
4309712 *syslogd* hangs on HUP when Lentronic terminal server has flow control enabled
4323101 *syslogd* 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-9 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: 
When syslogd receives a HUP signal, it attempts to complete
outputting pending messages, and close all log files to
which it is currently logging messages. If, for some reason,
one (or more) of these files does not close within a gen-
erous grace period, syslogd discards the pending messages,
forcibly closes these files, and starts reconfiguration. If
this shutdown procedure is disturbed by an unexpected error
and syslogd cannot complete reconfiguration, syslogd sends a
mail message to the superuser on the current system stating
that it has shut down, and exits. 

 
NOTE 2:	
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:  Tuesday, March 23, 2004