08759225a6
Use `Type=Forking`. By default, `Type=Simple` is used and it expects that the daemon stays forking in the foreground. However, lbrycrdd does the opposite and forks/goes to background. This confuses systemd a little bit: ``` Dec 09 10:30:28 lbry.devass.club systemd[1]: lbrycrdd.service: Unit process 12237 (lbrycrdd) remains running after unit stopped. ``` So basically it thinks that the unit stops working instantly. When the correct type is used, systemd should be able to handle this situations, along with restarts, properly. See also: [AUR systemd service](https://aur.archlinux.org/cgit/aur.git/tree/lbrycrd.service?h=lbrycrd) |
||
---|---|---|
.. | ||
android-build.md | ||
api-wrappers.md | ||
claim-signing.md | ||
claimtrie.md | ||
consensus.md | ||
daemon-settings.md | ||
dht-bootstrap.md | ||
download-overview-new.md | ||
download-overview.md | ||
encrypt-lbrycrd.md | ||
repository-standards.md | ||
setup-videos.md | ||
wallet-server.md | ||
web-instance.md |