PROBLEM:  (TKTB51380)	(Patch ID: OSF410-088)
********
This patch fixes a problem in which the syslogd program cannot properly forward
large messages to remote systems.  It will either write them to the wrong 
facility (specified in /etc/syslog.conf) or write incomplete data.

PROBLEM:  (SSRT0499U)            (Patch ID: OSF410-119)
********
A potential security vulnerability has been discovered in syslod, where under 
certain circumstances, system integrity may be compromised. This may be in the 
form of improper file or privilege management. Digital has corrected this 
potential vulnerability.

Information for installing a new version of the syslogd command. 

If your system is configured to forward syslog messages from one host to 
another, become superuser (for example, root) and manually create a 
/etc/syslog.auth file.

The /etc/syslog.auth file specifies which remote hosts are allowed to forward
syslog messages to the local host. Each remote host name should appear in a
separate line in the /etc/syslog.auth file.  A line that starts with the '#'
character is considered as a comment and is ignored.  A host name must be a
complete domain name for example, trout.nyc.com.  If a domain host name is
given, it must either appear in the local /etc/hosts file or be able to be
resolved by the name server (for example, BIND) that is running on the system.

Note that a host name can have at most as many characters as defined by the
MAXHOSTNAMELEN constant in <sys/param.h>. However, each line in the
/etc/syslog.auth file can have up to 512 characters.

The /etc/syslog.auth file must be owned by root and have permissions set to
0600.

Unless the domain host name of a remote host is given in the local file, the 
local host will not log any syslog messages from that remote host.

If the /etc/syslog.auth file does not exist or it exists but is empty or has
no valid remote host names in it, the system will assume no remote host is
allowed to forward syslog messages to the local host.

PROBLEM:  (QAR 51348)             (Patch ID: OSF410-130)
********
This patch fixes a panic that occurs when the system's message buffer size is
increased to beyond the default size of 4096.  During the subsequent reboot,
the syslogd daemon fails with a "Segmentation fault (core dumped)" message,
and creates a core file in the "/" directory.

PROBLEM:  (MCPM309FT, QAR 58021)         (Patch ID: OSF410-142)
********
This patch fixes a problem in which the syslogd daemon may hang when writing
to a named pipe log file.

The following is an example of a stack trace:

   thread_block()
   mpsleep()
   fifo_open()
   vn_open()
   copen()
   open()

PROBLEM:  (HPAQ706FK, BCGM708HD)    (Patch ID: OSF410-198)
********
This patch fixes a problem when setting up the syslogd.auth file for remote
loggging, if there are more than 23 entries in the file, syslogd -d coredumps 
when started.