On Thu, Mar 13, 2008 at 6:53 PM, Bruno Moreira Guedes
<[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm currently interested in know what's the Listener status. Is there
> any "TODO" list for it?
> Is there something wrong with recursion on that?? Where can I find
> more info about it and how to make detailed tests??
Hi there,
Listener works. Its current limitation, as you noticed, is that it
doesn't watch for events recursivelly. For example, you can configure
it to listen for removals at /Programs so that it will catch 'rm
/Programs/Foo'. However, if you remove '/Programs/Foo/1.0' Listener
won't trigger that rule, as it's looking for events at its parent dir
only.
I once started to implement that, and then I didn't have time to
finish it, so I did a partial rollback to remove the intrusive code.
You'll find an '#if 0' in rules.c that identifies the 'RECURSIVE'
keyword in listener.conf and some unused code in listener.c (see
walk_tree() and use of the 'recursive' member of struct
directory_info).
Once that's implemented fine it will be trivial to implement something
like 'RECURSIVE = {n}', where {n} will define how many levels to look
down the path. But that's a bonus :)
Cheers,
--
Lucas
powered by /dev/dsp
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
