confluent/confluent_server/systemd/confluent.service

# IBM(c) 2015 Apache 2.0
[Unit]
Description=Confluent hardware manager 

[Service]
Type=forking
#PIDFile=/var/run/confluent/pid
ExecStart=/opt/confluent/bin/confluent
ExecStop=/opt/confluent/bin/confetty shutdown /
Restart=on-failure

[Install]
WantedBy=multi-user.target
Add simple systemd service file for confluent server. The sysvinit scripts were not returning the same informational messages when run under systemctl as they were when run under service. 2015-07-15 13:33:47 -04:00			`# IBM(c) 2015 Apache 2.0`
			`[Unit]`
			`Description=Confluent hardware manager`

			`[Service]`
			`Type=forking`
Change systemd unit to not have PIDFile systemctl restart always prints a worrying message with pidfile. 2018-09-07 11:27:43 -04:00			`#PIDFile=/var/run/confluent/pid`
Add simple systemd service file for confluent server. The sysvinit scripts were not returning the same informational messages when run under systemctl as they were when run under service. 2015-07-15 13:33:47 -04:00			`ExecStart=/opt/confluent/bin/confluent`
Prevent hang on systemctl stop confluent systemd's default stop seems to be incapable of understanding how to shut down our service. Provide an explicit ExecStop to have systemd act more sanely. 2015-11-02 14:11:07 -05:00			`ExecStop=/opt/confluent/bin/confetty shutdown /`
Correct some minor potential issues and add restart on failure 2017-08-25 16:41:22 -04:00			`Restart=on-failure`
Add simple systemd service file for confluent server. The sysvinit scripts were not returning the same informational messages when run under systemctl as they were when run under service. 2015-07-15 13:33:47 -04:00
			`[Install]`
			`WantedBy=multi-user.target`