Bug in beacon as discussed on IRC. Here's how to reproduce: Server side:
[EMAIL PROTECTED] ~]$ rm -rf ~/.beacon ~/tmpfoo [EMAIL PROTECTED] ~]$ mkdir ~/tmpfoo [EMAIL PROTECTED] ~]$ BEACON_DATABASE=~/.beacon BEACON_MONITOR=~/tmpfoo beacon --start --verbose crawler,db INFO crawl(90): crawl <beacon.Directory /home/tack/tmpfoo/> INFO crawl(96): start crawler 1 INFO crawl(218): add inotify for /home/tack/tmpfoo/ INFO crawl(160): crawler 1 finished Client side: [EMAIL PROTECTED] ~]$ beacon --monitor --search keywords=foo Query took 0.000891923904419 seconds Now in another window: [EMAIL PROTECTED] ~]$ touch ~/tmpfoo/foo.txt Server updates with: INFO crawl(160): crawler 1 finished Client updates with: Beacon query update <beacon.File /home/tack/tmpfoo/foo.txt> <beacon.File /home/tack/tmpfoo/foo.txt> So, the new file is listed twice. Even when I exit the client and run the query again: [EMAIL PROTECTED] ~]$ beacon --search keywords=foo <beacon.File /home/tack/tmpfoo/foo.txt> <beacon.File /home/tack/tmpfoo/foo.txt> Query took 0.00483393669128 seconds But note, if I list the dir explicitly, it's just once: [EMAIL PROTECTED] ~]$ beacon --search dirname=~/tmpfoo <beacon.File /home/tack/tmpfoo/foo.txt> Query took 0.00724792480469 seconds Jason. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
