From owner-freebsd-bugs  Sat May 30 15:47:07 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA18267
          for freebsd-bugs-outgoing; Sat, 30 May 1998 15:47:07 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: (from steve@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA18249;
          Sat, 30 May 1998 15:47:04 -0700 (PDT)
          (envelope-from steve)
Date: Sat, 30 May 1998 15:47:04 -0700 (PDT)
From: Steve Price <steve>
Message-Id: <199805302247.PAA18249@hub.freebsd.org>
To: uhclem@nemesis.lonestar.org, steve, freebsd-bugs
Subject: Re: bin/2191
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: syslogd stops logging after several hours of load - FDIV048

State-Changed-From-To: open-closed
State-Changed-By: steve
State-Changed-When: Sat May 30 15:45:29 PDT 1998
State-Changed-Why: 
PR #5548 seems to be a description of the same problem.
Anyone with plenty of free time on their hands want to
look into cleaning up syslogd's signal handling routines?

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message