pmlogrewrite quirk/bug?

Hi Ken,

Just writing a QA test for a logrewriter, and came across an odd
behaviour.  It looks like pmlogrewrite writes a different metadata
end to that which pmlogger & pmlogextract generate (checked both)?

I'll push this within qa/827, you can see this behaviour with the
new archive there.  I wouldn't expect a .meta file size change as
a result of this rewrite (its only units & sem affected).  Should
see a failing test with this at the end -

new -> ref changes ... expect none
@@ -375,7 +375,7 @@
 Temporal Index
              Log Vol    end(meta)     end(log)
 10:10:27.854       0          132          132
-10:10:27.855       0          351          272
+10:10:27.855       0         7893          272

 [140 bytes]
 10:10:27.854  2.3.3 (pmcd.pmlogger.host): inst [16936 or "16936"] value "slack"


(this archive was created with -T1sec and the attached pmlogger
config)

Does this behaviour sound familiar, or look like something obvious
to you?  Otherwise I'll dig deeper.  Thanks!

cheers.

--
Nathan

-=-=-=-=-=-=-=-=-=-=-=-
pcp mailing list
[email protected]
https://groups.io/g/pcp/messages
-=-=-
Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#14585): https://groups.io/g/pcp/message/14585
View All Messages In Topic (1): https://groups.io/g/pcp/topic/2967210
Mute This Topic: https://groups.io/mt/2967210?uid=174580
New Topic: https://groups.io/g/pcp/post

Change Your Subscription: https://groups.io/g/pcp/editsub?uid=174580

Group Home: https://groups.io/g/pcp
Contact Group Owner: [email protected]

Terms of Service: https://groups.io/static/tos

Unsubscribe: https://groups.io/g/pcp/leave/354243/563757577/xyzzy
-=-=-=-=-=-=-=-=-=-=-=-

log mandatory on once {
	network.tcp
}