I can see this in the logs spal. 21 10:33:44 systemd[1]: Reloading Prosody XMPP server. spal. 21 10:33:44 systemd[328823]: prosody.service: Failed to execute command: No such file or directory spal. 21 10:33:44 systemd[328823]: prosody.service: Failed at step EXEC spawning /usr/bin/kill: No such file or directory spal. 21 10:33:44 systemd[1]: prosody.service: Control process exited, code=exited, status=203/EXEC spal. 21 10:33:44 systemd[1]: Reload failed for Prosody XMPP server. ExecReload=/usr/bin/kill -HUP $MAINPID # equery b kill * Searching for kill ... sys-process/procps-3.3.16-r2 (/bin/kill) Reproducible: Always
I suppose, that changing to ExecReload=/bin/kill -HUP $MAINPID will fix that?
(In reply to Conrad Kostecki from comment #1) > I suppose, that changing to ExecReload=/bin/kill -HUP $MAINPID will fix that? Yeah, I suppose it should fix it.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a7c01843ba339d47ec244309c2d343ebf6b65b28 commit a7c01843ba339d47ec244309c2d343ebf6b65b28 Author: Conrad Kostecki <conikost@gentoo.org> AuthorDate: 2020-10-23 15:44:11 +0000 Commit: Conrad Kostecki <conikost@gentoo.org> CommitDate: 2020-10-23 15:44:11 +0000 net-im/prosody: fix systemd unit Closes: https://bugs.gentoo.org/750539 Package-Manager: Portage-3.0.8, Repoman-3.0.2 Signed-off-by: Conrad Kostecki <conikost@gentoo.org> net-im/prosody/files/prosody.service-r2 | 13 +++++ net-im/prosody/prosody-0.11.7-r2.ebuild | 96 +++++++++++++++++++++++++++++++++ 2 files changed, 109 insertions(+)