Hi,

Today I realised systemd allows you to define a set of conditions as "triggering conditions"; the unit will execute if *all* of the normal conditions are met, and *any* of the triggering conditions is met too.

This service override fixes the problem for me:

$ cat /etc/systemd/system/borgmatic.service.d/override.conf
[Unit]
# Allow using split configuration files in /etc/borgmatic.d/
ConditionFileNotEmpty=
ConditionFileNotEmpty=|/etc/borgmatic/config.yaml
ConditionPathExistsGlob=|/etc/borgmatic.d/*.yaml
ConditionPathExistsGlob=|/etc/borgmatic.d/*.yml

--
Martina Ferrari

Reply via email to