From EPrints Documentation
Revision as of 15:13, 25 February 2010 by Tdb01r (talk | contribs)
Jump to: navigation, search

EPrints 3 Reference: Directory Structure - Metadata Fields - Repository Configuration - XML Config Files - XML Export Format - EPrints data structure - Core API - Data Objects


Latest Source Code (3.4, 3.3) | Revision Log | Before editing this page please read Pod2Wiki


indexer - Indexing daemon for EPrints

User Comments


indexer start [options]

indexer stop

indexer status

indexer --help

User Comments


This daemon runs in the background and creates index files for all eprints repositories.

Messages and errors are logged to /opt/eprints3/var/indexer.log unless you change the log options. If it appears to be having problems try raising the log level and examining the log.

Once every 24 hours, the indexer rolls the logs (up to logfile.5) and then starts again. See --rollcount for ways to customise this.

User Comments


User Comments


Print a brief help message and exit.

User Comments


Print the full manual page and then exit.

User Comments


Be vewwy vewwy quiet. This option will supress all output unless an error occurs.

User Comments


Start up, even if the PID file exists (implying another copy is running). This is useful for starting after a crash, but be carefully not to run to copies at once as BAD THINGS will happen.

User Comments


Explain in detail what is going on. May be repeated for greater effect.

User Comments


Clear stale event queue items (items that are "inprogress") before commencing.

User Comments

--logfile filename

Log to filename rather than default indexer log.

User Comments

--loglevel level

Set the level of detail to log. Level may be 0-6.

User Comments

--rollcount number

Set the number of once-through logs that should be kept. If set to zero then indexer will never roll the logs but rather just keep writing to the main log.

User Comments


Do not become a daemon, remain attached to the current terminal.

Log goes to STDERR instead of the log file.

Does not create a .pid file.

User Comments


Only clear the current queue of things needing indexing then exit.

User Comments


Output version information and exit.

User Comments

Making into a service

This has only been tested under redhat linux. It make work on other OS's, but not promise.

To make the indexer into a service which starts and stops on reboots etc. like httpd and mysqld do the following (as root):

ln -s /opt/eprints3/bin/epindexer /etc/init.d/epindexer 
chkconfig --add epindexer
chkconfig epindexer on

The epindexer script runs as root, changes user to "eprints" (or whatever uid your eprints install runs as) and then calls indexer.


User Comments