From owner-freebsd-hackers  Tue Nov 26 14:21:06 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA00546
          for hackers-outgoing; Tue, 26 Nov 1996 14:21:06 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA00539
          for <hackers@freebsd.org>; Tue, 26 Nov 1996 14:21:03 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.3/8.6.9) with ESMTP id KAA13471; Tue, 26 Nov 1996 10:51:53 -0800 (PST)
To: peter@taronga.com (Peter da Silva)
cc: bmk@fta.com, jgreco@brasil.moneng.mei.com, brantk@atlas.com,
        hackers@freebsd.org
Subject: Re: Replacing sendmail 
In-reply-to: Your message of "Tue, 26 Nov 1996 07:48:58 CST."
             <199611261348.HAA13543@bonkers.taronga.com> 
Date: Tue, 26 Nov 1996 10:51:53 -0800
Message-ID: <13469.849034313@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > That's why I suggest doing this more incrementally by service type.
> 
> But this hasn't got anything to do with services. It has to do with
> security. How about:
> 
> 	security -enable/disable class-of-resources

Not in this particular set of examples, no, but understand that
services have many more options *other* than security which you'd also
eventually want to fold into the same mechanism.  To contrive more examples:

	mail_control -fast_queue_depth 10
	mail_control -bounce_warnings no
	mail_control -add-virtual "fred sfred@scurvy.com"

	lp_control -polled-mode
	lp_control -set-type HP500C

All of which might be reasonable things to want if you were intending
to write a more robust front-end for a variety of service options.

Think "big picture", guys. :-)

					Jordan