On 3/17/20 4:02 AM, Marc Lehmann wrote:
> On Sun, Mar 15, 2020 at 03:43:09PM -0700, Robert Woodcock
> wrote:
>> If you *do* need to differentiate, I would adjust the limit for the
>> number of outstanding probes in packet/probe.h, and then recompile:
>>
>> #define MAX_PROBES 1024
>>
>> However, t
On Sun, Mar 15, 2020 at 03:43:09PM -0700, Robert Woodcock
wrote:
> If you *do* need to differentiate, I would adjust the limit for the
> number of outstanding probes in packet/probe.h, and then recompile:
>
> #define MAX_PROBES 1024
>
> However, that's not enough - I believe the intent of this
This would be caused by the use of very low intervals, as you mentioned
(causing ping probes to be consumed at a fast rate) in combination with
lost packets at one or more remote hops (causing the probes to not be
freed soon enough). 10 seconds at 100 probes per second does not leave
sufficient mar
Package: mtr-tiny
Version: 0.92-2
Severity: normal
Dear Maintainer,
recent versions of mtr started to crash seemingly randomly with the
following message:
mtr: Probes exhausted
and an exit status of 1. It's not consistently reproducible, but I found
that when specifying a low interval, e.g.
4 matches
Mail list logo