From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Terje Malmedal <terje.malmedal@usit.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: directory notification.
Date: Wed, 5 Nov 2003 13:15:09 +1100 [thread overview]
Message-ID: <20031105131509.23d38c58.sfr@canb.auug.org.au> (raw)
In-Reply-To: <E1AH5ED-0005Qm-00@aqualene.uio.no>
On Tue, 4 Nov 2003 18:44:29 +0100 Terje Malmedal <terje.malmedal@usit.uio.no> wrote:
>
> Modifications of existing files via NFS are not picked up by the
> directory notification system.
>
> kernel is 2.4.22, I'm testing with the example program from
> /usr/src/linux/Documentation/dnotify.txt
>
> I get notifications on the following:
> nfs-server# echo hello >> existing.file
> nfs-client# echo hello > new.file
>
> But not on this:
> nfs-client# echo hello >> existing.file
>
> I guess the problem of detecting changes done via NFS is similar to
> the problem of multiple hard-links to the same file, which is
> documented as not supported.
>
> Is this something that can be fixed, or is it going to be too
> difficult to go from NFS-handle and back to the directory it came
> from?
Are you running the program that expects notifies on the NFS server or the
client? If on the client, you will never get notifies for modifications
made on the server or other clients. If on the server, it needs looking
at as you should get the notifies (I think - it has been a while since I
last looked at the NFS server code).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
next prev parent reply other threads:[~2003-11-05 2:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 17:44 directory notification Terje Malmedal
2003-11-05 2:15 ` Stephen Rothwell [this message]
2003-11-05 10:22 ` Terje Malmedal
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=20031105131509.23d38c58.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=terje.malmedal@usit.uio.no \
/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).