This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] more than 10 concurrent measurements to the same target
- Previous message (by thread): [atlas] more than 10 concurrent measurements to the same target
- Next message (by thread): [atlas] more than 10 concurrent measurements to the same target
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jared Mauch
jared at puck.nether.net
Wed Dec 9 19:58:31 CET 2015
> On Dec 9, 2015, at 1:38 PM, Klaus Darilion <klaus.mailinglists at pernau.at> wrote: > > Hi! > > When scheduling checks I often get the error: "We do not allow more than > 10 concurrent measurements to the same target." > > Imo this is not correct. Yes, I do schedule more then 10 measurements to > the same target, but they are not concurrent. They are sequential - one > ofter the other. Thus, it would be great if this check could be fixed to > consider start and stop times. I have found a workaround for this by using DNS names in addition to the IP address. Bonus points if you create your own unique DNS name for the time period in question. - Jared
- Previous message (by thread): [atlas] more than 10 concurrent measurements to the same target
- Next message (by thread): [atlas] more than 10 concurrent measurements to the same target
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]