You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The path for the systemd unit environment file is currently hard-coded to /etc/sysconfig/activemq .
This will work on most installations, but /etc/sysconfig/ is a path specific to RHEL/CentOS/etc.
On Debian, for example, init script environment files are stored in /etc/default/ .
Even on RH, /etc/default/ has started to see some use lately.
I recommend making the path customisable via an Ansible variable or moving environment variables directly into the service file.
Quote the systemd overlord himself:
Use of EnvironmentFile= is pretty much always a bad idea, and we probably should never have added that, since it invites packagers to reintroduce the /etc/default/ and /etc/sysconfig/ madness we try to remove.
-- systemd/systemd#618 (comment)
The text was updated successfully, but these errors were encountered:
The path for the systemd unit environment file is currently hard-coded to /etc/sysconfig/activemq .
This will work on most installations, but /etc/sysconfig/ is a path specific to RHEL/CentOS/etc.
On Debian, for example, init script environment files are stored in /etc/default/ .
Even on RH, /etc/default/ has started to see some use lately.
I recommend making the path customisable via an Ansible variable or moving environment variables directly into the service file.
Quote the systemd overlord himself:
The text was updated successfully, but these errors were encountered: