Start WildFly as a systemd Service on Linux: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
We create a simple <tt>systemd</tt> <tt>Type=oneshot</tt> unit file that delegates the work of starting and stopping the instance to the System V wrappers shipped with EAP installation bundle. | We create a simple <tt>systemd</tt> <tt>Type=oneshot</tt> unit file that delegates the work of starting and stopping the instance to the System V wrappers shipped with EAP installation bundle. | ||
=<tt>systemd</tt> File Locations= | |||
We adapted the installation procedure after an ActiveMQ installation procedure that recommended placing files in <tt>/usr/lib/systemd/scripts</tt> and <tt>/usr/lib/systemd/system</tt>. However, a better location seems to be <tt>/etc/systemd/...</tt> More research is needed, the results will go here [[systemd Concepts#Unit_File_Location]]. | |||
Revision as of 07:39, 16 February 2016
Internal
Overview
We create a simple systemd Type=oneshot unit file that delegates the work of starting and stopping the instance to the System V wrappers shipped with EAP installation bundle.
systemd File Locations
We adapted the installation procedure after an ActiveMQ installation procedure that recommended placing files in /usr/lib/systemd/scripts and /usr/lib/systemd/system. However, a better location seems to be /etc/systemd/... More research is needed, the results will go here systemd Concepts#Unit_File_Location.