commit dbfbadab8e68059431d41aded46325e7b6c2e4b7
author Andrew Geissler <geissonator@yahoo.com> Mon Jun 16 10:39:35 2025 -0500
committer Andrew Geissler <geissonator@yahoo.com> Mon Jun 16 11:13:44 2025 -0500
tree 2af9f3895bf6fc152f2c310abf859b741bc5381e
parent 81cf06523fcfcd0ea8a87040be4fbb7b276894b3

utilize systemd semantic for non-critical ExecStart

The "|| true" was always a bit of a hack to have systemd services ignore
commands which are not critical. It seems recent systemd releases have
broken that workaround.

Utilize the official[1] systemd mechanism to indicate a command within
the service is optional and ok to fail (=-).

The location of the "|| true" within the commands quotation marks
now matters. But lets just get rid of it all together now that we have a
way to just have systemd allow the command to fail and continue.

Tested:
Wrote a little test service:
```
[Unit]
Description=Test Service

[Service]
RemainAfterExit=yes
Type=oneshot
ExecStart=/bin/sh -c "busctl set-property invalid || true"
ExecStart=-/bin/sh -c "busctl set-property invalid" || true
ExecStart=-/bin/sh -c "busctl set-property invalid"
ExecStart=/bin/echo 'we made it past all invalid tests above'

[Install]

```

[1]: https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html#Command%20lines

Change-Id: I5b16a5abf9ba8e0a384bac1130b77bf0252b9dd9
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>