On 2013-03-10, at 6:06, Lijo Antony wrote:
> On 03/10/2013 08:51 AM, Simeon Bird wrote:
>>
>> We (nepomuk) recently looked at using fanotify, and indeed we would
>> need user watches, support for moves and recursive directory watches
>> (we need to support the case where /home is not a separate
On 2013-03-10, at 6:06, Lijo Antony lijo.ker...@gmail.com wrote:
On 03/10/2013 08:51 AM, Simeon Bird wrote:
We (nepomuk) recently looked at using fanotify, and indeed we would
need user watches, support for moves and recursive directory watches
(we need to support the case where /home is not
On 03/10/2013 08:51 AM, Simeon Bird wrote:
Hi,
We (nepomuk) recently looked at using fanotify, and indeed we would
need user watches, support for moves and recursive directory watches
(we need to support the case where /home is not a separate filesystem)
before it would be useful to us. If you
On 03/10/2013 08:51 AM, Simeon Bird wrote:
Hi,
We (nepomuk) recently looked at using fanotify, and indeed we would
need user watches, support for moves and recursive directory watches
(we need to support the case where /home is not a separate filesystem)
before it would be useful to us. If you
Sent again in plain-text - apologies.
-- Forwarded message --
From: Simeon Bird
Date: 9 March 2013 23:49
Subject: Re: [Nepomuk] Better support for (desktop) file search /
indexing applications
To: Tvrtko Ursulin
Cc: Martin Steigerwald , Jan Kara ,
Robert Love , linux-kernel
Sent again in plain-text - apologies.
-- Forwarded message --
From: Simeon Bird bla...@gmail.com
Date: 9 March 2013 23:49
Subject: Re: [Nepomuk] Better support for (desktop) file search /
indexing applications
To: Tvrtko Ursulin tvrtko.ursu...@onelan.co.uk
Cc: Martin Steigerwald
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
>
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
Am Donnerstag, 1. November 2012 schrieb Tvrtko Ursulin:
> On Thursday 01 November 2012 13:52:42 Martin Steigerwald wrote:
> ...
>
> > The following two main issues led to the discussion about adding
> > notification about user inotify watch limit or even having it raised
> > automatically via
Am Donnerstag, 1. November 2012 schrieb Tvrtko Ursulin:
On Thursday 01 November 2012 13:52:42 Martin Steigerwald wrote:
...
The following two main issues led to the discussion about adding
notification about user inotify watch limit or even having it raised
automatically via some policy
On Thursday 01 November 2012 13:52:42 Martin Steigerwald wrote:
...
> The following two main issues led to the discussion about adding
> notification about user inotify watch limit or even having it raised
> automatically via some policy kit mechanism:
>
> 1) Watches are not working recursively.
Am Donnerstag, 1. November 2012 schrieb Martin Steigerwald:
> Furthermore there is an issue with updating the file index on login or
> service start. In order to catch all other file renames a indexer would
> have to run over every directory whose modification time stamp has
> changed again in
Hi!
Some time ago I stumpled over a blog entry that kernel user inotify watch
limit is often not enough for Nepomuk File Watcher to be notified of file
renames, new files and file deletes reliably[1].
There has been a discussion about that on various places[2,3,4] and likely
others.
I am
Hi!
Some time ago I stumpled over a blog entry that kernel user inotify watch
limit is often not enough for Nepomuk File Watcher to be notified of file
renames, new files and file deletes reliably[1].
There has been a discussion about that on various places[2,3,4] and likely
others.
I am
Am Donnerstag, 1. November 2012 schrieb Martin Steigerwald:
Furthermore there is an issue with updating the file index on login or
service start. In order to catch all other file renames a indexer would
have to run over every directory whose modification time stamp has
changed again in order
On Thursday 01 November 2012 13:52:42 Martin Steigerwald wrote:
...
The following two main issues led to the discussion about adding
notification about user inotify watch limit or even having it raised
automatically via some policy kit mechanism:
1) Watches are not working recursively. Thus
16 matches
Mail list logo
