Re: stuck in file crawl task loop

On Mon, 2007-01-22 at 17:42 -0500, Joe Shaw wrote:
> Hi,


> Are those the packages that Kevin Kubasik put up?

They are whatever comes in Ubuntu's Feisty.  Not sure if Kevin is the
maintainer there or not.  The changelog.Debian.gz file seems to indicate
that a Brandon Hale <brandon ubuntu com> and Matthias Klose
<doko ubuntu com> are maintainers.  Here are the changelogs:

        beagle (0.2.14-0ubuntu3) feisty; urgency=low
          * Drop build dependency on python2.4-gtk.
          * Make the build independent of the python version.
         -- Matthias Klose <doko ubuntu com>  Fri, 12 Jan 2007 20:45:26 +0100
        beagle (0.2.14-0ubuntu2) feisty; urgency=low
          * Rebuild for python2.5 as the default python version.
         -- Matthias Klose <doko ubuntu com>  Fri, 12 Jan 2007 13:21:05 +0000
        beagle (0.2.14-0ubuntu1) feisty; urgency=low
          * New upstream release
            - Use XDG autostart
            - Notify when index is not completely built in beagle-search
            - Index files inside archives (eg tar.gz)
            - Reduced memory usage
          * Drop autostart .desktop files, now handled upstream
          * Update relibtoolize.dpatch
         -- Brandon Hale <brandon ubuntu com>  Thu, 14 Dec 2006 17:59:59 -0500
Looks pretty stock.

> If so, those are
> actually a CVS snapshot before 0.2.14 was release, and they probably
> have looping bugs in them still.

So 0.2.14 has the looping bugs fixed?  I thought you said that they were
fixed post 0.2.14.  No worries either way.

> The Ubuntu guys have given us pushback on putting new versions in to
> backports; they want us to only backport specific fixes.  So what we're
> going to do is build new packages and host an apt-get repository on
> instead.

I see.  I am using feisty, so backports is not so much an issue for me.

> Yep, it's ~/.beagle/Indexes/FileSystemIndex/FileAttributesStore.db.
> Just open it up with sqlite or sqlite3 and you can poke around in there.

Ahhh.  Just the sort of thing I wanted to poke around for:


Seems to be putting stuff in local filesystem in the db as recently as 6
days ago if I'm understanding that particular record, yes?  Yet:
$ grep home /etc/fstab
/dev/rootvol/home /home         ext3    defaults,user_xattr 0   0
$ grep home /proc/mounts
/dev/rootvol/home /home ext3 rw,data=ordered 0 0
$ attr -l /home/brian/sieve.script
$ attr -l /home/brian/inv1035.pdf
Attribute "Beagle.Uid" has a 22 byte value for /home/brian/inv1035.pdf
Attribute "Beagle.MTime" has a 14 byte value for /home/brian/inv1035.pdf
Attribute "Beagle.AttrTime" has a 14 byte value
for /home/brian/inv1035.pdf
Attribute "Beagle.Fingerprint" has a 25 byte value
for /home/brian/inv1035.pdf

So some files on a local FS are using EAs and some are in the database.
Any ideas why?  I did start using beagle before I was mounting /home
with user_xattr, but I thought some code had gone into beagle to convert
the use of files in the db to using EAs if they later became available.

> I think the developers got a mostly working solution and just left it to
> do other things.

Fair enough I guess.  If it ain't broke...

> Also note that the lack of remote file notification was a design
> decision; I don't think there were ever plans to add it.

I would tend to agree.

> Well, it would if its API didn't suck. :)


> The inotify API is really
> simple and trivial to use.  FAM's is much more complex.

I see.

> I believe so.  That was the plan, and I know that Robert did a lot of
> work to inotify to handle Samba's use cases.  To get a definitive answer
> you'd have to ask the Samba guys though. :/

Of course.

> The work is pretty much stalled.  The two guys who worked on it pretty
> much dropped off after the project was finished, and Fredrik began
> integrating it over the summer, but he too has pretty much vanished.


> If you have all of your files on an NFS server and they don't change
> much, you could use the beagle-build-index tool to create a static index
> of the files on the NFS server, and export that to Beagle for searching
> it on the client.

Right.  Which precludes $HOME though.

Thanx for all the info and feedback Joe.  You are great!


My other computer is your Microsoft Windows server.

Brian J. Murrell

Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]