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

[Unit]
Description=Nomad Agent
Requires=network-online.target
After=network-online.target

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

# systemd>=230 prefer StartLimitIntervalSec,StartLimitBurst in Unit,
# however Ubuntu 16.04 only has systemd==229. Use these old style settings
# as they will be supported by newer systemds.
StartLimitBurst=3
StartLimitInterval=10

[Install]
WantedBy=multi-user.target
Terraform configs for e2e tests 2018-12-17 17:40:09 +00:00			`[Unit]`
			`Description=Nomad Agent`
			`Requires=network-online.target`
			`After=network-online.target`

			`[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`
systemd: set a high but non-infinite fd limit 2019-07-02 16:13:24 +00:00			`LimitNOFILE=65536`
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			`LimitNPROC=infinity`
e2e: fix nomad service for systemd<230 2019-05-08 03:26:04 +00:00			`TasksMax=infinity`
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			`Restart=on-failure`
			`RestartSec=2`
e2e: fix nomad service for systemd<230 2019-05-08 03:26:04 +00:00
			`# systemd>=230 prefer StartLimitIntervalSec,StartLimitBurst in Unit,`
			`# however Ubuntu 16.04 only has systemd==229. Use these old style settings`
			`# as they will be supported by newer systemds.`
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			`StartLimitBurst=3`
e2e: fix nomad service for systemd<230 2019-05-08 03:26:04 +00:00			`StartLimitInterval=10`
Terraform configs for e2e tests 2018-12-17 17:40:09 +00:00
			`[Install]`
			`WantedBy=multi-user.target`