The daemon for ekeyd forks and creates a PID file with no option to run in the foreground, however it's current service file does not indicate this behavior. Because of this, it can fail to start with systemd. This is easily fixed with the following patch: ```diff --- app-crypt/ekeyd/files/ekeyd.service 2015-08-08 20:38:18.000000000 -0400 +++ app-crypt/ekeyd/files/ekeyd.service.new 2018-03-03 13:47:30.532002927 -0500 @@ -3,6 +3,8 @@ [Service] ExecStart=/usr/libexec/ekeyd +Type=forking +PIDFile=/var/run/ekeyd.pid [Install] WantedBy=multi-user.target` ```
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c766d91b70819666658681fb5fc7c113ffdd5bb7 commit c766d91b70819666658681fb5fc7c113ffdd5bb7 Author: Kristian Fiskerstrand <k_f@gentoo.org> AuthorDate: 2018-03-21 19:55:59 +0000 Commit: Kristian Fiskerstrand <k_f@gentoo.org> CommitDate: 2018-03-21 19:55:59 +0000 app-crypt/ekeyd: Fixes for systemd service file Closes: https://bugs.gentoo.org/649478 Package-Manager: Portage-2.3.24, Repoman-2.3.6 app-crypt/ekeyd/files/ekeyd.service | 2 ++ 1 file changed, 2 insertions(+)
