Date: 20 Feb 2001 16:19:10 -0500 From: Randell Jesup <rjesup@wgate.com> To: Jonathan Lemon <jlemon@flugsvamp.com> Cc: Jonathan Graehl <jonathan@graehl.org>, freebsd-arch@FreeBSD.ORG Subject: Re: modifying config files for a running daemon Message-ID: <ybubsrx2gtt.fsf@jesup.eng.tvol.net.jesup.eng.tvol.net> In-Reply-To: Jonathan Lemon's message of "Tue, 20 Feb 2001 14:58:43 -0600" References: <20010220105723.C85542@prism.flugsvamp.com> <NCBBLOALCKKINBNNEDDLMEECDLAA.jonathan@graehl.org> <20010220145843.D85542@prism.flugsvamp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jonathan Lemon <jlemon@flugsvamp.com> writes:
>On Tue, Feb 20, 2001 at 12:48:19PM -0800, Jonathan Graehl wrote:
>> Is there any way to be sure of receiving a change notification only
>> after the writer has closed the file?
>
>No, I don't think so. But even if that was the case, it doesn't eliminate
>the race condition where another process can open the file after the
>notification was sent.
Assuming the writers are using flock() (exclusive), you have the
reader use flock() (perhaps/probably in shared mode). As the original
author said, this doesn't obviate the need to deal with locks.
--
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ybubsrx2gtt.fsf>