perfsonar-user - Re: [perfsonar-user] Change of IP
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Brian Candler <>
- To: Andrew Lake <>
- Cc: "" <>
- Subject: Re: [perfsonar-user] Change of IP
- Date: Thu, 29 Jan 2015 19:58:18 +0000
- Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=sasl; b=r/XYgW j17r5I/sqYhzEP8x7m3WVFMNRNMFQEzhbRAr4I74AUm2AeznSAi7fbt5Ko27ri5Y lgc7uSeVkG8jzBzB+ywBX99LwihV9d7ddXTYb3nTYoT7Kpmd1nI9QjDBsOb/yRo9 LQdhA4PrTWTF82WIH/g4NhJ0faVI+U1E6A2/E=
On 29/01/2015 14:55, Andrew Lake wrote:
There's a script that allows you to delete data based on age, so you couldThanks - I have no problem erasing history rather than modifying it.
potentially use that, though I am guessing since it is a remote host you have
a bunch of other data you don't want deleted that is just as old. I have
created an issue to add a filter based on IP address to our DB cleaner
script. You could likely monkey with postgres to change the IP, but I
generally don't think retroactively changing things like the IP observed at
the time of the measurement is a good idea….but maybe I have seen Back to the
Future too many times and have become too wary of changing the past;)
Another example of where I'd like to do this is where I was doing some experiments with different test durations - e.g. 5 seconds, 7 seconds, 10 seconds. Now I have separate esmond archives for each set of parameters, and this makes navigating the JSON rather painful.
- [perfsonar-user] Change of IP, Brian Candler, 01/28/2015
- Re: [perfsonar-user] Change of IP, Andrew Lake, 01/29/2015
- Re: [perfsonar-user] Change of IP, Brian Candler, 01/29/2015
- Re: [perfsonar-user] Change of IP, Andrew Lake, 01/29/2015
Archive powered by MHonArc 2.6.16.