From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Heikki Orsila <shd@modeemi.cs.tut.fi>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Chubb <peterc@gelato.unsw.edu.au>
Subject: Re: fcntl(F_GETLEASE) semantics??
Date: Thu, 11 Aug 2005 14:56:59 -0400 [thread overview]
Message-ID: <1123786619.7095.47.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20050811184144.GE31158@jolt.modeemi.cs.tut.fi>
to den 11.08.2005 Klokka 21:41 (+0300) skreiv Heikki Orsila:
> Peter Chubb <peterc@gelato.unsw.edu.au> wrote:
> > if (fcntl(fd, F_SETLEASE, F_RDLCK) == -1)
> > fail;
>
> Is that something inotify can do? If so, then should F_SETLEASE/GETLEASE
> be deprecated for future? F_SETLEASE is Linux specific, and inotify is
> generally more useful. It looks like inotify could be used to detected
> changes in any file.
inotify does not give you synchronous notification. It just tells you
something has happened after the fact. Not the same thing at all.
Cheers,
Trond
next prev parent reply other threads:[~2005-08-11 18:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 23:48 Peter Chubb
2005-08-11 1:14 ` Trond Myklebust
2005-08-11 1:29 ` Peter Chubb
2005-08-11 8:14 ` fcntl(F GETLEASE) semantics?? Michael Kerrisk
2005-08-11 11:51 ` Trond Myklebust
2005-08-11 12:27 ` Michael Kerrisk
2005-08-11 12:49 ` Trond Myklebust
2005-08-11 13:22 ` Michael Kerrisk
2005-08-11 14:06 ` Trond Myklebust
2005-08-11 14:12 ` Trond Myklebust
2005-08-11 14:20 ` J. Bruce Fields
2005-08-11 14:42 ` Michael Kerrisk
2005-08-11 14:40 ` Michael Kerrisk
2005-08-11 15:06 ` Trond Myklebust
2005-08-11 15:25 ` Trond Myklebust
2005-08-11 14:10 ` Stephen Rothwell
2005-08-11 18:41 ` fcntl(F_GETLEASE) semantics?? Heikki Orsila
2005-08-11 18:56 ` Trond Myklebust [this message]
2005-08-11 19:02 ` Heikki Orsila
2005-08-11 19:15 ` Trond Myklebust
2005-08-11 19:23 ` Heikki Orsila
2005-08-11 19:31 ` Trond Myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1123786619.7095.47.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=peterc@gelato.unsw.edu.au \
--cc=shd@modeemi.cs.tut.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®