open-nomad/terraform/shared/config/nomad.service

[Unit]
Description=Nomad
Documentation=https://nomadproject.io/docs/
Wants=network-online.target
After=network-online.target
StartLimitIntervalSec=10
StartLimitBurst=3

# If you are running Consul, please uncomment following Wants/After configs.
# Assuming your Consul service unit name is "consul"
#Wants=consul.service
#After=consul.service

[Service]
ExecReload=/bin/kill -HUP $MAINPID
ExecStart=/usr/local/bin/nomad agent -config /etc/nomad.d
KillMode=process
KillSignal=SIGINT
LimitNOFILE=infinity
LimitNPROC=infinity
Restart=on-failure
RestartSec=2
TasksMax=infinity

[Install]
WantedBy=multi-user.target
update config files to support systemd and Azure; reorganize Packer file hierarchy; update Vagrantfile to use latest tool versions 2017-11-15 19:31:46 +00:00			`[Unit]`
docs: sync systemd unit files; update deploy guide The systemd configs spread across our repo were fairly out of sync. This should get them on our best practices. The deployment guide also had some strange things like running Nomad as a non-root user. It would be fine for servers but completely breaks clients. For simplicity I simply removed the non-root user references. 2019-03-19 22:18:12 +00:00			`Description=Nomad`
			`Documentation=https://nomadproject.io/docs/`
			`Wants=network-online.target`
update config files to support systemd and Azure; reorganize Packer file hierarchy; update Vagrantfile to use latest tool versions 2017-11-15 19:31:46 +00:00			`After=network-online.target`
dist: place systemd unit options correctly This PR places StartLimitIntervalSec and StartLimitBurst in the Unit section of systemd unit files, rather than the Service section. https://www.freedesktop.org/software/systemd/man/systemd.unit.html Fixes #10065 2021-02-23 01:23:00 +00:00			`StartLimitIntervalSec=10`
			`StartLimitBurst=3`
update config files to support systemd and Azure; reorganize Packer file hierarchy; update Vagrantfile to use latest tool versions 2017-11-15 19:31:46 +00:00
docs: sync systemd unit files; update deploy guide The systemd configs spread across our repo were fairly out of sync. This should get them on our best practices. The deployment guide also had some strange things like running Nomad as a non-root user. It would be fine for servers but completely breaks clients. For simplicity I simply removed the non-root user references. 2019-03-19 22:18:12 +00:00			`# If you are running Consul, please uncomment following Wants/After configs.`
			`# Assuming your Consul service unit name is "consul"`
			`#Wants=consul.service`
			`#After=consul.service`

update config files to support systemd and Azure; reorganize Packer file hierarchy; update Vagrantfile to use latest tool versions 2017-11-15 19:31:46 +00:00			`[Service]`
			`ExecReload=/bin/kill -HUP $MAINPID`
docs: sync systemd unit files; update deploy guide The systemd configs spread across our repo were fairly out of sync. This should get them on our best practices. The deployment guide also had some strange things like running Nomad as a non-root user. It would be fine for servers but completely breaks clients. For simplicity I simply removed the non-root user references. 2019-03-19 22:18:12 +00:00			`ExecStart=/usr/local/bin/nomad agent -config /etc/nomad.d`
			`KillMode=process`
			`KillSignal=SIGINT`
			`LimitNOFILE=infinity`
			`LimitNPROC=infinity`
			`Restart=on-failure`
			`RestartSec=2`
			`TasksMax=infinity`
update config files to support systemd and Azure; reorganize Packer file hierarchy; update Vagrantfile to use latest tool versions 2017-11-15 19:31:46 +00:00
			`[Install]`
			`WantedBy=multi-user.target`