> esr@snark:~/software/ntp-rescue/ntpsec$ ntpq -c mrulist
> ***Command `mrulist' unknown
I don't know what's wrong on your end. When I cut/paste that line, I get
things like this:
Ctrl-C will stop MRU retrieval and display partial results.
Retrieved 5 unique MRU entries and 0 updates.
lstint av
Hal Murray :
>
> e...@thyrsus.com said:
> > I'm not sure what the referent of "that" is. The statistics-gathering I've
> > seen seems to be all about writing line-at-a-time records to various stats
> > files; I can't see that generating a lot of memory pressure.
>
> > If there's somewhere in the
e...@thyrsus.com said:
> I'm not sure what the referent of "that" is. The statistics-gathering I've
> seen seems to be all about writing line-at-a-time records to various stats
> files; I can't see that generating a lot of memory pressure.
> If there's somewhere in the code that is allocating mem
Hal Murray :
> ntpd can take a lot of memory if you collect the statistics for who is
> talking to you on a busy machine, for example a pool server. It depends on
> how busy and how long you want to keep the data.
>
> Is there any way to turn that off?
>
> I don't see any mention in the documen
e...@thyrsus.com said:
> BTW, I think I've knocked the mlockall/threads/async bug on the head. I
> swiped some code from chrony that does memlocking after telling ntpd it can
> have as much memory as it wants - ntpd's worst-case memory requirement ain't
> much. I've had that version running contin
