slocate's database

merchtemeagle · 10-29-2009, 04:32 PM

It seems the path to slocate's database file is hard-coded.

C code:

Code:

# define DEFAULT_DB "/var/lib/slocate/slocate.db"
# define DEFAULT_DB_DIR "/var/lib/slocate"

Is there any reason why it's not configurable?

tredegar · 10-29-2009, 04:39 PM

Quote:

# define DEFAULT_DB "/var/lib/slocate/slocate.db"
# define DEFAULT_DB_DIR "/var/lib/slocate"
Is there any reason why it's not configurable?

This really isn't of big interest to me, but those lines are "commented out" because the lines begin with the # character.

If you remove the "#", alter the default path, and restart the service, all should be well.

merchtemeagle · 10-29-2009, 04:43 PM

Quote:

Originally Posted by tredegar

This really isn't of big interest to me, but those lines are "commented out" because the lines begin with the # character.

If you remove the "#", alter the default path, and restart the service, all should be well.

Well, not really. It's C code. I've altered my original post to include this information.

tredegar · 10-29-2009, 05:57 PM

Quote:

Well, not really. It's C code. I've altered my original post to include this information.

OK.

It's C code.

If you don't like the suggested default you can change the

Code:

# define DEFAULT*

to whatever you like, then recompile.

Be aware that this may break some apps that assume the default(s) are used.

Quote:

It seems the path to slocate's database file is hard-coded.

This isn't the case, it is soft-coded in the source code.

If you'd like to change it then do so, but you'll have to recompile.

merchtemeagle · 10-29-2009, 06:03 PM

Yes, I can change and recompile it. But my question was actually why it is not configurable. In other words: does someone knows any apps that would break by changing the path.

lwasserm · 10-29-2009, 06:12 PM

Quote:

Originally Posted by merchtemeagle

Yes, I can change and recompile it. But my question was actually why it is not configurable. In other words: does someone knows any apps that would break by changing the path.

Just because those #defines are present in the source code does not mean it is not configurable. They define default values but it is quite possible that somewhere else there is a check for different values read from a configuration file, environement values, or command line, etc.

merchtemeagle · 10-29-2009, 06:34 PM

Quote:

Originally Posted by lwasserm

Just because those #defines are present in the source code does not mean it is not configurable. They define default values but it is quite possible that somewhere else there is a check for different values read from a configuration file, environement values, or command line, etc.

I should just read the man pages before searching the code.

Code:

-o <file>  -  Specifies the database to create.

Thanks!

unSpawn · 10-29-2009, 06:34 PM

Quote:

Originally Posted by merchtemeagle

It seems the path to slocate's database file is hard-coded. (..) Is there any reason why it's not configurable?

Not exactly an answer but I use 'locate' with custom databases (running 'updatedb -U /search/path -o /target/database.db'), this works with both 'slocate' and 'locate' ("mlocate" package) as both allow for the --database= switch. However this requires use of a function, alias or script to switch between databases as the default indeed is hardcoded.