From owner-freebsd-arch Tue Feb 20 13:12:35 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 7917437B401 for ; Tue, 20 Feb 2001 13:12:32 -0800 (PST) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net ([10.32.2.26]) by mail.wgate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 152CZ9H7; Tue, 20 Feb 2001 16:12:27 -0500 Reply-To: Randell Jesup To: "Jonathan Graehl" Cc: Subject: Re: modifying config files for a running daemon References: From: Randell Jesup Date: 20 Feb 2001 16:13:03 -0500 In-Reply-To: "Jonathan Graehl"'s message of "Tue, 20 Feb 2001 12:48:19 -0800" Message-ID: User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jonathan Graehl" writes: >Is there any way to be sure of receiving a change notification only after the >writer has closed the file? At the moment, I don't think so, since there's no change notification. Certainly it wouldn't be tough to create a protocol/API that provided that functionality, at least if you can guarantee that the writer uses the protocol, or by use of a special pseudo-fs, etc. Since a change-notification protocol/API would need to be defined anyways, there wouldn't be a problem including this. I believe that the support for file notification in the Amiga ramdisk notified on close of a modified file (I've lost too many neurons to be sure). Providing it on an arbitrary FS _without_ requiring the writer to use the defined protocol would be quite a hairy change to make, of course. -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message