From owner-freebsd-bugs  Sun Nov 29 09:19:28 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA15017
          for freebsd-bugs-outgoing; Sun, 29 Nov 1998 09:19: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 JAA14992
          for <freebsd-bugs@FreeBSD.org>; Sun, 29 Nov 1998 09:19:25 -0800 (PST)
          (envelope-from gnats@FreeBSD.org)
Received: (from Unknown UID 563@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id JAA24968;
	Sun, 29 Nov 1998 09:20:03 -0800 (PST)
Date: Sun, 29 Nov 1998 09:20:03 -0800 (PST)
Message-Id: <199811291720.JAA24968@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.ORG
From: support@uunet.ca
Subject: i386/8847: /usr/sbin/syslogd stops logging
Reply-To: support@uunet.ca
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR i386/8847; it has been noted by GNATS.

From: support@uunet.ca
To: freebsd-gnats-submit@FreeBSD.ORG
Cc:  Subject: i386/8847: /usr/sbin/syslogd stops logging
Date: Tue, 24 Nov 1998 08:45:00 -0800 (PST)

 >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
 
 

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