From owner-freebsd-bugs Thu May 7 05:23:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05870 for freebsd-bugs-outgoing; Thu, 7 May 1998 05:23:00 -0700 (PDT) (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 FAA05839 for ; Thu, 7 May 1998 05:22:52 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id FAA14608; Thu, 7 May 1998 05:20:01 -0700 (PDT) Date: Thu, 7 May 1998 05:20:01 -0700 (PDT) Message-Id: <199805071220.FAA14608@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: Sakari Jalovaara Subject: Re: bin/2191: syslogd stops logging after several hours of load - FDIV048 Reply-To: Sakari Jalovaara Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/2191; it has been noted by GNATS. From: Sakari Jalovaara To: FreeBSD-gnats-submit@freebsd.org Cc: Subject: Re: bin/2191: syslogd stops logging after several hours of load - FDIV048 Date: Thu, 7 May 1998 15:11:55 +0300 >Synopsis: syslogd stops logging after several hours of load - FDIV048 One possibility for syslogd's erratic behavior is that it does complicated things in signal handlers. Seems to me it can end up recursively calling functions that break due to static variables or getting mixed up with linked list handling (ouch). bin/5548 seems related, maybe other syslogd-related ones too (bin/6216?) ++sja To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message