similar to: flintlock issues

Hi everyone (oh yeah, and I am new to the list but have a little Samba experience). I have a Samba 3.0.1 install on a Fedora Core 1 (.2138 kernel non-smp - not that it should matter for this). I have created a group called "osla" for the users in my domain and I have Samba working properly as a PDC, or at least properly in so far as I can join clients to the server, run scripts and

Hi Guys, I'm working on some integration project with Ruby, Rack, Apache, Phusion Passenger and Xapian. I've been having intermittent issues with the flintlock code - it seems that the function FlintLock::lock is never returning and this is locking up the Ruby process. My guess is that Xapian is locking up in a system call and Ruby can't schedule its green threads. I've done

Hi, I'm experiencing weird behaviour in Xapian/Omega. Here's my situation: * I'm indexing data through scriptindex, the output is as follows: ***************** Replace: 6706476 Replace: 6706477 Replace: 6706478 ***************** Since there is no output after entering several enters, I assume scriptindex is indexing data. * The search I perform on omega is as follows:

Hi all, I´ve been developing a search application using Xapian and Omega. When our visitors search on specific keywords it´s noticable that Omega is case sensitive. It will find results on keyword `Asus´ and it will NOT find results on keyword ´asus´. I´ve been looking through the documentation to find a CGI param to turn this

hallo, I'm indexing a filesystem using omindex, and users can query the database via omega: everything works fine now I'd like to add an option like "search files by name" and I'm wondering how to do this can omega search files by name directly? how should I build the query? could I use scriptindex to index, eg., the locate database? how? should I index file names

Hi All, I've installed Xapian and the php module. I've set up a script for use with scriptindex and dbi2omega for getting data from the db into the index easily, the script file is as follows: =============================== id : field=id title : index title: field=title description : index description : truncate=50 field=content ============================= However, when querying

James, thanks for the explanations. I misread the notes. As an exercise, I'm trying to convert an existing project that currently uses Scriptindex and Omega to direct Xapian API calls. I did a (I think) complete dump of a document with delve -r 565 -d database and I see things like subject='A typical subject' with a corresponding set of terms like Sa Stypical Ssubject Which

OK, I'm indexing my data with the scriptindex. I want to be able to restrict the search by the category field. Do I need to do anything to the data itself? Like, literally prefix it with the characters "XC"? Below is my indexor for scriptindex and the my php code... document_id : field=ref unique=Q boolean=Q search_id : field=document_id index=S document_title : field=title

On Sun, 21 Feb 2016 22:33:22 +0000, Olly Betts <olly at survex.com> wrote: > On Sun, Feb 21, 2016 at 02:15:25PM +0100, Eric J wrote: > > I discovered, while trying to set up Tcl bindings for Notmuch > > (https://notmuchmail.org/), which uses Xapian, that flintlock was not > > being locked (I had lost updates). > > It seems to work for me, testing with this: >

Hi, I was researching indexing of text in omindex and scriptindex. While indexing text with omindex.cc possition of terms is saved with gap. This is not happening with scriptindex.cc While this is happening ? Another question is why in omindex.cc the term possition starts with 0 while in scriptindex it starts from 1 ? Code snippet from omindex.cc // Add postings for terms to the document

I discovered, while trying to set up Tcl bindings for Notmuch (https://notmuchmail.org/), which uses Xapian, that flintlock was not being locked (I had lost updates). I then found that opening a Xapian database for writing directly via the Xapian Tcl bindings also silently fails to lock flintlock. I have taken a copy of flint_lock.cc to play with, and I find that it locks the file when called

I am trying to use Xapian 1.0.2 with the Python SWIG bindings withn an environment consisting of Apache httpd with mod_python. (not as a CGI) Also this is Linux. Whenever the python code attempts to open a database the entire httpd process will hang indefinitely. The python bindings work outside of the apache/mod_python environment. >From the best I can tell the hang occurs in

I'm using omega for a sitesearch and currently having a problem trying to filter $field(sample). At the moment it returns text from the page header and navigation within the sample, ideally I'd like it to return only the page content. I've been trying various omegascript commands to trim the output or seperate the fields and also looking at scriptindex to control how the xhtml is

Hi, Currently Omega/scriptindex supports filtering by date. For example, all dates between START and END. Would it be possible to extend this behaviour to include the time? We have documents which expire. In order to filter out 'old' articles, we would like to check if the document date is between START=NOW and END=MAXINT. Best regards, Eric

Hi, I configured XAPIAN 1.0.1 and OMEGA 1.0.1. on my development machine (first removed the old ones). I recreated my databases (both quartz and flint) and tried to run original queries against the databases created by the new versions. I'm getting empty result sets from OMEGA. If I use the delve tool I actually see that the records are created fine. No log files are written as far as I

Hello :-) There was probably no good reason to do this build but the Debian 6.0 Squeeze repo version was 1.2.3, we needed 1.2.4 and I didn't think of using the package from unstable. Arch: x86_64 Platform: Linux 2.6 Debian 6.0 (Squeeze) Compiler: gcc version 4.4.5 (Debian 4.4.5-8) Version: 1.2.4 Status: no known problems Source: http://oligarchy.co.uk/xapian/1.2.4/xapian-core-1.2.4.tar.gz

I wrote: > I think it's a bug. Or at least QueryParser uses a rather delicate rule > for when to add a ":" between the prefix and the term, which scriptindex > doesn't implement. The rule is undocumented (except in the code) so > it's arguable who is correct. I've been looking at this some more. We need some way to distinguish the term prefix from the term

Hi, I am trying to use datas written in the stdin to run scriptindex, (I am working with Windows and not Unix). And Scriptindex does not work, the database is created but the datas are not indexed. Thanks by advance Stephane

Hi I am a beginner with Xapian. I am trying to use scriptindex but I get some problems : 1) If my script file is empty I have an indexation by default, and I get two output fields when I am using quest.exe (These fields are caption and sample) 2) I then tryed to not use an empty script file defining this time my own fields, but if I use quest to perform researches these fileds does not appear in

Hi, I've tested omega (cgi) on several sql databases on my local machine in which runs Ubuntu, using the version 0.9.4 (installed using apt), and I was really satisfied for the results I obtained. I customized a bit the "query" template. But once I installed omega on the server (using apt for Debian, and omega version 0.9.5), I discovered that the relevances didn't work, as