From owner-freebsd-bugs  Tue Nov 24 08:49:28 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA10747
          for freebsd-bugs-outgoing; Tue, 24 Nov 1998 08:49:28 -0800 (PST)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10590
          for <freebsd-bugs@FreeBSD.org>; Tue, 24 Nov 1998 08:49:24 -0800 (PST)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id IAA10752;
	Tue, 24 Nov 1998 08:50:02 -0800 (PST)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA10187;
          Tue, 24 Nov 1998 08:45:00 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199811241645.IAA10187@hub.freebsd.org>
Date: Tue, 24 Nov 1998 08:45:00 -0800 (PST)
From: support@uunet.ca
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: i386/8847: /usr/sbin/syslogd stops logging
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         8847
>Category:       i386
>Synopsis:       /usr/sbin/syslogd stops logging
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Nov 24 08:50:01 PST 1998
>Last-Modified:
>Originator:     Support
>Organization:
Support
>Release:        2.2.6-RELEASE
>Environment:
FreeBSD machine.name 2.2.6-RELEASE FreeBSD 2.2.6-RELEASE #0: Wed Mar 25
02:2:49 GMT 1998 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386
>Description:
After a random period of time, syslog will stop logging but will
not exit. It must be killed and restarted manually. Oddly enough,
it *will* log itself being killed, but otherwise it logs nothing.
>How-To-Repeat:
Simply wait and log a whole *pile* of stuff. We're logging a lot
of stuff on one of these machines and syslogd seems to not handle
it very well. Considering upgrading machine to 3.0-RELEASE if no
workaround or patch information becomes available.
>Fix:
None, unless you consider restarting it manually a 'fix'.
>Audit-Trail:
>Unformatted:

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