Maintenance

Once you have set up SOPAC, Locum, and Insurge, you will have to schedule the regular maintenance tasks. There are both daily and hourly tasks. The hourly tasks can be schedules and a higher or lower frequency if you like, but hourly seems a safe bet.

Daily Tasks

The daily Locum maintenance script (maint.php) does several things:

• Retires old/weeded records
• Updates changed records
• Adds newly cataloged records

The maintenance script is in the Locum tools directory (/usr/local/lib/locum/tools/maint.php). You'll want to check its configuration parameters then add it to cron.daily:

chmod +x /usr/local/lib/locum/tools/maint.php
ln -s /usr/local/lib/locum/tools/maint.php /etc/cron.daily/locum


Hourly Tasks

The hourly maintenance script does the following:

• Incorporates hold stats into the index for computing 'Hot Items'.
• Incorporates new social data into the index.
• Rebuilds the index and facet tables

The maintenance script is in the Insurge tools directory (/usr/local/lib/Insurge/tools/update-index.php). You'll want to check its configuration parameters then add it to cron.hourly:

chmod +x /usr/local/lib/insurge/tools/update-index.php
ln -s /usr/local/lib/insurge/tools/update-index.php /etc/cron.hourly/locum


Logging

It's a good idea to let logrotate manage your locum log file. You can do that easily, by adding an entry in /etc/logrotate.d

Autostart Sphinx

Finally, it's a really good idea to have sphinx autostart so that if you reboot the server, it comes up by itself. In Debian, the default runlevel is 2, so you would do something like:

ln -s /etc/init.d/sphinx /etc/rc2.d/S99-Sphinx