Re: slocate 3.1 not working?

On Aug 3, 2006, at 8:14 AM, Paul Guyot wrote:

>
> Le 3 août 06 à 02:11, Artemio Gonzalez Lopez a écrit :
>
>> After upgrading slocate to the latest version (3.1), it stopped  
>> working altogether, giving invariably the following error message:
>>
>> slocate: fatal error: set_path_head: path_head len <= 0: 0
>>
>> I've googled the error and it seems related to the upgrade 2.7 ->  
>> 3.1, not to DP, but I haven't been able to find a fix or  
>> workaround online.
>> Does anybody have any idea what may be going on?
>
> The first google result shows that running updatedb fixes the  
> problem. I guess that the database format changed.
> This explains why I didn't encounter the problem myself.
>
> Sorry for the inconvenience. It looks like that slocate 3.1 has  
> been entirely rewritten, for the better and the worse (for example,  
> the code now doesn't consider it can be installed at a non ordinary  
> path and I had to bundle the port with patches to fix it up).
>
> Paul
> -- 
> Ministre ultraplénipotentiaire en disponibilité.
> Mobile. Sans baignoire fixe.
> http://www.kallisys.com/
> http://www-poleia.lip6.fr/~guyot/
>

Thanks a lot, Paul, that actually works (and explains why I wasn't  
having a problem in one of my machines). By the way, do you have any  
idea why slocate insists in looking for /var/db/locate.database, e.g.,

slocate: warning: database /var/db/locate.database' is more than 8  
days old
slocate: fatal error: search_db: read: '/var/db/locate.database':  
Database file is empty.

The last message is due to the fact that, apparently, you NEED /var/ 
db/locate.database to exist for slocate to work, but the old locate  
database is not compatible with slocate, so I've just created an  
empty file under that name.

Thanks again,

Artemio