On Tue, 2008-11-25 at 10:38 +1100, Ken McDonell wrote:
> Hmmm.
>
> Does not disprove my hypothesis, but does not prove it either.
>
> 20081006 is a bit odd. If pmdumplog -l reports an end time then the
> archive is not really busted. But pmdumplog -v is a strange beast, that
> looks like a pmdumplog bug (sigh).
>
> Just try pmdumplog 20081006 | head -100 ... the timestamps appear in the
> pmResult dumps.
I've attached two dump heads - one pmdumplog with no options,
the other with -Dpdu (this one shows the raw timestamps).
> But 20081006 looks like it is for the correct day which undermines my
> theory.
>
> I believe the problem is in pmdate -1d when you're within an hour of
> midnight and there was a DST adjustment in the previous 23-25 hrs ...
> there is no good answer here, pmdate cannot produce the 100% right
> answer no matter what.
Yep, sounds entirely feasible.
> I'm looking at reworking pmlogger_daily to remove all dependence on
> pmdate, and this will give me a chance to re-instate the -o option ...
> actually new behaviour to merge _all_ archives, not just yesterday's and
> -o for the old (current) behaviour, so all of pmlogger_daily QA will
> work again ...
OK, great!
cheers.
--
Nathan
dumplog.head
Description: Text document
dumplog.head2
Description: Text document
|