1 |
On Monday, 3 September 2018 22:47:50 BST Holger Hoffstätte wrote: |
2 |
> On Mon, 03 Sep 2018 22:23:18 +0100, Mick wrote: |
3 |
|
4 |
> > This is repeatable if I try to stop it manually. Version 3.3 didn't have |
5 |
> > this problem. |
6 |
> |
7 |
> Ah yes, that's from upgrading. Apologies for the misleading advice, |
8 |
> I fixed that locally and forgot. :} |
9 |
> |
10 |
> 1) Edit /etc/init.d/chronyd and change occurrences of /run/chronyd.pid to |
11 |
> /run/chrony/chronyd.pid (i.e. add the subdirectory). |
12 |
> |
13 |
> 2) file a bug so that the init file gets fixed in portage as well. :) |
14 |
> |
15 |
> cheers |
16 |
> Holger |
17 |
|
18 |
Done! |
19 |
|
20 |
https://bugs.gentoo.org/665210 |
21 |
https://bugs.gentoo.org/665212 |
22 |
|
23 |
Interestingly, two Intel systems running 3.3 are booting normally. It was |
24 |
only an AMD system here which was hanging at boot. |
25 |
|
26 |
-- |
27 |
Regards, |
28 |
Mick |