Subj : Pktdate works fine.. :)
To : mark lewis
From : Janis Kracht
Date : Fri Mar 25 2016 08:00 pm
Hi Mark,
>> I just dug up an old packet I had laying around here and tried pktdate on
>> it:
>> bbs@filegate:~/pktdate$ ./pktdate -me -c 1a35fac1.pkt Pktdate Rev. 1.5:
>> processing 1a35fac1.pkt (type: 2+) Packet header date (D/M/Y): 19.9.2012
>> fixed to 25.3.2016. Packet sender: 1:261/38.0 Msg #001: Date "19 Sep 12
>> 15:50:00" fixed to "25 Mar 16 16:38:51" (rc 8). Msg #001: Message sender
>> is "Nick Kill@1:261/38". Msg #002: Date "19 Sep 12 15:54:22" fixed to "25
>> Mar 16 16:38:51" (rc 8). Msg #002: Message sender is "Janis
>> Kracht@1:261/38". Wrote changes to 1a35fac1.pkt.
>> Interesting.. :)
> yup... i've been running it here since it was first every released... have
I used to run it way back.. then never noticed the source until Ben sent it out
<bg>
> pktdate fixed it to today's date... that may cause other systems to not catch
> the post as a dupe if their dupe database goes back that far...
Sure.. like I said this was just an old packet I had kept for some reason or
other.. so it was a good test pkt for this.. (i.e., not a live packet in the
stream).
> anyway, here's what i currently use...
> rem set pdate=pktdate -k -c -l2 -S -L%fd%\pktd-sec.log
> rem ***
> rem *** -c means to correct the pkt... stopped correcting on 7 Jul 2014
> rem *** -k means to keep the original pkt if we correct any dates in it
> rem *** -p means "past" and "9y" means "9+ years"
> rem *** -f means "future" and "1m" means "1+ month"
> rem *** -l is the logging level
> rem *** -S changes seadog dates to standard ftsc dates
> rem *** -L is the log file name
> set pdate=pktdate -k -p9y -f1m -l2 -S -L%fd%\pktd-sec.log
> gosub do_mydate
> echo %MYDATE% [723] %pdate% | %SLOGS%
> for %%i in ( *.pkt) do %pdate% %%i
Looks good..
> i set my command in an environment variable so i can echo it to my processing
>log... then i just toss it at each pkt in my secure and insecure directories..
> each has its own log... in the above, if the date is older than 9 years or
>newer than 1 month in the future then we note it in the processing log... if i
>was using "-c" it would be corrected in the pkt... i also have it changing the
> seadog date format to the fido date format since all my software expects the
> fido format...
