From owner-freebsd-arch Tue Feb 20 10: 4:31 2001 Delivered-To: freebsd-arch@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 5B3CD37B401 for ; Tue, 20 Feb 2001 10:04:29 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f1KI4HG45260; Tue, 20 Feb 2001 10:04:17 -0800 (PST) (envelope-from dillon) Date: Tue, 20 Feb 2001 10:04:17 -0800 (PST) From: Matt Dillon Message-Id: <200102201804.f1KI4HG45260@earth.backplane.com> To: Jonathan Lemon Cc: Randell Jesup , Terry Lambert , Alfred Perlstein , josb@cncdsl.com, arch@FreeBSD.ORG Subject: Re: DJBDNS vs. BIND References: <200102200122.SAA04466@usr05.primenet.com> <20010220105723.C85542@prism.flugsvamp.com> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :It would be fairly trivial to monitor a configuration file with kevent, :which would generate a notice whenever the file is changed/copied/renamed, :etc. I believe that John-Mark Gurney had patches somewhere to implement :exactly this for inetd. : :The problem is that under our current model, the administrators do not :expect writes to the file to take immediate effect, and this immediately :breaks POLA. So while it could be done, it may not be a good idea. At :the very least, I would argue that it should be hidden behind a flag option. :-- :Jonathan I don't even think it's that useful. Lets say you have a daemon (say, named) that requires several configuration files and you want to update all of them. Now how do you do it? I much rather like the idea of an editor-wrapper similar to vipw. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message