From owner-freebsd-ports Mon Apr 24 21:26:56 2000 Delivered-To: freebsd-ports@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id A218B37B7AC for ; Mon, 24 Apr 2000 21:26:52 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id AAA11013; Tue, 25 Apr 2000 00:26:55 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Tue, 25 Apr 2000 00:26:54 -0400 (EDT) From: Chuck Robey To: Will Andrews Cc: FreeBSD Ports Subject: Re: syslog-ng's category (see PR 18187) In-Reply-To: <20000425001747.B445@argon.blackdawn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 25 Apr 2000, Will Andrews wrote: > Hi, > > I'm ready to import syslog-ng as per PR 18187, with minor changes. However, > I'm torn between importing it into security and sysutils. > > Can anyone offer a recommendation? Noting that both are reasonable answers, I would say that since it's only a user of security, and doesn't either provide security to other services or audits (only use security in providing it's own service) I would stick it into sysutils. rsaref is an example that provides security, and whisker is something that provides security auditing ... both of which seem to me to be legitimately in security. Something that is a user of security, well ... On top of which, I *think*, if I were looking for alternative syslog tools, I'd probably look into sysutils first, wouldn't you? > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message