From owner-freebsd-arch Mon Feb 19 10:29:16 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 4732437B491 for ; Mon, 19 Feb 2001 10:29:12 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f1JIT6l37371; Mon, 19 Feb 2001 10:29:06 -0800 (PST) (envelope-from dillon) Date: Mon, 19 Feb 2001 10:29:06 -0800 (PST) From: Matt Dillon Message-Id: <200102191829.f1JIT6l37371@earth.backplane.com> To: Alfred Perlstein Cc: Terry Lambert , josb@cncdsl.com, arch@FreeBSD.ORG Subject: Re: DJBDNS vs. BIND References: <20010218233916.J28286@lizzy.bugworks.com> <200102191012.DAA17412@usr05.primenet.com> <20010219021757.L6641@fw.wintelcom.net> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> 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. I was thinking just having a 'mountd -reload'. I don't like the idea of programs polling configuration files. I actually used a similar mechanism in Diablo and wound up having to add hacks to, for example, try to avoid catching a configuration file in the middle of being written out by an editor. A better way would be to take the 'vipw' concept and write a general system utility to edit configuration files that does the right thing when you write the config file out (heh heh... based on.... another config file!). -Matt :(*) 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] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message