Re: [chrony-users] Syncing time as with a single request

2020-03-01 Thread Bill Unruh
Not my concerns, but trying to make sure you understand the consequences of your decision. If what is most important is the speed of bootup, together with the clock being roughly on time, then your solution is fine, assuming of course that the system one happens to get from the pool say is itself

Re: [chrony-users] Syncing time as with a single request

2020-03-01 Thread Lonnie Abelbeck
Hi Bill, I appreciate your comments, but chronyd is called immediately after the foreground "chronyd -q ..." so that should mitigate your concerns. Lonnie > On Mar 1, 2020, at 4:27 PM, Bill Unruh wrote: > > There is a battle between acuracy and speed. Your time might be synched, but > your

Re: [chrony-users] Syncing time as with a single request

2020-03-01 Thread Bill Unruh
There is a battle between acuracy and speed. Your time might be synched, but your rate may be way off. Thus your clock might lose 10 sec per minute with your procedure. To get a good estimate for the rate you need to spend more time. (with 4 sec you might reduce the rate to something like

Re: [chrony-users] Syncing time as with a single request

2020-03-01 Thread Lonnie Abelbeck
> On Jan 28, 2020, at 2:35 AM, Miroslav Lichvar wrote: > > On Tue, Jan 28, 2020 at 04:11:49AM +, Gustav Krantz wrote: >> Would it be possible to do the initial sync with a single request per >> server? If so how would this be done and what would the drawback be? > > The current