The issue has been fixed last year and considering I2Pd can connect through Yggdrasil natively, tunneling Yggdrasil in is a bad idea and could lead into Yggdrasil over Yggdrasil loop situation. |
||
---|---|---|
.. | ||
bluetooth.service.d | ||
chrony.service.d | ||
i2pd.service.d | ||
ipv6 | ||
oidentd.socket.d | ||
sailfish | ||
snapd.refresh.service.d | ||
systemd-resolved.service.d | ||
tor.service.d | ||
ydns6 | ||
yggdrasil.service.d | ||
README.md | ||
etherpad-lite.service | ||
flatpak-update.service | ||
flatpak-update.timer | ||
gitea-restart.service | ||
gitea-restart.timer | ||
limnoria.service | ||
matterbridge-cleanup.service | ||
matterbridge-cleanup.timer | ||
matterbridge-restart.service | ||
matterbridge-restart.timer | ||
matterbridge.service | ||
reflector.service | ||
syncplay-server.service | ||
tor-client.service | ||
tor-onehoponion.service | ||
zeronet.service | ||
znc.service |
README.md
Systemd services. These are sorted by some kind of category into
subdirectories. The sudirectories won’t exist in the real
/etc/systemd/system
unless they end .wants
or
.d
or something similar and I forget to update this README
file if that happens.
- reflector.service is copied from https://wiki.archlinux.org/index.php/Reflector but uses https instead of http, because there is no reason I would want someone to see what I download.
Worth reading
- Waiting for network devices to have IP address (I only use
this for cables)
https://wiki.freedesktop.org/www/Software/systemd/NetworkTarget/#cutthecraphowdoimakenetwork.targetworkforme
- systemctl enable NetworkManager-wait-online.service
- systemctl enable systemd-networkd-wait-online.service