RE: [chrony-users] "clients" command maxes out at 4096

["McDonald, Isaac" <Isaac.McDonald@xxxxxxxxxxxxxxxxxx>]

That makes perfect sense. Seeing as how I'm more interested in how many
clients are connecting as opposed to what their IP addresses are I'm going
to hold off on increasing clientloglimit.

Is there functionality available to report on the number of unique NTP
clients? If not, where can I submit a feature request?

--
Isaac McDonald

-----Original Message-----
From: Miroslav Lichvar [mailto:mlichvar@xxxxxxxxxx] 
Sent: Tuesday, May 31, 2016 10:46 AM
To: chrony-users@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [chrony-users] "clients" command maxes out at 4096

On Tue, May 31, 2016 at 05:19:25PM +0000, McDonald, Isaac wrote:
> Hello,
> 
>  
> 
> I've noticed the "clients" command appears to stop listing clients at
4096.
> Is this intentional? Run "chronyc -a -n -m clients |wc -l " to count 
> the amount of clients connecting.

The amount of memory used for monitoring clients is limited, so chronyd
running on a public server doesn't try to take all memory and crash. It can
be configured with the clientloglimit directive. By default, it's 1 MB by
default, which allows monitoring of 4096 clients at the same time. You can
increase it as much as you want and there should be no impact on the maximum
packet rate the server will handle.
Just the chronyc clients command will take much longer :).

--
Miroslav Lichvar

--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.

Attachment: smime.p7s
Description: S/MIME cryptographic signature