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] feature requests
- Previous message (by thread): [atlas] feature requests
- Next message (by thread): [atlas] feature requests
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Klaus Darilion
klaus.darilion at nic.at
Mon Nov 11 12:22:59 CET 2013
On 11.11.2013 12:21, Klaus Darilion wrote: > > On 11.11.2013 12:12, Gert Doering wrote: >> Hi, >> >> On Mon, Nov 11, 2013 at 11:49:57AM +0100, Vesna Manojlovic wrote: >>> Posting your wish on the mailing list will raise the priority of your >>> requested feature, so, everyone, please keep on doing that! >> - restart an UDM after it has stopped >> >> - change parameters of an UDM and restart it, keeping the same ID >> >> (usage case: test run an UDM with just a few probes, develop the >> software to fetch and evaluate the json result data, then set >> the number of probes / number of packets / frequency / ... to >> what the final measurement should be, without having to change the >> ID in the grabbing software - especially if tweaking parameters for >> a couple of rounds this gets inconvenient) > That's one reason why I switched to the REST API To be more verbose: My "add measurement" script writes the ID to a file, and my "analyze" script reads the ID from this file. regards Klaus
- Previous message (by thread): [atlas] feature requests
- Next message (by thread): [atlas] feature requests
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]