SUMMARY: syslogd dies on 2.6

matthew zeier (mrz@3com.com)
Tue, 03 Mar 1998 11:52:48 -0800 (PST)

Original question:

> I've got two nearly identical Solaris 2.6 machines (one has the 2.6
> recommended patches, the other doesn't). One's my desktop machine and
> the other's a mailhost.
>
> I've noticed that over the course of a week, syslogd will just die for
> no apparent reason. Can't locate a left over core file either. Anyone
> having similar problems or know of a fix I might have over looked?

Solution (from "Jody L. Baze" <jody@blueskytours.com>):

Date: Mon, 2 Mar 1998 17:19:56 -0700 (MST)
From: "Jody L. Baze" <jody@blueskytours.com>
To: matthew zeier <mrz@3com.com>
Subject: Re: syslogd dies on 2.6

This is a well-known problem with 2.6 - I've had a bug report files for
months now. If Sun has a patch they haven't let me know... Anyway, the
problem is an apparent race condition that allows a HUP through when there's
no handler for it. You can easily reproduce the problem by HUPing syslogd
3-4 times.

My workaround was to use the the syslogd from 2.5.1. Good luck!

JLB

--
Jody L. Baze                 Blue Sky Tours, Inc.
Software Development         10832 Prospect Avenue N.E.
System Administration        Albuquerque, NM  87112
jody@BlueSkyTours.COM        (505) 293-9462

--
matthew zeier -- mrz@3com.com -- 3Com EWD Engineering -- 408/764-8420
......................................................................
"Y el mundo se mueve, mas rapido y mejor." - Fey