At present the indexer is a hotchpotch of various things. It would be better if it was managed by systemd, this would simplify matters significantly. Systemd is supported on RHEL based and Debian based Linux, as well as the majority other Linux varieties.
Simplifications:
- No need to manage logfiles, they would all go in the journal. So this would save having the settings for rollcount, respawn and needing to care what the log file is called just write everything to STDOUT and let systemd deal with it.
- Failure would be automatically detected and the indexer restarted so .pid and .tick files would no longer be needed. These can cause issues if stale versions are sitting about.
- EPrints::Index::Daemon already supports SIGINT, SIGTERM, SIGALRM, which can be used by systemd's KillSignal and the like to gracefully and possibly not so gracefully exit.
Improvements:
i. With systemctl --enable ensures the indexer is always restarted after a reboot and with dependencies makes sure it is start at a suitable time.
ii. Better management of logfiles with journalctl. In particular issue with regular restarts of the indexer meaning logfiles never get rotated.
iv. Removes quite a bit of unnecessary configuration and code and various individual files to manage the indexer.
Potential problems:
A. Not straightforward to get indexer to start through systemd from the web interface.
B. Possible other problems yet to be determined.
At present the indexer is a hotchpotch of various things. It would be better if it was managed by systemd, this would simplify matters significantly. Systemd is supported on RHEL based and Debian based Linux, as well as the majority other Linux varieties.
Simplifications:
Improvements:
i. With systemctl --enable ensures the indexer is always restarted after a reboot and with dependencies makes sure it is start at a suitable time.
ii. Better management of logfiles with journalctl. In particular issue with regular restarts of the indexer meaning logfiles never get rotated.
iv. Removes quite a bit of unnecessary configuration and code and various individual files to manage the indexer.
Potential problems:
A. Not straightforward to get indexer to start through systemd from the web interface.
B. Possible other problems yet to be determined.