From: Stef Bon <stefbon@gmail.com>
To: Steve French <smfrench@gmail.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
linux-cifs <linux-cifs@vger.kernel.org>
Subject: Re: Possible to make nfs aware of a inotify watch has been set.
Date: Fri, 30 Nov 2012 08:19:52 +0100 [thread overview]
Message-ID: <CANXojcxa98W7buVOgmsjMgrOukiiyVuafHS-NFz_yaSC2OFE1w@mail.gmail.com> (raw)
In-Reply-To: <CANXojcwRy5cBz=E1S567J-1BFC4AiamLr=35bKrX0Zq-Me2b3w@mail.gmail.com>
2012/11/30 Stef Bon <stefbon@gmail.com>:
> 2012/11/30 Steve French <smfrench@gmail.com>:
>> match closely to the existing Linux API.
>
> Hi,
>
> I start working on the seperate notifyfs servers.
> The whole advantage of that approach is that you can design the api
> from scratch. Notifyfs is not bound to the api of inotify. There
> remains the problem of mapping it to the fs event api on the host,
> which will be inotify probably on linux.
>
> At this moment the different events look like:
>
Maybe I will add locking information as well. I see that the
/proc/locks file can be monitored as well.
To me, information is very valuable. It would be very nice (yes my
opinion) to have information about a file on a nfs (or cifs) share
about it lockstatus, and by who, and get notified when it's unlocked.
And no nobody asked me to do so.
Stef
next prev parent reply other threads:[~2012-11-30 7:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 9:32 Possible to make nfs aware of a inotify watch has been set Stef Bon
2012-11-29 14:03 ` Myklebust, Trond
2012-11-29 14:49 ` Stef Bon
2012-11-29 14:54 ` Myklebust, Trond
2012-11-29 15:22 ` simo
2012-11-29 15:33 ` Myklebust, Trond
2012-11-29 16:28 ` Steve French
2012-11-29 17:05 ` Myklebust, Trond
2012-11-29 16:39 ` Stef Bon
2012-11-29 17:11 ` Myklebust, Trond
2012-11-29 20:05 ` simo
2012-11-29 21:09 ` Myklebust, Trond
2012-11-29 22:26 ` simo
2012-11-29 20:10 ` Stef Bon
2012-11-29 20:20 ` Al Viro
2012-11-29 20:31 ` Stef Bon
2012-11-29 21:16 ` Al Viro
2012-11-29 23:14 ` Stef Bon
2012-11-29 23:44 ` Steve French
2012-11-30 7:10 ` Stef Bon
2012-11-30 7:19 ` Stef Bon [this message]
2012-11-30 13:37 ` Bernd Petrovitsch
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=CANXojcxa98W7buVOgmsjMgrOukiiyVuafHS-NFz_yaSC2OFE1w@mail.gmail.com \
--to=stefbon@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=smfrench@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).