Re: Crawl System and Beagle 0.3.3

> I suspect this is due to wrong path supplied when building the rpm. Check one
> thing, move one of the index to /usr/var/cache ... e.g.
> /usr/var/cache/beagle/indexes/documentation

It does not work, sorry :

[root grogro ~]# ll /usr/var/cache/beagle/indexes/
total 4
drwxr-xr-x 7 beagleindex beagleindex 4096 2008-06-23 18:00 music/

[chicha grogro ~]$ beagled --fg --debug --backend music
Always: Starting Beagle Daemon (version 0.3.3)
Always: Running on Mono 1.2.6
Always: Command Line: /usr/lib/beagle/BeagleDaemon.exe --fg --debug
--backend music
Debug: Established a connection to the X server
Debug: Reniced process to 7
Debug: Starting messaging server
Debug: Done reading conf from /etc/beagle/config-files/Networking.xml
Debug: Done reading conf from /home/chicha/.beagle/config/Daemon.xml
Debug: Done reading conf from /etc/beagle/config-files/Daemon.xml
Warn: Inotify watches may be too low (8192) for some users!  Increase
it to at least 65535 by setting fs.inotify.max_user_watches in
Debug: Starting QueryDriver
Debug: Found 0 backends in /usr/lib/beagle/Backends/ThunderbirdBackends.dll
Debug: Found 0 backends in /usr/lib/beagle/BeagleDaemonLib.dll
Debug: Reading mapping from filters
Debug: Found 0 user-configured static indexes..
Debug: Waiting 60 seconds before starting queryables
Debug: Starting Scheduler thread
Debug: Starting Inotify threads
Debug: Daemon initialization finished after ,21s
Debug: Memory usage: VmSize=38,4 MB, VmRSS=14,4 MB,
GC.GetTotalMemory=909312 (10 colls)
Debug: Starting queryables

This is really strange isn't it ?
I have add a look at the rpm spec file which you can find here :,
for instance.
Indeed they do not specify the --localstatedir=/var variable. But
copying some indexes to the default prefix does not seem to fixe the

I am considering opening a bug to Mandriva an see what is the packager
opinion about this ...

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