From: Tvrtko Ursulin <tvrtko.ursulin@onelan.co.uk>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>,
John McCutchan <john@johnmccutchan.com>,
Robert Love <rlove@rlove.org>, Eric Paris <eparis@parisplace.org>,
Eric Paris <eparis@redhat.com>,
Nepomuk Mailing List <nepomuk@kde.org>,
Linux Filesystem Development Mailinglist
<linux-fsdevel@vger.kernel.org>
Subject: Re: Better support for (desktop) file search / indexing applications
Date: Mon, 12 Nov 2012 09:10:15 +0000 [thread overview]
Message-ID: <10569573.iu1a6eiZCO@deuteros> (raw)
In-Reply-To: <201211101753.46211.Martin@lichtvoll.de>
On Saturday 10 November 2012 17:53:45 Martin Steigerwald wrote:
> Still fanotify needs root access and thus this would need a daemon running
> as root and some policy kit stuff to access it and in case of mount point
> watches robust and secure code so that each user may only see his/her own
> results.
Perhaps then also extend fanotify to support user watches, from the top of my
head I can't think of a reason it would be very difficult to implement. But it
has been a few years since I actively worked with that code.
Since you are not the only group having issues with fanotify feature set I can
see this mini-project (together with extensions from me previous reply) being
useful. It is also better to evolve it than neglect due a few shortcomings and
then in a few years someone will come up with something completely new and
then we will have yet another notification system.
Tvrtko
next prev parent reply other threads:[~2012-11-12 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 12:52 Better support for (desktop) file search / indexing applications Martin Steigerwald
2012-11-01 12:55 ` [Nepomuk] " Martin Steigerwald
2012-11-01 13:48 ` Tvrtko Ursulin
2012-11-10 16:53 ` Martin Steigerwald
2012-11-12 9:10 ` Tvrtko Ursulin [this message]
[not found] ` <CAKRKD_W8pW+8kUO2HvgCQrtqnHOZzgeGiwAF5ER3Yad4OMcizg@mail.gmail.com>
2013-03-10 4:51 ` Fwd: [Nepomuk] " Simeon Bird
2013-03-10 12:06 ` Lijo Antony
2013-03-12 2:55 ` Andreas Dilger
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=10569573.iu1a6eiZCO@deuteros \
--to=tvrtko.ursulin@onelan.co.uk \
--cc=Martin@lichtvoll.de \
--cc=eparis@parisplace.org \
--cc=eparis@redhat.com \
--cc=jack@suse.cz \
--cc=john@johnmccutchan.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nepomuk@kde.org \
--cc=rlove@rlove.org \
/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).