Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 665212 - net-misc/chrony-3.4_pre1 fails to stop due to incorrect path to PID file in /etc/init.d/chronyd
Summary: net-misc/chrony-3.4_pre1 fails to stop due to incorrect path to PID file in /...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Jeroen Roovers (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-04 08:28 UTC by MickKi
Modified: 2018-09-04 17:59 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description MickKi 2018-09-04 08:28:48 UTC 
net-misc/chrony-3.4_pre1 fails to stop due to incorrect path to its PID file in /etc/init.d/chronyd.

Current path is PIDFILE=/run/chronyd.pid, when it should be PIDFILE=/run/chrony/chronyd.pid (lines 46 & 61).

Reproducible: Always
Comment 1 Larry the Git Cow gentoo-dev 2018-09-04 09:32:25 UTC 
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6e9478074f14ff36bd4beb516f8ba144bef45201

commit 6e9478074f14ff36bd4beb516f8ba144bef45201
Author:     Jeroen Roovers <jer@gentoo.org>
AuthorDate: 2018-09-04 09:31:04 +0000
Commit:     Jeroen Roovers <jer@gentoo.org>
CommitDate: 2018-09-04 09:32:19 +0000

    net-misc/chrony: Set default PID file and check for it
    
    Fixes: https://bugs.gentoo.org/665212
    Package-Manager: Portage-2.3.49, Repoman-2.3.10

 ...y-3.4_pre1.ebuild => chrony-3.4_pre1-r1.ebuild} | 12 ++--
 net-misc/chrony/files/chronyd.init-r2              | 70 ++++++++++++++++++++++
 2 files changed, 76 insertions(+), 6 deletions(-)
Comment 2 Cyril 2018-09-04 13:18:23 UTC 
systemd service must be patched with
PIDFile=/run/chrony/chronyd.pid
Comment 3 Mike Gilbert gentoo-dev 2018-09-04 17:59:55 UTC 
(In reply to Cyril from comment #2)

See bug 665232.