From owner-freebsd-arch Tue Feb 20 12:47:20 2001 Delivered-To: freebsd-arch@freebsd.org Received: from molly.straylight.com (molly.straylight.com [209.68.199.242]) by hub.freebsd.org (Postfix) with ESMTP id 615FF37B491 for ; Tue, 20 Feb 2001 12:47:16 -0800 (PST) (envelope-from jonathan@graehl.org) Received: from dickie (case.straylight.com [209.68.199.244]) by molly.straylight.com (8.11.0/8.10.0) with SMTP id f1KKlBC00848 for ; Tue, 20 Feb 2001 12:47:11 -0800 From: "Jonathan Graehl" To: Subject: modifying config files for a running daemon Date: Tue, 20 Feb 2001 12:48:19 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal In-Reply-To: <20010220105723.C85542@prism.flugsvamp.com> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way to be sure of receiving a change notification only after the writer has closed the file? I suppose that such a notification would not obviate flock(2)ing between editors (a quick glance at contrib/nvi shows that vi uses flock) and daemons (although, e.g. inetd simply opens the file without locking) -JG > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message