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] Scheduling a test for all probes?
- Previous message (by thread): [atlas] Flow-id of built-in traceroute measurement
- Next message (by thread): [atlas] Introducing the RIPE Forum
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jared Mauch
jared at puck.Nether.net
Wed Apr 6 13:06:35 CEST 2016
On Wed, Jan 27, 2016 at 12:25:19PM +0100, Robert Kisteleki wrote: > (Excuse me for the belated answer -- I'm picking up topics that were not > answered by us or the community.) > > On 2015-12-09 20:00, Jared Mauch wrote: > > Is there a way to schedule a one-off test on all the probes to be run “at a leisurely pace”, eg: looking up a specific DNS QNAME? > > > > (I’ll call it a lazy query/scheduling). > > > > - Jared > > Not at the moment -- one-off really means "it's important, do it now!" Yeah, I'm looking for something that says "I'd like to run this one item on all probes". > One can always schedule a short-running regular measurement and use the > (new) spread control mechanism to distribute the probes over a longer period. I'll have to look closer at this. - Jared -- Jared Mauch | pgp key available via finger from jared at puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.
- Previous message (by thread): [atlas] Flow-id of built-in traceroute measurement
- Next message (by thread): [atlas] Introducing the RIPE Forum
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]