From d1e5dee6ca9ddd0c806ef52375d997e33b1c98fa Mon Sep 17 00:00:00 2001 From: Jan Willamowius Date: Wed, 25 May 2022 05:36:50 +0200 Subject: [PATCH] fix documentation of [RasSrv::LRQFeatures] NeighborTimeout and consistently treat the value as 10th of a second --- Neighbor.cxx | 4 ++-- changes.txt | 2 ++ docs/manual/neighbors.sgml | 4 ++-- 3 files changed, 6 insertions(+), 4 deletions(-) diff --git a/Neighbor.cxx b/Neighbor.cxx index d3061e64..8007339e 100644 --- a/Neighbor.cxx +++ b/Neighbor.cxx @@ -279,7 +279,7 @@ class NeighborPingThread : public PThread, public RasRequester { void NeighborPingThread::Main() { - int timeout = GkConfig()->GetInteger(LRQFeaturesSection, "NeighborTimeout", 5) * 1000; + int timeout = GkConfig()->GetInteger(LRQFeaturesSection, "NeighborTimeout", 5) * 100; PString pingAlias = GkConfig()->GetString(LRQFeaturesSection, "PingAlias", "gatekeeper-monitoring-check"); H225_ArrayOf_AliasAddress aliases; aliases.SetSize(1); @@ -1939,7 +1939,7 @@ class NeighborPolicy : public Policy { NeighborPolicy::NeighborPolicy() : m_neighbors(*RasServer::Instance()->GetNeighbors()) { - m_neighborTimeout = GkConfig()->GetInteger(LRQFeaturesSection, "NeighborTimeout", 5) * 1000; + m_neighborTimeout = GkConfig()->GetInteger(LRQFeaturesSection, "NeighborTimeout", 5) * 100; m_name = "Neighbor"; } diff --git a/changes.txt b/changes.txt index 154248a3..caa0fd6d 100644 --- a/changes.txt +++ b/changes.txt @@ -1,5 +1,7 @@ Changes from 5.9 to 5.10 ======================== +- BUGFIX(Neighbor.cxx, neighbors.sgml) fix documentation of [RasSrv::LRQFeatures] NeighborTimeout + and consistently treat the value as 10th of a second - fix crash when handling MSD diff --git a/docs/manual/neighbors.sgml b/docs/manual/neighbors.sgml index cedfb093..3be11cd7 100644 --- a/docs/manual/neighbors.sgml +++ b/docs/manual/neighbors.sgml @@ -73,9 +73,9 @@ The -Default: +Default:

-Timeout value in seconds to wait for responses from neighbors. +Timeout value in 10th of a second to wait for responses from neighbors. If no neighbor responds before the timeout, the gatekeeper will reply with an ARJ to the endpoint sending the ARQ.