diff options
| author | St33v <github@f3rr3t.com> | 2026-06-09 17:11:47 +1000 |
|---|---|---|
| committer | St33v <github@f3rr3t.com> | 2026-06-09 17:11:47 +1000 |
| commit | 258a3bec5192106e1e24e65763649b7f6943af9e (patch) | |
| tree | 9add3f9e8579e649c8acd7be5bdf8f329e2644ce /systemd/radar.service | |
| parent | 71a0aecb76984347292199db328142bef4807088 (diff) | |
Add Brisbane radar (IDR663) alongside Sydney
radar.service / radar-retry.service now invoke radarFetch.sh once
per product code, prefixed with `-` so one radar's outage does not
skip the other.
Landing page at / links to /sydney and /brisbane; each per-radar
page is the familiar black-page full-image idiom with a small
corner link to its sibling.
setup.sh provisions the subdirs and installs all three pages.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Diffstat (limited to 'systemd/radar.service')
| -rw-r--r-- | systemd/radar.service | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/systemd/radar.service b/systemd/radar.service index 8e9dd40..6995637 100644 --- a/systemd/radar.service +++ b/systemd/radar.service @@ -6,7 +6,9 @@ OnFailure=radar-retry.timer Type=oneshot User=st33v WorkingDirectory=/var/lib/radar -ExecStart=/opt/radar/radarFetch.sh +# `-` prefix: one radar's failure does not skip the next +ExecStart=-/opt/radar/radarFetch.sh IDR713 +ExecStart=-/opt/radar/radarFetch.sh IDR663 ExecStopPost=/bin/sh -c 'STATUS=SUCCESS; [ "$$EXIT_STATUS" != "0" ] && STATUS=FAILURE; logger -t radar -p user.err "radar $$STATUS exit=$$EXIT_STATUS"' SyslogIdentifier=radar StandardOutput=journal |