[ome-devel] Trouble with OMERO.Dropbox

[Colin Blackburn]

Hi Niko,

> Hum, I thought more of something at OS level for configuring inotify itself.

Yes, but at the present time any configuration there is, is only available to us through the Python bindings. I will, though, look into this further.

> Regarding the Python bindings, are you aware of the following?
>
> * http://www.serpentine.com/blog/2008/01/04/why-you-should-not-use-pyinotify/  (particularly interesting regarding performance is also the last comment)
> * https://bitbucket.org/bos/python-inotify (original repo)
> * https://bitbucket.org/JanKanis/python-inotify/ (more recent fork)
>
> There are a couple of additional forks of the latter, whereof the only one containing significant changes is the "poupas" one.

Yes, at the time we adopted pyinotify it was done for pragmatic reasons. We’ll certainly look at whether we can somehow allow for other bindings to the notification system to be used in the future.

More generally, I’m investigating the problem you are seeing on one of our systems here. I’ll get back to you about that as soon as I can.

Cheers,

Colin


> On 5 Feb 2015, at 16:21, Niko Ehrenfeuchter <nikolaus.ehrenfeuchter at unibas.ch> wrote:
>
> Hi Colin,
>
> On 05.02.2015 12:14, Colin Blackburn wrote:
>> Hi Niko,
>>
>>> Sure, we'd love to try this. In the current situation, DropBox is
>>> entirely unusable for our scenario :-(
>>
>> I’ll push a commit as soon as I can and let you know. I assume your
>> server is built using our 5.0.x line?
>
> that's correct, currently still 5.0.5 but the upgrade to 5.0.7 is WIP as we're expecting some bugs to be fixed there.
>
>>> Is there no way to configure the behaviour of the inotify subsystem
>>> to trigger (or pass on) modification with a lower frequency, e.g.
>>> only once per second instead of once per millisecond?
>>
>> No, not as far as I can see from the python library we us, pyinotify.
>> The latest version of this library, later than the one one we bundle,
>> allows events to be ignored but they are still propagated from
>> inotify to pyinotify but just passed no further.
>
> Hum, I thought more of something at OS level for configuring inotify itself. Regarding the Python bindings, are you aware of the following?
>
> * http://www.serpentine.com/blog/2008/01/04/why-you-should-not-use-pyinotify/  (particularly interesting regarding performance is also the last comment)
> * https://bitbucket.org/bos/python-inotify (original repo)
> * https://bitbucket.org/JanKanis/python-inotify/ (more recent fork)
>
> There are a couple of additional forks of the latter, whereof the only one containing significant changes is the "poupas" one.
>
> Cheers
> ~Niko
> _______________________________________________
> ome-devel mailing list
> ome-devel at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel


The University of Dundee is a registered Scottish Charity, No: SC015096