sys-process/cronie: fix cronie pidfile path #24716
Conversation
cronie's build system is using runstatedir to determine
where to place the PID file. On one of my systems,
this path _happens_ to exist because of thermald,
but it won't usually exist.
We should set runstatedir to be "${EPREFIX}"/run
to store the PID file in the place the init script expects
(cronie hardcodes the value of runstatedir into the binary
to find where its pidfile is).
Closes: https://bugs.gentoo.org/835814
Bug: https://bugs.gentoo.org/685306
Signed-off-by: Sam James <sam@gentoo.org>
Pull Request assignmentSubmitter: @thesamesam sys-process/cronie: At least one of the listed packages is maintained entirely by non-GitHub developers! Linked bugsIn order to force reassignment and/or bug reference scan, please append Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide |
gentoo-bot
added
need assignment
Pull request CI reportReport generated at: 2022-03-22 22:51 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
|
Fixed in https://bugs.gentoo.org/685306#c1 and followup to add the ${EPREFIX}. |
cronie's build system is using runstatedir to determine
where to place the PID file. On one of my systems,
this path happens to exist because of thermald,
but it won't usually exist.
We should set runstatedir to be "${EPREFIX}"/run
to store the PID file in the place the init script expects
(cronie hardcodes the value of runstatedir into the binary
to find where its pidfile is).
Closes: https://bugs.gentoo.org/835814
Bug: https://bugs.gentoo.org/685306
Signed-off-by: Sam James sam@gentoo.org