strange lr_xml2report behaviour

[Edwin Groothuis]

I have some strange results with lr_xml2report:

    lr_run lr_xml2report -U spamfilter -S spamd \
							 2002-10-30.xml

       2002-10-29 ................................................ 0
       2002-10-30 ............................................. 4857

    lr_run lr_xml2report -U spamfilter -S spamd \
					  2002-10-29.xml 2002-10-30.xml

       2002-10-28 ................................................ 0
       2002-10-29 ............................................. 4861
       2002-10-30 ............................................. 4859

    lr_run lr_xml2report -U spamfilter -S spamd \
			   2002-10-28.xml 2002-10-29.xml 2002-10-30.xml

       2002-10-26 ................................................ 0
       2002-10-28 ............................................. 4214
       2002-10-29 ............................................. 4861
       2002-10-30 ............................................. 4859
    (where did 2002-10-27 go?)

    lr_run lr_xml2report -U spamfilter -S spamd \
	    2002-10-27.xml 2002-10-28.xml 2002-10-29.xml 2002-10-30.xml

       2002-10-26 ................................................ 0
       2002-10-27 ............................................. 5723
       2002-10-28 ............................................. 4861
       2002-10-29 ............................................. 4859
    (where did 2002-10-30 go?)

The time-periods are not overlapping:
    2002-10-27 00:00:01 EST - 2002-10-27 23:58:16 EST
    2002-10-28 00:00:01 EST - 2002-10-28 23:59:56 EST
    2002-10-29 00:00:01 EST - 2002-10-30 00:00:04 EST
    2002-10-30 00:01:11 EST - 2002-10-30 23:59:35 EST


lr_run lr_xml2report -U spamfilter -S spamd 2002-10-27.xml

   2002-10-26 ................................................ 0
   2002-10-27 ............................................. 1509
   (the first entry in the DLF file is 1035640801, or
	Sun Oct 27 00:00:01 EST 2002)

lr_run lr_xml2report -U spamfilter -S spamd 2002-10-28.xml

   2002-10-26 ................................................ 0
   2002-10-28 ............................................. 4214
   (the first entry in the DLF file is 1035723601, or
	Mon Oct 28 00:00:01 EST 2002)

lr_run lr_xml2report -U spamfilter -S spamd 2002-10-29.xml

   2002-10-28 ................................................ 0
   2002-10-29 ............................................. 4861
   2002-10-30 ................................................ 2
   (the first entry in the DLF file is 1035810001, or
	Tue Oct 29 00:00:01 EST 2002)

lr_run lr_xml2report -U spamfilter -S spamd 2002-10-30.xml

   2002-10-29 ................................................ 0
   2002-10-30 ............................................. 4857
   (the first entry in the DLF file is 1035896471, or
	Wed Oct 30 00:01:11 EST 2002)

Okay, the 
   2002-10-26 ................................................ 0
   2002-10-28 ............................................. 4214
one is due to Daylight Saving Time: 1035723601 is Monday 00:00, 24
* 3600 substracted from it is Sunday 00:00 but then the clock has
moved one hour forward so it will end up as Saturday 23:00.

Buuut, it doesn't explain why it will print the previous date, as
there is no data of it available.

Cc: to bugs@ for this strange behaviour (twice)

Raw log files, dlf files, xml files et al are available on request.

Edwin

-- 
Edwin Groothuis      |            Personal website: http://www.MavEtJu.org
edwin at mavetju.org    |    Weblog: http://www.mavetju.org/weblog/weblog.php 
bash$ :(){ :|:&};:   | Interested in MUDs? http://www.FatalDimensions.org/

-- 
To UNSUBSCRIBE, email to development-request at logreport.org with a subject of
"unsubscribe". Trouble? Send an email with subject "help" to
development-request at logreport.org