salt/pkg/deb/salt-minion.service

[Unit]
Description=The Salt Minion daemon
After=network.target salt-master.service

[Service]
Type=notify
NotifyAccess=all
LimitNOFILE=8192
ExecStart=/usr/bin/salt-minion

[Install]
WantedBy=multi-user.target
Add initscripts, SystemD service units and environment files for Debian (#32857) 2016-05-19 20:10:02 +00:00			`[Unit]`
			`Description=The Salt Minion daemon`
salt-minion.service: Start after salt-master.service On systems where you have both services, salt-master and salt-minion, enabled, you want that salt-minion.service starts after salt-master.service so that the minion will be able to connect to the master on first attempt. 2017-04-03 09:43:00 +00:00			`After=network.target salt-master.service`
Add initscripts, SystemD service units and environment files for Debian (#32857) 2016-05-19 20:10:02 +00:00
			`[Service]`
Use Type=notify for debian systemd units 2016-10-06 14:14:50 +00:00			`Type=notify`
Use NotifyAccess=all in all unit files When systemd-python is not installed, systemd notification falls back to using the systemd-notify for service notification. This cannot be used however unless the unit has NotifyAccess=all set. The particular use case for this is when Salt is installed using pip. We don't put systemd-python into the requirements.txt because we can't be sure that the minion supports systemd, so pip installs won't necessarily have systemd-python available. 2016-10-19 15:08:10 +00:00			`NotifyAccess=all`
Add initscripts, SystemD service units and environment files for Debian (#32857) 2016-05-19 20:10:02 +00:00			`LimitNOFILE=8192`
			`ExecStart=/usr/bin/salt-minion`

			`[Install]`
			`WantedBy=multi-user.target`