From owner-freebsd-questions Tue Jun 9 09:23:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02960 for freebsd-questions-outgoing; Tue, 9 Jun 1998 09:23:06 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from blues.jpj.net (benh@blues.jpj.net [204.97.17.146]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02851 for ; Tue, 9 Jun 1998 09:22:38 -0700 (PDT) (envelope-from benh@blues.jpj.net) Received: from localhost (benh@localhost) by blues.jpj.net (backatcha) with SMTP id MAA13504 for ; Tue, 9 Jun 1998 12:22:26 -0400 (EDT) Date: Tue, 9 Jun 1998 12:22:26 -0400 (EDT) From: Ben Hockenhull To: questions@FreeBSD.ORG Subject: enhanced syslogd? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I set up a dedicated loghost on my network a while back and used the standard local log facilities to log activity from various devices to the loghost. However, I've run clean out of free facilities and have more devices to log than ever. Anyone else had this problem before? I'd rather not aggregate logs from multiple devices into one file if possible. What I need, I suppose, is an enhanced syslogd with support for a large number of facilities as well as patches to the system to add support for these facilities to syslog(3). Surely someone else has encountered this problem before. Any pointers? Ben -- Ben Hockenhull benh@jpj.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message