From owner-freebsd-questions Fri Feb 6 03:06:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18034 for questions-outgoing; Fri, 6 Feb 1998 03:06:49 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from silver.sms.fi (silver.sms.fi [194.111.122.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA17994 for ; Fri, 6 Feb 1998 03:06:43 -0800 (PST) (envelope-from pete@silver.sms.fi) Received: (from pete@localhost) by silver.sms.fi (8.8.8/8.7.3) id NAA07686; Fri, 6 Feb 1998 13:06:39 +0200 (EET) Date: Fri, 6 Feb 1998 13:06:39 +0200 (EET) Message-Id: <199802061106.NAA07686@silver.sms.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Petri Helenius To: freebsd-questions@FreeBSD.ORG Subject: syslogd problem X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe questions" I've a problem in 2.2-STABLE cvsupped about a week ago (but the problem existed earlier also) that syslogd stops logging messages received over network after a while, usually after when a router or similar device in the network has been reset. The only way to restore functionality is to kill and restart syslogd. This used not to happen about half a year ago. Any ideas what might be causing this? Pete