From owner-freebsd-arch Tue Feb 11 15:10:34 2003 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B72C837B401 for ; Tue, 11 Feb 2003 15:10:32 -0800 (PST) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id E167543FA3 for ; Tue, 11 Feb 2003 15:10:31 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.6/8.12.6) with ESMTP id h1BNAUbs019098 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Tue, 11 Feb 2003 18:10:30 -0500 (EST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.6/8.12.6/Submit) id h1BNAUBS019097; Tue, 11 Feb 2003 18:10:30 -0500 (EST) (envelope-from wollman) Date: Tue, 11 Feb 2003 18:10:30 -0500 (EST) From: Garrett Wollman Message-Id: <200302112310.h1BNAUBS019097@khavrinen.lcs.mit.edu> To: wes@softweyr.com Subject: Re: syslog.conf syntax change (multiple program/host specifications) In-Reply-To: <200302111430.03156.wes@softweyr.com> References: <20030210114930.GB90800@melusine.cuivre.fr.eu.org> Organization: MIT Laboratory for Computer Science Cc: arch@FreeBSD.org Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <200302111430.03156.wes@softweyr.com> you write: >Excellent. I have another simple change to syslog I want to cast before the >audience for consideration. I have had near the bottom of the CFT pile for some time now a project to do the following (which your example is just crying out for): 1) Integrate syslogd and newsyslog. 2) Replace syslog.conf and newsyslog.conf with a new configuration file that contains complete descriptions of log sources and destinations. As a part of (2) I have been thinking at very low priority about how to represent the new configuration file, and I've come to the conclusion that XML is probably the best answer. Although XML syntax is vile, it is also unambiguous and relatively easy to parse (particularly given that we now have an XML lexer library in the base system). It also has the benefit that it can be easily transformed into a human-readable description of log configuration, which might make some tasks easier. Before starting on this I wanted to take up a somewhat easier task, like inetd, which is also crying for relief from its kluge-encrusted historical syntax. -GAWollman -- Garrett A. Wollman | [G]enes make enzymes, and enzymes control the rates of wollman@lcs.mit.edu | chemical processes. Genes do not make ``novelty- Opinions not those of| seeking'' or any other complex and overt behavior. MIT, LCS, CRS, or NSA| - Stephen Jay Gould (1941-2002) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message