From owner-freebsd-arch Mon Feb 19 10:34:31 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 1645B37B491 for ; Mon, 19 Feb 2001 10:34:29 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f1JIXxh98301; Mon, 19 Feb 2001 13:33:59 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 19 Feb 2001 13:33:58 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Matt Dillon Cc: Alfred Perlstein , Terry Lambert , josb@cncdsl.com, arch@FreeBSD.ORG Subject: Re: DJBDNS vs. BIND In-Reply-To: <200102191829.f1JIT6l37371@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Feb 2001, Matt Dillon wrote: > :> 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. Yeah -- automatic rereading of configuration files worries me also. You can end up with races during a file-rewrite. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message