<html><head><meta name="color-scheme" content="light dark"></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">OBSOLETE Patch-ID# 110946-05
Keywords: syslogd SIGHUPS descriptor IPv6 log messages
Synopsis: Obsoleted by: 110946-06 SunOS 5.8_x86: /usr/sbin/syslogd patch
Date: Mar/08/2002

Install Requirements: See 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

BugId's fixed with this patch: 4309712 4323101 4336917 4337337 4345133 4345785 4353901 4357732 4374785 4385688 4386798 4408797 4413974 4416744 4429942 4463575 4476741 4477565 4519254 4614036

Changes incorporated in this version: 4519254 4614036

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:

4614036 *syslogd* incorrectly logs kern messages under user facil. from remote machines
4519254 *syslogd* does not check the 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* 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-8 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:	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 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:  Wednesday, June 26, 2002

</pre></body></html>