From owner-freebsd-questions Tue Oct 1 18:17:10 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA17789 for questions-outgoing; Tue, 1 Oct 1996 18:17:10 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA17784 for ; Tue, 1 Oct 1996 18:17:07 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id VAA25526 for ; Tue, 1 Oct 1996 21:16:55 -0400 (EDT) Date: Tue, 1 Oct 1996 21:16:55 -0400 (EDT) From: Brian Tao To: FREEBSD-QUESTIONS-L Subject: Improved syslogd? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does there exist an improved syslog daemon anywhere? I figure someone has improved upon virtually every other UNIX utility (inetd, portmapper, ftpd, vi, more, etc.), and syslogd would not be a bad candidate to muck with. I'm looking for something that offers greater control over where log messages are sent. It should be able to select based on facility, priority, logging program and originating host. It should handle log rotation itself, rather than relying on something like newsyslog. It should allow inclusive as well as exclusive specification of logging destinations (e.g., I want all messages from ftpd to go to /var/log/ftp.log, but *not* to /var/log/messages). Does such a beast exist, or should I hack one together using my limited set of C and perl skills? ;-) -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't"