[chrony-dev] [GIT] chrony/chrony.git branch, master, updated. 1.24-93-g833022b

2010-12-09 Thread git
This is an automated email from git. It was enerated because a ref change was pushed to the repository "chrony/chrony.git". The branch, master has been updated via 833022b7459017f5f21539f59774dddb61dac6df (commit) via d1b820e7e323771d79a164ffa02cd9b835213bab (commit) via 43

Re: [chrony-dev] [GIT] chrony/chrony.git branch, master, updated. 1.24-93-g833022b

2010-12-09 Thread Bill Unruh
On Thu, 9 Dec 2010, g...@tuxfamily.net wrote: commit d1b820e7e323771d79a164ffa02cd9b835213bab Author: Miroslav Lichvar Date: Thu Dec 9 15:14:05 2010 +0100 Shorten initial delay and sampling separation to 0.2 seconds Is this going to run into problems with ntpd's Kill signal, thinking t

Re: [chrony-dev] [GIT] chrony/chrony.git branch, master, updated. 1.24-93-g833022b

2010-12-09 Thread Miroslav Lichvar
On Thu, Dec 09, 2010 at 08:27:44AM -0800, Bill Unruh wrote: > On Thu, 9 Dec 2010, g...@tuxfamily.net wrote: > > > > >commit d1b820e7e323771d79a164ffa02cd9b835213bab > >Author: Miroslav Lichvar > >Date: Thu Dec 9 15:14:05 2010 +0100 > > > > Shorten initial delay and sampling separation to 0.2

Re: [chrony-dev] [GIT] chrony/chrony.git branch, master, updated. 1.24-93-g833022b

2010-12-09 Thread Miroslav Lichvar
On Thu, Dec 09, 2010 at 06:16:06PM +0100, Miroslav Lichvar wrote: > > Is this going to run into problems with ntpd's Kill signal, thinking that > > your > > machine is flooding the server (or is the current behaviour of chrony > > already > > in danger of that anyway)? > > It should be ok. The 0