NAME
SYNOPSIS
DESCRIPTION
SYSTEMD SERVICE CONFIGURATION
AUTHOR
COPYRIGHT
IDENTITIES OF AUTHORS
yabddnsd.service - yabddnsd systemd integration
yabddnsd@-absolute-path-to-configuration.file.conf.service
Runs
yabddnsd --config-file /absolute/path/to/configuration.file.conf
in a Type=exec systemd instance service unit.
There should be a single --config-file-supplied configuration file for each domain name that should be maintained, and therefore a single systemd service instance per domain name.
In bash, for any
single configuration file, such an instance may be created
like this (as root):
systemctl enable yabddnsd@"$(systemd-escape ’/absolute/path/to/configuration.file.conf’)".service
An example configuration file path might be:
/etc/yabddnsd/instances/your.domain.org.conf
yabddnsd does not require to be run as root; any non-privileged user should suffice, and it is good practice to not run stuff as root unnecessarily.
Systemd makes it
easy to customize services without having to touch their
.service unit files using unit drop-ins. Setting up a unit
drop-in that runs all instances of yabddnsd@.service as a
custom user would consist of creating this text file:
/etc/systemd/system/yabddnsd@.service.d/custom-user.conf
[Service]
User=your-user
eomanis
E-Mail: eomanis@web.de
PGP key fingerprint: F576 37E9 E5C2 8F91 EE64 277B 603E EF8F
E0A9 9498
Copyright 2014-2020 eomanis
yabddnsd is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License version 3 as published by the Free Software Foundation.
yabddnsd is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with yabddnsd. If not, see <http://www.gnu.org/licenses/>.
Should it be required to ascertain the identity of an author, the person who can prove to be in possession of the secret master key of an author’s PGP key is to be considered the respective author.
In case an author’s PGP key has been replaced by another PGP key, the person who can prove the key supersession in the most convincing manner is to be considered the respective author. For example, an author may document the existence of a properly signed key supersession declaration at a certain point in time in a provably tamper-proof way, such as embedding the declaration or a cryptographically secure hash of it in an irreversible blockchain.