oxidized.git - configuration backup software

Age	Commit message (Collapse)	Author
2018-01-14	fix: Allow Oxidized service to be stopped from services. (#1144)	mattie47
	There is an issue with oxidized and correctly terminatating when a user stops the service. Unfortunately the root cause of this issue has yet to be identified, and it may have to do with specific versions of Ruby gems. As such, the workaround is to use a SIGKILL to kill the oxidized/puma service instead of a SIGINIT. Note: This does not solve the issue with manually starting the oxidized daemon and using Ctrl + c to stop it. The solution here is to then press Ctrl + Z, then manually "kill -9 <PID>".
2017-08-21	Updated oxidized.service file to rely on networking	Neil Lathwood

2017-07-21	Change SIGTERM (default) to SIGINT when stopping oxidized systemd	Antti Tönkyrä
	unit as per Puma documentation
2017-07-06	Add After/Wait to service	Dave
	Found with our setup this helped the service to come up on boot. Optional so commented out. CentOS7
2016-07-09	oxidized should be run as its own username, not as root	Nick Hilliard

2015-06-17	Oxidized as a service for systemd	Florian Doublet
	Oxidized as a service for systemd (Tested on Debian 8)