xmr-remote-nodes/deployment/init/xmr-nodes-prober.service

[Unit]
Description=xmr-node prober service
After=network.target

[Service]
Type=oneshot
User=your_user
WorkingDirectory=/path/to/project/dir
ExecStart=/path/to/project/dir/bin/xmr-nodes-client probe
TimeoutSec=90

# vim: filetype=systemd
Adding systemd service and timer for prober 2024-05-06 14:45:33 +00:00			`[Unit]`
			`Description=xmr-node prober service`
			`After=network.target`

			`[Service]`
			`Type=oneshot`
Use "your_user" for systemd example This will make the systemd service failed if "user" blindly copy the systemd example file. 2024-05-06 15:14:33 +00:00			`User=your_user`
Adding systemd service and timer for prober 2024-05-06 14:45:33 +00:00			`WorkingDirectory=/path/to/project/dir`
Update deployment example (CPU arch aware) #3 The ansible playbook is now using ansible_facts to determinate target server or prober CPU architecture. The final "production" binary name and changed to just simply "xmr-nodes-{client,server}". 2024-05-18 11:09:36 +00:00			`ExecStart=/path/to/project/dir/bin/xmr-nodes-client probe`
Adding systemd service and timer for prober 2024-05-06 14:45:33 +00:00			`TimeoutSec=90`

			`# vim: filetype=systemd`