From owner-freebsd-arch Mon Feb 19 2:18: 2 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id CAE5937B401 for ; Mon, 19 Feb 2001 02:17:59 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1JAHvJ06940; Mon, 19 Feb 2001 02:17:57 -0800 (PST) Date: Mon, 19 Feb 2001 02:17:57 -0800 From: Alfred Perlstein To: Terry Lambert Cc: josb@cncdsl.com, arch@FreeBSD.ORG Subject: Re: DJBDNS vs. BIND Message-ID: <20010219021757.L6641@fw.wintelcom.net> References: <20010218233916.J28286@lizzy.bugworks.com> <200102191012.DAA17412@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102191012.DAA17412@usr05.primenet.com>; from tlambert@primenet.com on Mon, Feb 19, 2001 at 10:12:05AM +0000 X-all-your-base: are belong to us. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Terry Lambert [010219 02:12] wrote: > > PS: on a similar note, I think there should be a 10 second or so > timer in inetd, and it should stat the inetd.conf file for changes, > so we no longer have to put up with cached state until we HUP the > thing. I think "init" should have a similar thing for /etc/ttys; > cached state data is inherently bad everywhere, not just in DNS > servers. > You scare me, I was thinking just the same thing about mountd earlier today. Only problem is that it violates POLA(* heh), one could offer an command line option to have it watch the file. (*) tmpwatch Another idea, instead of having to graft some interface and repeat it over and over with inetd/mountd/init, one could even write a program whos responsibility it was to sit in a poll()/kevent() look watching these conf files and sending the appropriate signals to them. Of course it would monitor its own config file for changes. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message