As per the various other systemd related answers posts:
[Is there a systemd unit file for Splunk?][1]
[Is there a systemd unit file for Splunk?][2]
[Splunk 7.2.2 - systemd - Root privileges required when starting/stopping Splunk?][3]
There has been a lot of confusion since Splunk added the systemd start/stop option in Splunk 7.2.2
However systemd is required for the use of workload management so what are the options?
Duane's blogpost on [Splunk 7.2.2 and systemd][4], does an excellent job of summarising the scenario and solutions.
So the question is, how do we get splunk to stop/start with the systemd unit file, without a modern version of polkit (which does not exist on any Redhat 7.x version), and without using the systemctl stop/start commands? In other words I want splunk stop/start to work as they did before the systemd unit file was in use...
[1]: https://answers.splunk.com/answers/59662/is-there-a-systemd-unit-file-for-splunk.html
[2]: https://answers.splunk.com/answers/594682/is-there-a-systemd-unit-file-for-splunk-1.html
[3]: https://answers.splunk.com/answers/710045/splunk-722-systemd-root-privileges-required-when-s.html
[4]: https://www.duanewaddle.com/splunk-7-2-2-and-systemd/
↧