Good Evening. Some News ...
* I will be attending LISA'06. If you want to take the oportunity
to meet to discuss ideas, projects, war stories, please drop a
line.
* In order to be able to spend more time on RRDtool/MRTG/SmokePing
work, I have setup a Sponsorship Program for companies and
On Fri, Dec 01, 2006 at 03:26:00PM +0100, Alex van den Bogaerdt wrote:
> (side note: 1.1806045000e+02 seems a weird value. I am going to look into
> this)
This seems to be a minor bug, fixed in svn. It has to do with rounding
(and subsecond precision timestamps indeed).
--
Alex van den Bogaer
On Fri, Dec 01, 2006 at 01:11:38PM +0100, Markus Wiget wrote:
> > Use timestamps, not "N".
>
> What's wrong when using "N"? I just read in the man page that it is
> legal. Anyway, if I use explicit update time by replacing
So what? Did I say "It is illegal to use 'N'" ? No, I didn't.
Here's w
Thanks for spending time on my problem. According to your answer I tried
to simplify my request.
Alex van den Bogaerdt wrote:
> On Wed, Nov 29, 2006 at 12:35:01PM +0100, Markus Wiget wrote:
> step 300, heartbeat 600. This means that if the updates would be
> exactly five minutes apart, with the
Hi Tobi/Johannes
I think a standard would be a good thing so that we can compare. However
when posting stats it would be usefull to know the types of disk and
raid configuration as I think these are as important as raw CPU power.
Tobi I assume the number of RRA's in the RRD is important as well,
On Thu, Nov 30, 2006 at 02:30:40PM -0800, Joel Lindsay wrote:
Hi Joel.
> Hi,
> I have no clock on my embedded system so am having problem using rrdtool
> correctly. I can add a fake date and therefore enter info into the RRD but
Not having a time source is usually a bad thing (tm).
Can you use N
