Re: [Dazuko-help] inotify vs dazuko ?

[Peter Boughton]

Thanks John and Oliver.

Would the file access control mean that I can prevent requests tripping over the same file?
For example, if multiple write requests come in close succession, I'd want to make them wait their turn (presumably by locking the file temporarily) while my script runs, rather than potentially having a file change three times then my script simply looking at the final version three times. (ie: I'd like to enforce ordered queueing of requests).
If Dazuko can do that then it'd definitely push the scales in it's favour.

I've had a quick search about the recursive stuff, and found JNotify (a Java wrapper for inotify) which would handle it for me. Although I also found mention of a limit of 8192 watches for inotify... which is probably fine; I don't think I'll exceed that many directories.

Does Dazuko have any similar limits?


Thanks,

Peter

On Fri, Feb 8, 2008 at 8:01 AM, John Ogness <address@hidden> wrote:

On 2008-02-07, Peter Boughton <address@hidden> wrote:
> Can anyone offer a comparison of the key features of Dazuko over
> inotify? I'll be creating a script that will monitor a directory
> tree and act instantly on every write to any files within that
> directory tree, and I need to decide which one would be the best
> choice to go with.

The main purpose of Dazuko is for "file access control". Although you
can use Dazuko for monitoring, that is probably overkill. For
monitoring, inotify is probably the best choice. The only difficulty
with inotify is that it is not recursive. That is not necessarily a
problem, but it is something to be aware of.

John Ogness

--
Dazuko Maintainer

-- 
 \ \
Peter Boughton
blog.bpsite.net
 / /