Subj : Re: FTN Packet's message date question
To   : slacker
From : deon
Date : Tue Dec 24 2024 10:02 am

  Re: Re: FTN Packet's message date question
  By: slacker to deon on Mon Dec 23 2024 07:23 pm

Howdy,

 > FTSC_DATE: 23 Dec 24 23:59:18 :: TZOFFSET: 1200
 >
 > BBS Log:
 > [2024-12-23 06:04:11.85648] [13813] [error] Parsed date time:
 > 2024-12-23T11:59:18 is after current UTC date: 2024-12-23T11:04:11 even
 > after TZ correction 1200 :: Using current UTC date for value.
 >
 > I think coming from hub 1, the TZUTC offset should be 1300 now instead of
 > 1200 for daylight savings, right? If I corrected for 1300, the time would
 > have been valid and just 5 min before the current UTC time when I processed
 > the packet.

Yes, you are correct. I just looked at the packet I received from Hub 1,and it does have TZUTC 1200. It should be TZUTC 1300 to be correct, but since its generated from a script Paul might have 1200 hard coded.

 > I'll also take a look at using the packet date as you mentioned in
 > a previous message. Maybe that would be a better choice than what I'm
 > doing.. but again, I think I might just be over thinking this. :)

I dont recall what you are doing - but keep in mind, that the packet date I generate will be the time of the youngest message in the packet, in the time the source gave it to me (if the packet format has timestamps - from memory its only 2.2 that doesnt).


....лоеп
--- SBBSecho 3.23-Linux
 * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

.