Le 16/08/2018 à 11:43, FUSTE Emmanuel a écrit :
> Le 16/08/2018 à 11:40, Miroslav Lichvar a écrit :
>> On Thu, Aug 16, 2018 at 09:23:06AM +, FUSTE Emmanuel wrote:
>>> No, with chrony the shm refclock seems to be ignored (need to retest
>>> precisely) . The observed stratum of my chrony servers
On 16/08/2018 04:40, Miroslav Lichvar wrote:
On Thu, Aug 16, 2018 at 12:11:00AM -0300, Gustavo Serra Scalet wrote:
I'm building Debian releases for cloud usage and noticed the known-issue[1]
regarding `getrandom` hanging when Chrony is called early on system boot
(and it does, as DHCP will call
Le 16/08/2018 à 11:40, Miroslav Lichvar a écrit :
> On Thu, Aug 16, 2018 at 09:23:06AM +, FUSTE Emmanuel wrote:
>> No, with chrony the shm refclock seems to be ignored (need to retest
>> precisely) . The observed stratum of my chrony servers were not
>> refclock+1 (0+1) but the defined orphan
On Thu, Aug 16, 2018 at 09:23:06AM +, FUSTE Emmanuel wrote:
> No, with chrony the shm refclock seems to be ignored (need to retest
> precisely) . The observed stratum of my chrony servers were not
> refclock+1 (0+1) but the defined orphan stratum (3).
Oh, you mean the servers were not
Le 16/08/2018 à 10:57, Miroslav Lichvar a écrit :
> On Thu, Aug 16, 2018 at 08:47:16AM +, FUSTE Emmanuel wrote:
>> NTP servers pool connected to the PTP network and to the organization
>> network.
>> Each server use the GM on the PTP network.
> The servers have a SHM reference clock providing
On Thu, Aug 16, 2018 at 07:53:24AM +, FUSTE Emmanuel wrote:
> have you on your todo list for a future release some work around orphan
> mode and refclocks ?
I wasn't planning anything in that area.
> Taking refclocks into account as other ntp sources for the orphan mode
> is the only
Le 16/08/2018 à 09:40, Miroslav Lichvar a écrit :
> I was planning to make a new release in about a month, depending on
> how much time I'll have for chrony. There is just one new feature left
> on my todo list and then I'll be writing tests for the new code, etc.
>
> If people think it's
On Thu, Aug 16, 2018 at 12:11:00AM -0300, Gustavo Serra Scalet wrote:
> I'm building Debian releases for cloud usage and noticed the known-issue[1]
> regarding `getrandom` hanging when Chrony is called early on system boot
> (and it does, as DHCP will call it during network configuration). I see
