1 |
On Fri, Nov 22, 2013 at 9:15 PM, Paul B. Henson <henson@×××.org> wrote: |
2 |
> I was unable to come to an agreement with the current maintainer of the |
3 |
> ebuild on this design, and would like some general feedback from the larger |
4 |
> community of developers on this topic. |
5 |
|
6 |
Thank you for your explanation of the issues here, I found it quite interesting. |
7 |
|
8 |
I think I was the original user who complained about the boot delays. |
9 |
I was surprised a few times by openntpd behavior. |
10 |
|
11 |
- Without -s, it can take a *very* long time to get close to an |
12 |
acceptable time error, whereas my initial expectation was that |
13 |
"starting my ntpd should fix the time error fairly quickly". But for |
14 |
me this, this is partly about starting ntpd while the machine is |
15 |
online, not just at boot. |
16 |
|
17 |
- Second, with -s, the boot delays can be quite long. I'm pretty sure |
18 |
I've seen delays that are quite a bit longer than 15s, probably in the |
19 |
case where there's no network or maybe where DNS doesn't resolve well; |
20 |
in any case, when you're trying to debug issues in a data center |
21 |
environment, waiting for a bunch of machines to come up is not much |
22 |
fun. (Or when you've had a machine go down and you're waiting to see |
23 |
if it comes up again.) |
24 |
|
25 |
Now, for my use case, it is not all that important that the time error |
26 |
is minimized before resuming the boot process, but I really wanted to |
27 |
minimize boot delays. |
28 |
|
29 |
Also, I'm really not sure how the change to logging to stderr/file and |
30 |
running in debug mode helps with the boot delays. |
31 |
|
32 |
Cheers, |
33 |
|
34 |
Dirkjan |